If you run n8n, you already own the only piece this integration needs: a Webhook trigger node. The moment a link is clicked or a QR code is scanned, the full event — signed, structured, seconds old — POSTs to your instance, and the workflow does the rest on hardware you control.
No community node to vet, no credentials to store in n8n, nothing to update when we ship. We push the event to a URL your Webhook trigger node generates; everything after that is ordinary n8n — IF nodes, Code nodes, three hundred downstream integrations.
In n8n: start a workflow with the Webhook node, set the HTTP method to POST, then activate the workflow and copy its Production URL (the Test URL works for a dry run first).
Console → Notifications → Add channel → n8n. Paste the URL into the Webhook URL field, save, and hit Send test — with the node listening you'll see the event arrive with every field expanded.
Attach the channel to the links and QR codes that should trigger it — asset labels to the maintenance workflow, campaign links to the reporting one.
Your n8n instance sits on the console's Notifications page like any SaaS channel: named, testable with one click, pausable without deleting configuration, with send counts and last-delivery status visible.
Self-hosting means occasional downtime. The delivery log records every POST — first attempt and each retry — with response codes, so you can reconcile against n8n's execution list after the fact.
Not a bare ping: the full scan event — code, source, destination, tags, timestamp, device — arrives at your Webhook URL within seconds of the scan.
Every delivery carries Svix-compatible signature headers
(webhook-id, webhook-timestamp,
webhook-signature) signed with your channel's
whsec_ secret, and failures retry on a backoff
ladder for up to six attempts — with every attempt visible in
the console's delivery log. Verification docs →
{
"event": "click",
"source": "qr",
"code": "spring-launch",
"shortUrl": "go.yourbrand.com/spring-launch",
"title": "Spring launch pack",
"destination": "https://yourbrand.com/spring",
"tags": { "campaign": "spring-24", "sku": "SB-114" },
"createdAt": "2026-05-02T09:14:11Z",
"ts": 1752319441000,
"at": "2026-07-12T10:44:01+00:00",
"ip": "203.0.113.7",
"ua": "Mozilla/5.0 (iPhone; …)",
"referer": null,
"customerId": "cus_9f2k…"
}Unlike the SaaS channels, n8n URLs aren't forced to HTTPS — useful behind your own reverse proxy, though HTTPS remains the sensible default.
Svix-compatible signature headers (webhook-id, webhook-timestamp, webhook-signature) ship on every delivery — a Code node can verify against your whsec_ secret.
No Schedule Trigger polling our API: the event arrives seconds after the scan, and the workflow runs exactly as often as reality demands.
Failed deliveries retry on a 30s/2m/10m/15m/15m ladder; we re-read the channel each attempt, so pausing it stops the retries too.
Code, click-vs-QR source, short URL, destination, tags, timestamp, device, referrer — the full event, not a ping that makes the workflow call back for details.
n8n keeps its execution history; the console keeps the delivery log. Between them, 'did the workflow run for that scan?' is always answerable.
Not yet — a native n8n node is on the roadmap. Today the stock Webhook trigger node ingests our POST natively, which gives you the same instant trigger without installing or trusting third-party node code on your instance.
Deliveries come from our cloud, so the Webhook node's URL must be reachable from the internet — a public hostname, a reverse proxy, or a tunnel. Plain http:// is accepted for n8n channels, but if the URL only resolves on your LAN, the POST can't arrive.
Production. n8n's Test URL only listens while the editor is open, which is handy for the first Send test but wrong for real traffic. Activate the workflow, paste the Production URL, and use Send test again to confirm end to end.
Every delivery carries Svix-compatible signature headers signed with your channel's whsec_ secret, shown once when the channel is created. A Code node can recompute the HMAC and reject anything that doesn't match — or you can rely on the webhook path staying secret.
We retry: six attempts on a backoff ladder covering roughly 43 minutes of outage, each logged with its response code. Delivery is at-least-once and the webhook-id header is stable across retries, so idempotent workflows can de-duplicate cleanly.
Smart URLs, dynamic QR codes and a full API — branded on your own domain, safety-screened, and tracked. Build, re-point and measure it all in one place.
Start free trialBranded short links on a domain you control — editable, screened, and tracked.
Branded QR codes you can re-point any time — never reprint the poster again.
$ curl -X POST api.xengo.io/v1/links { "domain": "go.acme.com", "url": "https://acme.com/…" } → 201 go.acme.com/aB3xK▋
Create and manage links + QR at scale, straight from your own tools.
14-day free trial, card required, cancel anytime. One Webhook node, one paste, done.