Connectors in Flows
Connectors enable you to integrate with third-party services to fetch data or push information during flow execution. Configure connectors in the Connectors page of the Descope Console, then add them as steps within your flows.
For further information about Connectors including dedicated configuration guides, check out our Connectors Doc.
Testing Connectors
If the connector supports testing, use the test functionality on the connector configuration page to verify connectivity. For some connector types, you may need to provide a test URL or endpoint.
Test results display in the Test Results panel, showing the response or any errors that occurred.
Implementing Connectors in Flows
Add the Connector to the Flow
- Click the + icon in the flow editor and select Connector
- Select the Connector or Connector type (e.g., GET request for Generic HTTP)
Configure the Connector
Connector Settings
| Setting | Description |
|---|---|
| Step Name | Name for the connector step in your flow |
| Connector | Select from configured connectors in your project |
| Base URL | Auto-populated from connector configuration (read-only) |
| Endpoint | Endpoint path (can include query parameters) |
| Payload | JSON Payload for the request |
| Timeout | HTTP request timeout in seconds |
| Run asynchronously | Select this option if the flow doesn't need to wait for the step's result to continue (like sending analytics data). Response will not be available in context. |
| Context Key | Response data is mapped to this key for use in later steps |
| Error Handling | Define custom error handling |
Attach the Connector within the Flow
Once you have configured the Connector, attach it within your flow. In this example, the action is connected after successful authentication of the user.
Accessing Connector Results
Once a connector step executes, its response data is available in the flow context under the Context Key you specified during configuration. Access the data using the pattern connectors.<contextKey>.
For nested JSON properties, use dot notation (connectors.<contextKey>.<jsonKey>).
You can use connector results in:
- Conditions: Implement conditional logic based on connector response data
- Custom Claims: Add connector data to the user's JWT using the Custom Claims action
- Update User Properties: Update user attributes with data from the connector response
- Other Actions: Reference connector data in any action that supports dynamic values
Troubleshooting Connectors
You can use the Flow Runner to debug connectors. When running a flow, Descope logs the request sent to the connector and the response received in the runner messages.