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 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.
Best Durable Workflow Engines for Production in 2026
A ranked list of the best durable workflow engines for production deployments in 2026. Durable workflow engines persist execution state to a database so that long-running workflows survive process restarts, deployments, and infrastructure failures. The ranking covers Temporal, Prefect, Apache Airflow, Camunda, Windmill, and n8n. Tools were evaluated on production reliability, developer experience, scalability, open-source health, and documentation quality. The shortlist intentionally mixes code-first engines (Temporal, Prefect, Airflow) with hybrid visual platforms (Camunda, Windmill, n8n) to reflect how production teams actually choose workflow engines in 2026.
Dive Deeper
Keystroke vs n8n in 2026: Agent-Built TypeScript vs the Visual Canvas
Keystroke, launched in July 2026 by Y Combinator W24 company Sprint Labs, is a code-first automation platform where AI coding agents write workflows as TypeScript in the user's repository. n8n, founded in 2019, is the most widely deployed source-available visual workflow platform, with 200,000+ users and a $2.5 billion valuation. This comparison covers the agent-authored versus canvas building models, durable execution, licensing (Elastic License 2.0 vs the Sustainable Use License), verified July 2026 pricing including Keystroke's usage metering, and the maturity gap between a days-old platform and an established ecosystem.
QuantumBPM vs Camunda 2026: Single-Binary Challenger vs the BPMN Incumbent
QuantumBPM (launched 2026, Coroid s.r.o., Slovakia) packages a BPMN 2.0 runtime and DMN 1.5 decision engine into one Go binary backed by Temporal and PostgreSQL. Camunda (Berlin, founded 2013) is the category incumbent: Camunda 7 (Apache 2.0, in maintenance) and the Zeebe-based Camunda 8 platform. This comparison covers product structure, architecture, DMN TCK conformance with recording dates, deployment, pricing, and vendor maturity, verified July 2026.
Migrating 23 Make Scenarios to Self-Hosted n8n: a 3-Week Breakdown
Anonymized retrospective of a DTC ecommerce brand migrating 23 Make scenarios to a self-hosted n8n instance over three weeks. Tooling cost dropped from $348/month on Make Teams to roughly $12/month on a Hetzner VPS, but credential and webhook recreation consumed about 40% of total project time.