How to configure webhooks

Webhooks are configured inside Automations, not in a separate developer or API area. There are two, and they are not the same kind of thing.

Catch a Webhook is a trigger. It starts an automation the moment it receives a payload at its URL. Send a Webhook is an action, a step inside an automation that sends a payload out to somewhere external. One begins a workflow, the other happens during one.

Catch a Webhook, the trigger

Use this when you want an external service to start an automation by sending it data.

When choosing a trigger for a new automation, Catch a Webhook sits under Advanced, alongside other trigger types.

Adding it generates a unique webhook URL for you automatically, with a Copy button next to it. Give that URL to whatever external service needs to trigger this automation.

Until a payload arrives, it shows Waiting for payload. Send a test request to that URL, and once one is received, it shows Payload Detected, along with the date and time it arrived and the IP address it came from. A Retry option is there if you need to send or capture another one.

Underneath, Detected Data lists every field found in that payload, each shown as its raw key alongside an editable label. Tick the checkbox on any field you want to use. Only fields you've ticked become available in later steps of the automation, anything left unchecked is ignored.

Send a Webhook, the action

Use this when you want an automation to send data out to something external.

Action Name

A name for this step, used to identify it within the automation itself.

Webhook URL

The address the payload is sent to, entered after the fixed https:// prefix.

Method

Choose how the request is sent. The options are GET, Create, Update and Delete, matching what the destination is expecting to receive.

Parameters

Key and value pairs, added with Add Parameter, for any extra data you want sent along with the request. Add as many as the destination needs.

More Settings

An expandable section holding authentication and headers, for anything that needs more than a plain request.

Basic Authentication takes a single field, entered as username followed by a pipe character followed by password, rather than two separate fields.

Headers are key and value pairs, the same shape as Parameters, added with Add Header. Use these for anything the destination expects in its request headers rather than in the main payload.

Once everything is filled in, Submit saves the step.