Receive data from another service with an incoming webhook

Give another service a URL to call so its data starts a workflow in your app, and find the older incoming webhooks under Automation.

  • Verified Nov 17, 2026
  • Classic builder
  • Available on: Business Growth, Business Pro, Business Elite

On this page
  1. Receive a webhook with a workflow
  2. Incoming webhooks under Automation
  3. Plans
  4. If nothing happens

An incoming webhook is a URL in your app that another service calls when something happens on its side, such as a payment, a form submission or a new order. The data it sends starts work in your app, for example creating or updating a record.

Receive a webhook with a workflow #

  1. Create a workflow with the Incoming Webhook trigger In the trigger picker it is described as When a webhook is received.
  2. Save the workflow Until then the trigger says Save this workflow to generate its incoming webhook URL. After saving, the Webhook URL appears with a Copy button.
  3. Capture a sample Click Send a test request, paste a sample with Paste sample JSON, or have the other service call the URL with ?test=true added. The fields of the sample become available to mappings, conditions and Loop steps.
  4. Add the steps For example a Create Record or Update Record action that maps the incoming values to your fields.
  5. Give the URL to the other service It sends a JSON body to the URL with a POST request. Each request runs the workflow.

The URL ends in a secret key that is unique to the workflow. Treat the whole URL like a password: anyone who has it can run the workflow.

Under Delivery, Allow Immediate Processing runs the workflow while the request is open and replies with the result instead of queueing it. Keep it off for long workflows, or the sender waits. Under Failure Notification, Email on failure sends one email when a run ends badly or a step fails.

For every option of the trigger, see Incoming Webhook.

Incoming webhooks under Automation #

Incoming webhooks created before Workflows live under Automation › Incoming Webhooks. What you see there depends on your app:

  • Workflows available, no incoming webhooks: the page says incoming webhooks are no longer managed here and offers Go to Workflows.
  • Workflows available, some incoming webhooks: a notice says they are moving to Workflows. Your webhooks keep working and the webhook manager opens below the notice.
  • Workflows not available: the webhook manager opens as before.

If the app has never used incoming webhooks, the page first shows Enable Incoming Webhook. Click it to switch the feature on for the app; the webhook manager then loads inside the page with your app's tables and fields, and you edit each webhook, its URL and its field mapping there.

Plans #

Incoming webhooks are included in Business Growth, Business Pro and Business Elite, with up to 10 per plan. The Incoming Webhook trigger also needs your plan to include it; if it does not, requests to a workflow's URL are refused.

If nothing happens #

  • Check that the workflow is saved and that the other service uses the exact Webhook URL, including the key at the end.
  • Check that the service sends a POST request with a JSON body.
  • Open the workflow's run history to see whether the request arrived and which step failed. See Workflow history and logs.

Was this page helpful?

Something wrong or missing on this page? Tell us.