The moment someone clicks your link or scans your QR code, a readable message lands in the Slack channel you chose — what was scanned, where it points, when, and from what device. No polling, no digest emails, no dashboard vigil.
Slack's Incoming Webhooks are the simplest thing the platform does, and we lean on that: no OAuth dance, no app to install, no scopes to review. If you can paste a URL, you're done.
In Slack: Apps → Incoming Webhooks → pick the channel that should hear about scans (#marketing, #sales-alerts, #ops — your call). Slack gives you a hooks.slack.com URL.
Console → Notifications → Add channel → Slack. Paste the webhook URL, name it, save — then hit Send test and watch it land in the channel.
Attach the channel to the links and QR codes it should hear about — proposals to the sales channel, event signage to the events channel. Each code carries its own channel list.
Slack sits alongside 23 other channels in the console's Notifications page — add it once, see its send count, last delivery and status at a glance, and pause it without deleting anything.
Notifications attach per link. Open any link, tick the Slack channels that should hear about it, and the next scan posts there — and only there.
The scan hits our redirect plane, the event is processed, and Slack receives the message — typically inside a couple of seconds.
Link title, short URL, source (click vs QR scan), destination, timestamp, device and your own tags — context, not just a ping.
Tag a link with campaign, SKU or site codes and every Slack message carries them — readable routing context for free.
Slack webhook URLs are validated and must be HTTPS — a misconfigured channel fails loudly at set-up, not silently at 2am.
Every attempt is recorded in the delivery log with its response code, so 'did Slack get it?' has a factual answer.
The same scan can also fire a signed webhook, page on-call or start a Zap — channels stack, they don't compete.
No. xengo posts through Slack's standard Incoming Webhooks, so there's no app installation, no OAuth grant and no admin approval beyond creating the webhook itself. If your workspace allows Incoming Webhooks, you're two minutes away.
Yes. Create one xengo channel per Slack destination (each with its own webhook URL), then attach them per link or QR code — each code carries its own channel list, so nothing posts anywhere you didn't choose.
The link's title, the short URL, the source (direct click or QR scan), the destination, the time (UTC), and — where available — the device, referrer, IP and your custom tags. It's the same context the analytics page records.
No — Slack's Incoming Webhooks are Slack-owned URLs that ignore extra headers, so signing would be theatre and we don't pretend otherwise. If you need cryptographic verification, use the signed generic webhook alongside Slack; the same scan can feed both.
The attempt and its response are recorded in the delivery log. Email is the only channel we deliberately never retry; webhook-style channels — Slack included — get retried on a backoff ladder for up to six attempts.
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 webhook URL and watch the first message arrive.
