Connectors

Connectors will be a step type that lets a journey interact with an external system — not just send HTTP requests to your own APIs, but reach out to third-party services, internal tools, or data sources as part of the workflow. Think of them as first-class steps for integrating actions like creating a ticket, triggering a webhook, or querying an external dataset mid-journey.

​

When to use it

Connectors are intended for situations where a journey needs to do something beyond HTTP requests to your own endpoints:

• Create or update a ticket in an external system as part of a workflow step.
• Trigger a side-effect in a third-party tool during a run.
• Pull data from an external source to use in later steps.

These are different from the work-item integrations (GitHub, Jira, Linear) that link tickets to journey Coverage — those are a traceability feature in Build mode, not run-time steps.

​

Key concepts

Connector step — a planned step type, alongside request steps, scripts, sub-journeys, set variables, and others. Like all steps, a connector step will appear on the journey canvas in Build mode and can be sequenced with other steps. Step outputs — connector steps are expected to produce step outputs, just like request steps, so later steps can use the results. Run-time execution — connectors will run during a journey’s execution (in Run mode, via the Cloud Runner, or through the CLI), not just at configuration time.

​

How it works

The details of connector configuration are still being designed. The general shape will follow the same pattern as other steps: you add a connector step to the journey canvas, configure its inputs (which may come from run inputs, variables, or previous step outputs), and map its outputs for use downstream. See Steps overview and Connectors step reference for updates as the feature ships.

​

Examples

Planned use cases (illustrative — not final):

• After a successful payment journey run, create a Jira ticket summarizing the result.
• Before a journey run, fetch a feature-flag value from an external config service and use it as a variable.
• During a support runbook, post a summary to a Slack channel when a manual checkpoint is reached.

These are directional examples. The exact connector types and configuration will be documented when the feature is available.

​

Related pages