Connectors
With Connectors, you can enrich your Descope flows by allowing you to integrate with external services to fetch information or push data during the execution of the flow.
Connectors are configured within the Connectors Page of the Descope Console.
Most connectors are used as steps within Flows, except for Audit & Troubleshooting Connectors which are used for streaming data and are not added as flow steps.
Connectors run synchronously by default: the flow waits for the connector to complete and receive a response before advancing to the next step. The response is then available in flow context for use in conditions, scriptlets, or later steps.
You can also configure a connector step to run asynchronously—for example when the flow does not need the result (e.g. sending analytics or firing a webhook). When run async, the flow continues without waiting and the connector response is not written to flow context.
Private network resources
To run connector actions against APIs or services inside your firewall (no inbound ports), deploy the Descope Engine in your network and assign connectors to it in the Console.
Here is a comprehensive list of all of the Connectors we currently support, as well as guides on how to configure each of them.
If you wish to request a new connector, please submit a Feature Request.