Destination type

n8n Destination Configuration

Use the n8n destination to route verified webhook events into published n8n workflows with delivery evidence, retries, replay, authentication, and throughput control. This destination configuration reference covers the fields and delivery behavior required to connect it to FastHook.

For n8n destinations, FastHook delivers to the published Production Webhook URL and stores response status, body, latency, retry, and replay evidence.

N8NPublished n8n Webhook nodePOST, PUT, PATCH, DELETEAutomation
All destination typesDestinations docs
n8n destination delivery flowFastHook routes accepted events through a connection to a n8n destination and stores delivery attempt evidence.AcceptedRequestsource verifiedConnectionRoute branchfilters and transformsretry policyN8Nn8nPublished n8n Webhook nodePOST, PUT, PATCH, DELETEAttemptEvidencestatus + bodyDestination config owns target, auth, method, rate limit, disabled state, and delivery attempt evidence.

n8n dashboard fields

n8n Production Webhook URL

The Production URL from the published n8n Webhook node.

HTTP method

The method configured on the n8n Webhook node.

Destination auth

How FastHook authenticates each delivery to n8n.

Max delivery rate

Optional pacing to protect n8n workers and downstream workflow dependencies.

n8n API config

config.url

The n8n Production Webhook URL that receives routed deliveries.

config.http_method

Outbound method expected by the n8n Webhook node: POST, PUT, PATCH, or DELETE.

config.auth_type

Authentication mode used when FastHook calls the n8n workflow.

config.auth

Custom header, OAuth2, or FastHook signature settings for the n8n receiver.

config.rate_limit

Optional maximum number of workflow executions in the selected period.

config.rate_limit_period

Rate-limit period: second, minute, or hour.

n8n destination config
{
  "name": "orders-to-n8n",
  "type": "N8N",
  "config": {
    "url": "https://n8n.example.com/webhook/orders",
    "http_method": "POST",
    "auth_type": "FASTHOOK_SIGNATURE",
    "auth": {},
    "rate_limit": 10,
    "rate_limit_period": "second"
  }
}

n8n authentication

  • No auth
  • FastHook signature
  • Custom header
  • OAuth2 client credentials
  • OAuth2 authorization code

n8n delivery method and limit

POSTPUTPATCHDELETE

Rate limit: Optional. Limit workflow starts per second, minute, or hour.

n8n delivery behavior

  • Use the Production Webhook URL from n8n. Test URLs listen temporarily and should not be used for durable FastHook delivery.
  • FastHook stores the n8n response status, body, latency, and attempt evidence for every routed event.
  • Custom header auth is a simple way to protect an n8n Webhook node; OAuth2 and FastHook signatures are available for more controlled receivers.
  • After fixing or publishing a workflow, retry or replay the affected FastHook events instead of asking the provider to resend them.

n8n setup checklist

  1. Add a Webhook node to n8n, save the workflow, and publish it.
  2. Create a FastHook destination and choose n8n as the destination type.
  3. Paste the n8n Production Webhook URL and select the same HTTP method as the Webhook node.
  4. Configure destination authentication and an optional max delivery rate.
  5. Connect one or more FastHook sources to the destination, send a test event, and inspect the delivery attempt.

n8n troubleshooting

n8n returns 404 or the workflow does not run.

Confirm the destination uses the Production Webhook URL and that the n8n workflow is published and active.

n8n returns 401 or 403.

Check destination authentication and match the custom header or OAuth settings configured on the n8n Webhook node.

The workflow fails or times out after accepting the request.

Inspect the n8n execution, fix the workflow or dependency, then retry or replay the corresponding FastHook event.

Related docs