n8n Webhooks: The Complete Guide to Triggering Workflows via HTTP (2026)

Webhooks are the backbone of real-time automation. Instead of polling an API every 5 minutes — burning API quota and adding latency — webhooks fire the instant something happens. A Stripe payment completes. A GitHub issue opens. A Typeform is submitted. Your n8n workflow wakes up immediately.

This guide covers everything: receiving webhooks, validating payloads, securing endpoints, handling failures, and building webhook-driven architectures.

Why Webhooks Over Polling?

| | Polling (Schedule Trigger) | Webhooks | |---|---|---| | Latency | Up to your poll interval (5-15 min) | Instant (<1 second) | | API Quota | Burns quota on every poll, even when nothing changes | Only fires when there's data | | Reliability | Misses events between polls | Captures every event | | Server Load | Your server works on every poll | Server only works on events |

If the service supports webhooks, use webhooks. n8n's Webhook node makes this trivial.

The Basics: Creating a Webhook Endpoint

Add a Webhook node as your trigger. n8n generates a unique URL:

https://your-n8n-instance.com/webhook/abc123

Choose your HTTP method. Most services send POST with a JSON body, but n8n supports GET, PUT, PATCH, and DELETE too.

Production tip: Under "Options," set the Response Mode to "Last Node" so the webhook caller gets a proper HTTP response when your workflow finishes — critical for services that require a response (like Slack).

Production Pattern #1: Stripe Payment → Invoice

Services that send webhooks: Stripe, Shopify, GitHub, Typeform, Calendly, Twilio

Here's the Stripe pattern:

1. Webhook node receives payment_intent.succeeded
2. Set node extracts customer email, amount, payment ID
3. HTTP Request node fetches full customer details from Stripe API
4. HTML node builds an invoice template
5. Convert to PDF node renders it
6. Email node sends it to the customer

The entire pipeline fires the instant payment completes — no polling, no delay.

FlowForge template: Stripe Payment → Invoice + Email Receipt

Production Pattern #2: GitHub → Project Board

When a GitHub issue is labeled "bug," automatically create a Trello card on the "Bugs" list and assign it to the on-call engineer:

1. Webhook node receives GitHub issue event
2. IF node checks label === "bug"
3. Trello node creates card with issue title, body, and GitHub link
4. Slack node notifies #engineering channel

FlowForge template: GitHub Issue → Trello Card

Securing Webhook Endpoints

By default, anyone with your webhook URL can trigger your workflow. Three ways to lock it down:

1. Webhook Secret / Signature Verification

Most platforms (Stripe, GitHub, Shopify) include a signature header. In n8n:

// In a Function node after the Webhook node
const crypto = require('crypto');
const payload = JSON.stringify($input.first().json);
const signature = $input.first().headers['x-hub-signature-256'];
const computed = 'sha256=' + crypto
  .createHmac('sha256', $env.WEBHOOK_SECRET)
  .update(payload)
  .digest('hex');

if (signature !== computed) {
  throw new Error('Invalid signature');
}
return $input.first();

2. IP Allowlisting

Restrict which IPs can hit your webhook URL at the reverse proxy level (Caddy/Nginx).

3. Webhook Path Randomization

Use n8n's "Webhook Suffix" option to add a random string to the URL path — a basic but effective measure against scanners.

Handling Webhook Failures

Webhooks can fail. The calling service might retry, so your workflow must be idempotent — processing the same event twice shouldn't create duplicates.

Pattern: Idempotency key check

// Check if we've already processed this event
const eventId = $input.first().json.id;
const existing = await $json.getWorkflowStaticData('global');
if (existing[eventId]) {
  return null; // Skip — already processed
}
existing[eventId] = new Date().toISOString();

Webhook vs Webhook Node: Which One?

n8n has two webhook-related nodes:

• Webhook — Generic HTTP receiver. Use this for custom webhooks, form submissions, and any service that posts to a URL.
• Webhook (app-specific) — Some app nodes (GitHub, Stripe) have built-in webhook triggers. These auto-parse the payload and handle authentication.

Rule of thumb: Use the app-specific node when it exists. Fall back to the generic Webhook node for everything else.

Testing Webhooks Locally

Use webhook testing services during development:

# webhook.site — generates a temporary URL for testing
# requestbin.com — inspect request payloads
# ngrok — tunnel your local n8n to a public URL
ngrok http 5678

Then point Stripe/GitHub at the ngrok URL while developing.

Building Webhook-Driven Pipelines

The real power comes from chaining. A single webhook can trigger a cascade:

Example: New Customer Onboarding Pipeline

1. Typeform submitted → webhook fires
2. Create contact in HubSpot
3. Send welcome email via Gmail
4. Notify Slack #new-customers
5. Create onboarding task in Notion
6. Schedule 48-hour follow-up email

All from one webhook. All instant. All automatic.

When NOT to Use Webhooks

• The source service doesn't support webhooks (use polling with HTTP Request node)
• You need historical/replay capability (webhooks are fire-and-forget)
• The event volume is extremely high (10,000+/minute) — consider a message queue instead

Ready to Build?

Webhooks are the fastest path to real-time automation. Start with a simple form → webhook → Google Sheets workflow today.

Browse FlowForge webhook-driven templates →

Every template includes the webhook configuration, payload parsing, and production security setup.