Skip to main content

​
Notify External Systems on Every Click

Webhook nodes make HTTP requests to external URLs as part of the rule evaluation. When the edge worker hits a webhook node, it queues a request to your endpoint and continues to the next node — keeping the redirect fast while your backend processes the event asynchronously.

POST or GET

Choose between POST and GET methods. POST sends a JSON payload with visitor context; GET is a simple ping.

Custom Headers

Add custom HTTP headers to the webhook request — authentication tokens, content types, or any metadata your endpoint expects.

Non-Blocking

Webhook calls are queued and fired asynchronously. They don’t add latency to the redirect — the visitor is redirected immediately.

Combine with Rules

Place webhook nodes after conditions or splits to fire different webhooks based on which rule branch was matched.

​
How It Works

  1. The edge worker evaluates the rule tree until it reaches a webhook node
  2. The webhook URL, method, and headers are queued for asynchronous execution
  3. Evaluation immediately continues to the next node — no waiting for the webhook response
  4. After the redirect is served, the queued webhooks fire in the background

​
Setting Up a Webhook

1

Create or edit a link

Set the link type to Rules and open the flow editor.
2

Add a webhook node

Drag a webhook node onto the canvas and wire it into your rule graph.
3

Configure the endpoint

Enter the webhook URL and select the HTTP method (POST or GET).
4

Add custom headers (optional)

Add any headers your endpoint requires — for example, an Authorization header with a bearer token.
5

Connect the next node

Wire the webhook node’s output to the next node. The webhook fires in the background while the visitor continues through the graph.
Header values cannot contain newline characters. Middlewr validates this at save time.

​
Use Cases

​
Real-time event tracking

Notify your analytics backend whenever a visitor clicks a link, with full visitor context:

​
Conditional notifications

Fire webhooks only when specific conditions are met — notify your team when high-value traffic segments are detected:

​
Workflow triggers

Trigger automations in external tools (Zapier, n8n, Make) based on link clicks:

​
Per-branch webhooks

Fire different webhooks based on which rule branch was taken, sending branch-specific data to your backend:

​
Next Steps

Rule Engine

Understand how webhook nodes fit into the full compilation and evaluation pipeline.

Edge Transforms

Inject query parameters or headers alongside webhook notifications.