Backend Webhooks from Flows

You can call your backend directly from a flow by using a Generic HTTP connector as a "webhook" step. The request is triggered at that point in the flow execution and sends whatever payload you define—flow context, user info, form data—formatted exactly how your API expects it. This is different from audit streaming: the call happens immediately when the flow hits that step, not as part of a batched audit export.

Use flow webhooks when you need to notify or sync with your backend at a precise moment in the flow, with a payload that matches your system.

Using a Webhook in Your Flow

1. Create a Generic HTTP connector

Create a Generic HTTP connector to your backend API that will consume the information sent from the flow. Full configuration options are in the Generic HTTP Connector guide.

2. Add the Webhook Action to Your Flow

1. In the Flow Editor, open your flow.
2. Click the + button and choose Connector → Generic HTTP / Post Action.
3. Select the connector you created and set the path (e.g. /webhooks/auth-complete).
4. In the request Body, build the JSON you want your backend to receive.

You can use dynamic values so each request is filled with current flow and user data. For example:

{
  "event": "user_signed_in",
  "userId": "{{user.userId}}",
  "email": "{{user.email}}",
  "tenantId": "{{user.tenantIds[0]}}",
  "loginId": "{{form.email}}",
  "authMethod": "{{lastAuth.authMethod}}"
}

Your backend receives exactly this structure on each run, so you can map it directly to your DB or internal APIs.

3. Use the Action in Your Flow

Add the Generic HTTP / Post action at the point in the flow where you want the webhook to fire—for example right after a successful sign-in or after collecting consent. The request runs when that step executes.

Alternate Method: Using the Audit Trail

Flow webhooks are for calling your backend with a custom payload. They do not, by themselves, create audit events in Descope’s audit trail or in audit streaming.

If you want the same moment to appear in your audit log and in any audit-based integrations, add a Generate Audit Event action in the flow (e.g. next to or right after the webhook step). That action creates a custom audit event with a step name, action, type, and event data you choose. Those events show up on the Audit page and are streamed to configured Audit Connectors.

So you can have both:

• Generic HTTP (flow webhook): real-time, custom request to your backend.
• Generate Audit Event: same moment recorded in Descope’s audit trail and audit streaming.