How to set up webhooks in Zapier
Quick Answer: Zapier webhooks allow external services to trigger Zaps by sending HTTP POST requests to a unique Zapier-generated URL. The Webhooks by Zapier trigger is available on all paid plans.
How to Set Up Webhooks in Zapier
Webhooks enable external applications and custom scripts to trigger Zapier automations by sending data to a URL endpoint. As of April 2026, the Webhooks by Zapier app is available on all paid Zapier plans (Starter at $19.99/month and above). Webhooks are one of the most flexible integration methods because any system capable of sending an HTTP request can start a Zap.
Step 1: Create a New Zap with a Webhook Trigger
Log into Zapier and click "Create Zap." In the trigger search box, select "Webhooks by Zapier." Choose the trigger event:
- Catch Hook — Receives any incoming POST, PUT, or GET request and parses the JSON/form body
- Catch Raw Hook — Receives the raw request body without parsing (useful for XML or non-JSON payloads)
For most use cases, "Catch Hook" is the correct choice.
Step 2: Copy the Webhook URL
Zapier generates a unique URL in the format https://hooks.zapier.com/hooks/catch/XXXXX/YYYYY/. Copy this URL. It is the endpoint that external services will send data to. Each Zap receives its own unique URL; the URL persists even if the Zap is edited.
Step 3: Send a Test Request
Send a sample HTTP POST request to the webhook URL using the external application, a cURL command, or a tool like Postman. The request body should contain the data fields the Zap will process. Example cURL command:
curl -X POST https://hooks.zapier.com/hooks/catch/XXXXX/YYYYY/ \
-H "Content-Type: application/json" \
-d '{"name": "Test Lead", "email": "[email protected]", "source": "website"}'
Step 4: Map Fields in Subsequent Steps
After Zapier receives the test request, the parsed fields appear as selectable data in subsequent Zap steps. Map each field to the appropriate action. For example, map email to the "Email" field in a Google Sheets row or a CRM contact creation step.
Step 5: Add Actions and Test the Complete Zap
Add one or more action steps (send email, create CRM contact, add spreadsheet row, post Slack message). Run the test for each step to verify data flows correctly. Once all steps pass, turn the Zap on.
Security Considerations
- Webhook URLs are public and unprotected by default. Anyone with the URL can trigger the Zap.
- To add authentication, use the "Catch Hook" trigger with a query string parameter as a shared secret:
https://hooks.zapier.com/hooks/catch/XXXXX/YYYYY/?secret=your_token. Add a Filter step to check the secret before proceeding. - Rotate the webhook URL by deleting and re-creating the trigger if the URL is compromised.
Common Use Cases
- Receiving form submissions from custom websites
- Processing payment events from Stripe or PayPal webhooks
- Triggering workflows from internal tools or scripts
- Connecting legacy systems that support HTTP but not native Zapier integrations
Limitations
- Zapier webhooks have a 30-second timeout for incoming requests as of April 2026
- Maximum payload size is 10 MB
- Webhook triggers count toward the Zap task limit on each plan
Related Questions
Related Tools
Zapier
Automate workflows between apps without coding—connect 9,000+ tools with simple, reliable automation.
Workflow AutomationMake
Automate your work with visual workflow builder and AI agents
Workflow Automationn8n
Workflow automation for technical teams
Workflow AutomationActivepieces
No-code workflow automation with self-hosting and AI-powered features
Workflow AutomationRelated Rankings
Best Human-in-the-Loop Automation Platforms 2026
Eight platforms are ranked here on a single mechanism: how a person enters an automated path, and what the system can prove afterward about the decision they made. Moxo scores 7.7 and ranks first; Camunda 8 scores 7.2, Microsoft Power Automate 7.1, Pega 6.9, n8n 6.7, Zapier 5.9, Kissflow 5.8 and ServiceNow 4.8, scored 22 September 2026 on the five weighted criteria. Those criteria cover the step type, the approver's account or licence, the routes available on a rejection, the audit record, and the meter that charges for the decision, and none of them can tell a review from a rubber stamp, so the methodology adds a check readers can run on any product in a few minutes: whether the decision record tells a considered approval from an instant one. Every figure was read from a vendor-owned surface and carries its own date.
Best Automation Platforms for AI Orchestration 2026
This ranking answers one question: how many real business applications can an AI agent act on out of the box? It evaluates nine platforms as of August 2026 on the reach they give an agent, not on the workflow logic they can express. That boundary is deliberate, because two neighbouring pages on this site answer different questions. Best Process Orchestration Platforms 2026 scores multi-step process control, error handling and state management. Best AI Agent Platforms 2026 scores building and hosting the agent itself. This page scores the layer between them: the connective tissue that lets an agent already built elsewhere reach the applications a business actually runs on. A platform that leads one of those pages can place low here, and two of them do. Scores derive from application and action catalogue counts, the exposure model each platform uses to publish those catalogues to an agent, setup effort, failure handling and cost per agent action. Every figure was retrieved from a vendor-owned surface on 11 August 2026 unless an earlier date is stated against it.
Dive Deeper
Moxo vs Gumloop in 2026: Texting the Client, or Building the Agent
Gumloop (founded 2023) builds AI agents a company's own staff run; Moxo, whose predecessor Moxtra was co-founded in 2012, runs processes that wait on people outside the company. Gumloop wins three rounds to two: the way in, per-tool gating and a priced overage. Moxo wins on texting a client a step and on what that client can be asked to do. Vendor pages and docs were read on 28 September 2026.
Moxo vs Relay.app in 2026: Where Relay's Approval Workflows Can Go Next
Relay.app, founded in 2021, shut down in September 2026 and deleted every account, workflow and run history; Moxo, whose predecessor Moxtra was co-founded in 2012, is one destination for its human-in-the-loop users. Relay.app takes two rounds, Moxo one, and vendor risk is a draw. The page maps which Relay steps Moxo replaces, on which plan, and what the shutdown teaches about exports, from sources read 28 September 2026.
Moxo vs Workato in 2026: The Integration Estate, or the Approval Inside It
Workato, founded in 2013, is an enterprise integration platform whose Workflow apps add human tasks to recipes; Moxo, whose predecessor Moxtra was co-founded in 2012, ships the human step itself. Workato wins three rounds to two: connector reach, change control and the way in. Moxo wins the human step and retries. Vendor pages and docs were read on 28 September 2026.