Merch table QR, link-in-bio, ticket drop, sticker on a lamppost — the instant it's used, a message hits the Discord channel you chose, with the code, the destination, the time and the device. Your community team sees it live instead of discovering it in next week's analytics.
Discord webhooks are built into every server — no bot to add, no permissions to scope, no slash commands to learn. If you can edit a channel, you can have scan alerts in it two minutes from now.
Server Settings → Integrations → Webhooks → New Webhook (or Edit Channel → Integrations on the channel itself). Pick the channel, name it, set its avatar if you like, and copy the webhook URL.
Console → Notifications → Add channel → Discord. Paste into the Webhook URL field, name the channel, save — then hit Send test and watch it post to the server.
Attach the webhook to the links and QR codes it should hear about — merch codes to #merch, event posters to #events, mod-only codes to a private channel. Routing is per link, so each code posts only where you pointed it.
Each Discord destination is its own named channel on the Notifications page — with a send count, a last-delivery timestamp and a pause switch. Run one for the public server and another for the staff server without them tangling.
The links page shows every short link and QR code with its scan counts, so the Discord pings always trace back to a specific, named code — not a mystery URL someone made in a hurry.
From scan to server message is typically a couple of seconds — quick enough to greet the person still standing at your stall.
Code title, short URL, click vs QR scan, destination, timestamp, device and your tags — a message the channel can act on without asking questions.
The name and avatar the message posts under are set on the webhook in Discord — so alerts can look like your brand, not like plumbing.
Discord webhook URLs are checked at set-up and must be HTTPS, so a broken paste fails when you save it, not during the drop.
A failed post goes onto a backoff ladder — up to six attempts across roughly 43 minutes — with every attempt logged.
The same scan can also start a Zap, fire a signed webhook or push to your phone. Discord is a listener, not the only one.
No. xengo posts through Discord's native channel webhooks, so there's no bot to invite, no role to configure and no OAuth screen. Anyone with Manage Webhooks permission on the channel can set it up.
Yes. Create a webhook per channel in Discord, add each as its own xengo channel, and attach them per link or QR code. A public #drops channel and a private staff channel can hear about completely different codes.
A plain, readable message: the code's title, the short URL, whether it was a direct click or a QR scan, the destination, the time and the device, plus any tags you set. It posts under the webhook's own name and avatar. No embeds, no formatting surprises.
No — Discord webhooks are Discord-owned URLs that ignore extra headers, so signing them would prove nothing. If you're building something that must verify origin, use the signed generic webhook alongside the Discord channel; the same scan feeds both.
Each attempt is recorded in the delivery log with its response code, and xengo retries on a backoff ladder for up to six attempts. If Discord comes back inside that window, the message still lands — and either way, the log tells you exactly what happened.
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 URL and the first test message is in your channel.
