Webhook steps in automation tools

All three tools follow one pattern. You add a webhook trigger, copy the URL it gives you, paste that URL into the sending app, then send a test event. The names and limits differ. Facts below were read from each maker's page on the date this page was reviewed, and they can change.¹

What you need

• An account with the automation tool. Plans and limits differ, so check the maker's pricing page.
• A sending app with a webhooks settings page.
• A test event you can trigger on purpose, such as a dummy form entry.
• No customer data in your tests if you can help it.

Zapier

Zapier's webhook trigger lives in an app called Webhooks by Zapier. You open the Zap editor, click the Trigger step, and search for that app.¹

You then choose an event. Catch Hook parses the request body for you. Catch Raw Hook leaves it unparsed and includes the headers.¹

Zapier recommends some familiarity with HTTP requests, APIs and reading API documentation before you start.¹ The same page says Zapier Support can give basic troubleshooting but can't troubleshoot the other app's API.¹

On the page as checked on 24 October 2026, the maximum payload is 10MB for triggers and 2MB for Catch Raw Hook.¹ It lists the feature as available on the Free, Professional, Team and Enterprise plans.¹

Make

Make calls its two kinds app-specific webhooks and custom webhooks. App-specific ones listen for data from a given app. Custom ones let you create a URL and send any data to it.²

To create a custom webhook you use Make's Webhooks app.²

When a request arrives, Make stores it in that webhook's queue.² Each webhook has its own queue, and you can see them under the Webhooks section in the left menu.²

By default, Make runs the scenario straight away. You can instead set a schedule so queued requests are processed in batches.²

Make has default replies when no Webhook response module is in the scenario. A request accepted into the queue gets a 200 status. A full queue gets 400. A failed rate limit check gets 429.²

n8n

n8n uses a Webhook node. It's a trigger node, so it can start a workflow. It can also catch events from services that have no dedicated trigger node.³

The node has two URLs, one for testing and one for production.³ The test URL shows incoming data in the editor. The production URL registers when you publish the workflow, and you view those runs under the Executions tab.³

You can require authentication from callers. The options are Basic auth, Header auth and JWT auth, or none.³ The maximum payload size is 16MB, and if you self-host n8n you can change this limit with the N8N_PAYLOAD_SIZE_MAX environment variable.³

Side by side

Before you build anything real

• Read the maker's page for the latest steps. Menus get renamed.
• Check what your plan includes. We haven't quoted prices here because they change.
• Keep the address private. The URL page says why.
• Know what arrives before you wire it to anything else. A walkthrough of a sample request is here.
• If an AI step comes next, read the safety notes for AI prompts first.