Configure inbound and outbound webhooks

Choose direction and ownership

Inbound receives events from your external system. Outbound delivers events to your endpoint. Integration webhooks live on an integration's Webhooks tab; automation trigger webhooks also have an Automation → Webhooks management screen. Use the webhook selected by the workflow or integration you are configuring, not a guessed URL.

Configure and test

1. Open the relevant integration's Webhooks tab or the automation webhook screen with management permission.
2. Create the webhook with a descriptive name, direction, supported event selection, and active state. For outbound delivery enter your endpoint URL and any supported headers.
3. For inbound events copy the URL shown for the configured webhook. Keep the associated secret private.
4. Confirm the authentication/signature and payload contract with your backend or integration implementer. Do not reuse a recipe from a different webhook direction.
5. Send a sanitized test event or use the screen's test action. If triggering a workflow, check its selected webhook/event and actual captured payload.
6. Inspect delivery history, status code, response/error, and retry count where shown. Verify the resulting business operation separately.

Endpoint implementation

Use HTTPS for your endpoint and validate incoming payloads against the agreed contract. Verify signatures against the exact raw bytes and scheme specified by that contract. Handle repeated deliveries safely. A retry count in the UI does not establish a guaranteed retry schedule; confirm delivery timing with the backend owner.

Expected result and recovery

The intended event reaches the intended consumer once in business effect. If nothing happens, check active state, direction, event name, authentication, conditions, recipient mapping, and delivery error. A successful HTTP response alone does not mean the downstream workflow completed.