n8n vs Make: Webhook Automation Comparison

Comparison matrix

ROI metrics

For a 10-person engineering team handling high-frequency webhooks, n8n's fixed hosting model saves $1,668 annually compared to Make's per-operation cloud tiers.

Step-by-step setup guide

1. 1.Define Inbound Webhook Trigger in n8n

   Create a Webhook node in the n8n canvas. Configure the HTTP Method to POST and define the path. Set Response Mode to 'Using Respond to Webhook Node' to decouple processing latency from the HTTP 200 acknowledgment.

   curl -X POST https://your-instance.app.n8n.cloud/webhook/v1/orders -H "Content-Type: application/json" -d '{"order_id":"ord_9921","amount":120.50}'

2. 2.Verify Payload Signature with Code Node

   Route raw headers and binary body into an n8n Code node to compute an HMAC-SHA256 signature using the crypto library, rejecting invalid origins with an HTTP 401 status.

   const crypto = require('crypto');
   const signature = $input.first().json.headers['x-signature-sha256'];
   const secret = $env.WEBHOOK_SECRET;
   const hmac = crypto.createHmac('sha256', secret).update(JSON.stringify($input.first().json.body)).digest('hex');
   if (signature !== hmac) {
     throw new Error('Invalid HMAC signature');
   }
   return $input.first();

3. 3.Provision Webhook Receiver in Make

   Add a 'Custom Webhook' module in Make. Click 'Add', supply a name, and copy the auto-generated hook URL. Make initiates a listening state to inspect the data structure from an initial test ping.

   curl -X POST https://hook.eu1.make.com/abc123xyz456 -H "Content-Type: application/json" -d '{"event":"customer.created","data":{"id":"cus_883"}}'

4. 4.Map JSON Payload and Filter Anomalies

   Use Make's Visual Data Mapper to extract nested parameters, or use n8n's Expression Engine ($json.body.data.id). Apply a condition or filter node to drop zero-value transactions or ping events.

   {
     "rule": "$json.body.amount > 0",
     "discard_on_false": true
   }

5. 5.Configure Webhook Acknowledgment Response

   Send an explicit synchronous JSON response back to the caller within 3 seconds to prevent origin timeouts, returning transaction trace identifiers.

   {
     "status": 200,
     "headers": {"X-Processed-By": "integration-gateway"},
     "body": {"status": "acknowledged", "received_at": "2024-03-29T12:00:00Z"}
   }

Webhook payload example

{
  "event": "workflow.execution.success",
  "executionId": "401289",
  "workflowId": "wflow_webhook_ingest_01",
  "workflowName": "Stripe Webhook Gateway",
  "mode": "webhook",
  "startedAt": "2024-03-29T14:22:10.120Z",
  "stoppedAt": "2024-03-29T14:22:10.450Z",
  "durationMs": 330,
  "status": "success",
  "retryOf": null,
  "data": {
    "resultData": {
      "runData": {
        "Respond to Webhook": [
          {
            "startTime": 1711722130300,
            "executionTime": 12,
            "source": [],
            "data": {
              "main": [
                [
                  {
                    "json": {
                      "received": true,
                      "txId": "tx_9940182"
                    }
                  }
                ]
              ]
            }
          }
        ]
      }
    }
  }
}

FAQ