n8n Webhook Tutorial: Receive External Data in Your Workflows

February 2, 2025 · 8 min read

Webhooks are the backbone of real-time automation. Instead of polling APIs every few minutes, webhooks let external services push data to your n8n workflow the instant something happens.

This guide walks you through setting up webhooks in n8n — from the basic trigger node to production-ready patterns with authentication, error handling, and response customization.

What Is a Webhook?

A webhook is an HTTP endpoint that waits for incoming requests. When another service sends data to that URL, your workflow triggers immediately.

Think of it as a doorbell: instead of checking if someone's at the door every 5 minutes (polling), you wait for the bell to ring (webhook).

Step 1: Add the Webhook Trigger Node

In n8n, create a new workflow and add a Webhook node as the trigger (first node).

The Path becomes part of your webhook URL. With a path of /my-webhook, your full URL will be something like:

Step 2: Test with a Sample Request

Before connecting a real service, test your webhook manually. Click "Listen for Test Event" in n8n, then send a test request:

n8n should show the received data in the webhook node output. You can now use{{ $json.name }} and{{ $json.email }} in downstream nodes.

Step 3: Process the Data

After the webhook receives data, add nodes to process it. Here's a common pattern:

1. Webhook → receives the incoming data
2. IF node → validate the data (check required fields exist)
3. Set node → transform/rename fields as needed
4. Action node → save to database, send email, call API, etc.
5. Respond to Webhook → send a response back to the caller

Step 4: Add Authentication

In production, you don't want anyone to trigger your webhook. n8n supports several auth methods:

Header Authentication

Set a secret header that callers must include:

Any request without the correct header gets rejected with a 403.

HMAC Signature Verification

For services like GitHub and Stripe that sign webhook payloads, use an IF node or Code node to verify the HMAC signature before processing.

Step 5: Handle Errors Gracefully

Webhooks in production will receive malformed data, duplicate events, and unexpected payloads. Build for it:

• Validate early: Check required fields in the first node after the webhook
• Respond fast: Many services timeout after 5-30 seconds. Acknowledge receipt quickly, then process asynchronously if needed
• Handle duplicates: Some services send the same event multiple times. Use an ID field to deduplicate
• Log failures: Use the Error Trigger node to catch and log any workflow failures

Step 6: Customize Your Response

With Response Mode: Last Node, whatever your final "Respond to Webhook" node outputs becomes the HTTP response. This is powerful:

Production Checklist

Common Gotchas

Next Steps

Now that you have webhooks working, you can build powerful real-time automations. Check out our workflow templates for production-ready examples, or read our guide on connecting n8n to AI with MCP servers.