Destination type

n8n Destination

Use the n8n destination to route verified webhook events into published n8n workflows with delivery evidence, retries, replay, authentication, and throughput control.

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.
For n8n destinations, FastHook delivers to the published Production Webhook URL and stores response status, body, latency, retry, and replay evidence.

When to use this destination type

Choose N8N when the receiver target is Published n8n Webhook node. Destinations are outbound delivery targets: they do not decide whether a source request should be accepted, and they do not own connection filters or transformations. They own where the final delivery goes and how FastHook should authenticate, pace, disable, and inspect that delivery.

A destination can be reused by multiple connections when several source branches should feed the same receiver. Reuse keeps receiver capacity, credentials, and attempt evidence attached to one destination id.

FastHook dashboard fields

In the dashboard, create a destination, set Destination Type to N8N, then fill the fields below.

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.

API config fields

The REST API stores destination-specific behavior under config. Use PATCH for focused edits and PUT only when your request contains the full config you want to keep.

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"
  }
}
Create n8n destination with cURL
curl -X POST "https://api.fasthook.io/v1/destinations" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "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"
  }
}'

Authentication

Destination authentication is outbound. It helps the receiver trust or accept FastHook delivery, and it is separate from source authentication that verifies the original webhook producer.

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

HTTP methods and rate limit

This destination type uses the methods below for delivery attempts. Rate limits apply at the destination boundary, so every connection that targets the same destination shares that capacity.

POSTPUTPATCHDELETE

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

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.

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.

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