Someone scans your QR code or clicks your link, and the full event — code, source, destination, tags, device — hits your Zap's Catch Hook within seconds. Whatever Zapier connects to is downstream: a Sheets row, a CRM update, a text to the rep. No polling interval, no dashboard refresh.
Webhooks by Zapier exists precisely so tools like ours can push events in. We POST the moment the scan happens, Zapier catches it, your Zap runs — the same instant trigger a native app would give you, by mechanism rather than marketplace.
In Zapier: Create Zap → choose Webhooks by Zapier as the trigger → event Catch Hook. Zapier hands you a hooks.zapier.com/hooks/catch/… URL — copy it.
Console → Notifications → Add channel → Zapier. Paste the URL into the Catch Hook URL field, save, then hit Send test — the sample request lands in your Zap editor, ready for field mapping.
Open a link or QR code and tick the channel — its scans start that Zap. Packaging codes feed the ops Zap, campaign links the marketing one.
Your Zapier channel sits on the console's Notifications page next to Slack, PagerDuty and the rest: named, paused or resumed at will, with send counts and last-delivery status at a glance.
Channels attach per link. Open any link, tick the Zapier channels that should hear about it, and the next scan triggers that Zap — and only that Zap.
Not a bare ping: the full scan event — code, source, destination, tags, timestamp, device — arrives at your Catch Hook 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…"
}The event is POSTed the instant the redirect fires. Your Zap doesn't wait on a polling schedule — it starts within seconds of the scan.
Code, source (click vs QR), short URL, destination, tags, timestamp, device — each arrives as a structured field the Zap editor can map into any action.
Deliveries carry Svix-compatible signature headers keyed to your channel's whsec_ secret, so a code step can prove the request came from us.
A failed delivery retries on a backoff ladder — six attempts over ~43 minutes — and the webhook-id stays constant, so duplicates are detectable.
The Catch Hook URL is validated as HTTPS at set-up. A typo fails loudly when you save, not silently when the campaign is live.
Every attempt — first try and each retry — is logged with its response code, so 'did the Zap fire?' has a factual answer in the console.
Not yet — a native Zapier app is on the roadmap. Today you paste a Catch Hook URL from Webhooks by Zapier, which is Zapier's built-in way of ingesting exactly this kind of push. Mechanically it behaves like an instant trigger: we POST the moment the scan happens.
Zapier lists Webhooks by Zapier as a premium built-in tool, so check what your Zapier plan includes. On the xengo side there is nothing extra: every plan can add Zapier channels.
Everything in the event: the code, whether it was a direct click or a QR scan, the short URL, the destination, the timestamp, the device user-agent, the referrer, and any custom tags you put on the link — campaign, SKU, site, whatever you tagged.
It can, rarely. Delivery is at-least-once: if Zapier accepts a request but the response times out, we retry rather than risk dropping the event. The webhook-id header is identical across retries of the same scan, so a filter or code step can de-duplicate on it.
Yes. Create one xengo channel per Catch Hook, then attach channels per link or QR code. A warehouse label can start an inventory Zap while a conference badge starts a lead-capture one — same account, separate Zaps.
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. Paste one Catch Hook URL and watch the Zap fire.