When a QR code is scanned or a link is clicked, the space you picked gets a message with the whole story — the code, the destination, the time, the device. If your company runs on Google Workspace, scan alerts belong in Chat, not in another inbox or another dashboard tab.
Google Chat lets any space owner add an incoming webhook from the space's settings — no Marketplace app, no OAuth consent screen, no admin console visit. xengo just needs the URL Chat gives you.
In Google Chat, open the space → click the space name → Apps & integrations → Webhooks → Add webhook. Name it (say, 'xengo scans') and copy the chat.googleapis.com URL.
Console → Notifications → Add channel → Google Chat. Drop the URL into the Webhook URL field, name the channel, save — then press Send test and see it appear in the space.
Attach the channel to the links and QR codes that should post there — the launch campaign to #launch, the office door code to #facilities. Routing lives on the link, so each code reports only to its spaces.
Open any link in the console and tick the Google Chat channels that should hear about it. The next scan posts there — and nowhere it shouldn't. No global firehose unless you actually want one.
Every fact in the Chat message — source, destination, device, tags — is the same fact the analytics page records. The space gives you the moment; analytics gives you the pattern.
The event flows from the redirect plane to Google's webhook endpoint typically within a couple of seconds — fast enough to act on, not just file.
Link title, short URL, click vs scan, destination, UTC timestamp, device and your custom tags — the message stands on its own.
Google Chat webhook URLs are validated as HTTPS when you save the channel, so a paste error surfaces immediately.
A failed post is retried with growing backoff — up to six attempts over roughly 43 minutes — and every attempt is visible in the delivery log.
Add as many Google Chat channels as you have spaces. Each keeps its own name, send count and pause switch in the console.
The same scan can simultaneously fire a signed webhook, a Zap or an email — channels stack rather than compete.
The webhook does — Google exposes incoming webhooks on spaces in Workspace, and space managers can add them from Apps & integrations. On the xengo side there's no Google account involved at all; we just POST to the URL you paste.
No. There's no xengo app to install and no OAuth grant to approve. The integration is Chat's own incoming-webhook feature plus one pasted URL — which also means there's nothing for an admin to review or revoke beyond the webhook itself.
Yes. Create a webhook in each space, add each URL as its own xengo channel, and attach them per link or QR code. If one space should see everything, tick that channel on every link — routing always lives on the link itself.
No. The space webhook is a Google-owned URL that ignores extra headers, so signature headers would be theatre. If you need cryptographic proof of origin, add the signed generic webhook alongside the Chat channel — one scan, both deliveries.
The attempt and its HTTP response are recorded in the delivery log, and xengo retries on a backoff ladder for up to six attempts. You can answer 'did the space get it?' from the log, not from memory.
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. Webhook from Chat, paste into xengo, watch the test message land.
