Skip to main content
Connector steps are planned and not yet available. The description below reflects the intended design. See Integrations: Connectors for what’s available today.
A Connector step would let you reach beyond HTTP request steps and interact with external systems — databases, queues, third-party platforms, internal tools — as a first-class step in a journey. Instead of writing a custom script to query a database or trigger a webhook, you’d configure a connector step that handles the integration and exposes its results to the rest of the journey.

​
Intended idea

Connectors would be backed by a library of integration definitions (similar to how HTTP request steps are backed by the request template library). You’d select a connector, configure it with the credentials and parameters it needs, and it would produce outputs that later steps can reference. Some likely uses:
  • Querying a database to verify that a record was created correctly after an API call
  • Publishing a message to a queue and asserting that a downstream system processed it
  • Checking state in a third-party service (a Stripe subscription, a Linear ticket) as part of an end-to-end workflow