How to set up webhooks in Zapier

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