Someone scans your QR code or clicks your short link, and a message appears in the Teams channel you chose — which code, where it points, when, and from what device. No new tab to watch, no waiting for the weekly analytics round-up.
xengo posts to Teams through the standard incoming-webhook mechanism — no bot to register, no Graph API permissions, no app submission to your tenant catalogue. Create the webhook, paste the URL, send a test.
In Teams, open the channel that should hear about scans, then add an Incoming Webhook to it (via the channel's Connectors, or the Workflows webhook template on newer tenants). Teams hands you a webhook.office.com URL.
Console → Notifications → Add channel → Microsoft Teams. Paste the URL into the Incoming Webhook URL field, name the channel, save — then hit Send test and watch the message land.
Attach the Teams channel to the links and QR codes that should report there — campaign links to Marketing, warehouse labels to Operations. Routing lives on the link, so a code only posts where you've pointed it.
The Teams channel lives on the console's Notifications page with the other 23 channel types — named, counted, pausable. Add one per Teams channel and keep Marketing and Operations cleanly apart.
Every post to Teams is written to the delivery log with its HTTP response code and attempt number. When someone asks whether the alert fired during the outage, you look it up rather than guess.
The redirect fires, the event is processed, and Teams gets the message — typically within a couple of seconds of the scan itself.
Link title, short URL, click vs QR scan, destination, timestamp, device and your tags — enough context that nobody has to open the console to understand it.
Teams webhook URLs are validated at set-up and must be HTTPS — a mistyped URL fails when you save it, not silently in production.
If the post fails, xengo retries on a backoff ladder — up to six attempts spanning roughly 43 minutes — and logs every attempt.
Tag links with campaign, region or asset codes and each Teams message includes them, so a busy channel still reads unambiguously.
The same scan can also start a Power Automate flow with the full signed JSON event — Teams for eyes, flows for actions.
No bot and no app registration. xengo posts through Teams' standard incoming-webhook mechanism, so the only requirement is being able to add a webhook to the channel — depending on your tenant's policy that's something any channel member can do.
xengo POSTs a simple JSON text message to whatever URL you paste. Classic Connector-style webhooks accept that directly. A Workflows-created webhook works when its flow accepts a plain JSON message — some Workflows templates expect an Adaptive Card payload instead, so hit Send test after saving and you'll know in seconds whether yours does.
Yes. Create one xengo channel per Teams destination — each with its own webhook URL — then attach them per link or QR code. If one channel should see everything, tick it on every link: routing always lives on the link, so nothing posts anywhere by accident.
No. Teams incoming webhooks are Microsoft-hosted URLs that ignore extra headers, so signing them would prove nothing and we don't pretend otherwise. If you need verifiable deliveries, run the signed generic webhook or Power Automate channel alongside — the same scan feeds both.
The attempt is logged with its response code and retried on a backoff ladder — 30 seconds, 2 minutes, then longer gaps, up to six attempts in total. Email is the only channel xengo deliberately never retries; Teams isn't it.
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 between you and the first message.
