n8n Workflow: Webhook Receiver Template

How This Blueprint Works

Every modern SaaS platform sends webhooks, but consuming them consistently is a challenge. This universal webhook receiver normalizes incoming payloads from any source, validates signatures, transforms data into a standard schema, and routes it to your target system.

The Execution Sequence

1. Webhook Node — A generic webhook node configured to accept POST, PUT, and PATCH methods. Supports both JSON and form-data content types. Can be configured with Basic Auth, Header Auth, or no auth depending on the sending service’s capabilities.
2. Signature Verifier Node — A Code node that validates the incoming request signature if the source supports webhook signing (Stripe, GitHub, Svix, Zapier). Extracts the HMAC-SHA256 hash from the x-hub-signature-256 header and computes the expected hash using the shared secret stored in n8n credentials.
3. Payload Schema Node — A Code node that normalizes the incoming payload into a standardized schema with common fields: {source_platform, event_type, id, timestamp, data, raw}. This ensures downstream processing nodes receive consistent field names regardless of the source platform.
4. Destination Router Node — A Switch node that inspects the source_platform field and routes to the correct handler: “stripe” routes to payment processing workflow, “github” routes to issue creation workflow, “shopify” routes to order processing, etc.
5. Dead Letter Queue Node — Payloads with unrecognized sources, missing required fields, or invalid signatures are appended to a Google Sheet named “Webhook Dead Letters”. Columns: received_at, source_platform, http_method, error_reason, and raw_payload (truncated).

FAQ

What webhook signing schemes are supported?

The Signature Verifier supports HMAC-SHA256 (Stripe, GitHub, Svix), HMAC-SHA1 (older services), and plain token comparison. Extend the Code node to add new verification schemes as needed.

Can I test webhooks before going live?

Yes. n8n provides an ephemeral webhook URL during development. Use tools like RequestBin or Postman to send sample payloads. n8n’s webhook inspector shows each incoming request’s raw body and headers.

How do I handle webhook replays?

Add an idempotency check in the Payload Schema node using the event ID. Store processed event IDs in a Supabase table. If an event ID already exists, complete the workflow without performing any downstream actions.

The JSON Blueprint Structure

{
  "name": "Universal Webhook Ingestion",
  "nodes": [
    { "name": "Webhook", "type": "n8n-nodes-base.webhook", "position": [250, 300] },
    { "name": "Sig Verifier", "type": "n8n-nodes-base.code", "position": [450, 300] },
    { "name": "Schema Mapper", "type": "n8n-nodes-base.code", "position": [650, 300] },
    { "name": "Route Switch", "type": "n8n-nodes-base.switch", "position": [850, 300] }
  ]
}

What You Get Inside Your SynthOperator System

This workflow is one of 27,400+ blueprints included in the n8n Business Automation OS ($17, one-time). When you deploy the complete system, you get:

• 27,400+ pre-built workflow JSON files across every business domain
• 15 elite AI agents integrated into your automation pipelines
• Lifetime updates, offline operation, and zero recurring fees

**Deploy your complete automation infrastructure today.