Badge a meeting room, tag a piece of equipment, put a QR code on the event stand — and the instant anyone scans it, the Webex space you chose gets the message: which code, where it points, when, from what device. Teams that run on Webex shouldn't have to check a separate dashboard to know their codes are working.
Webex's Incoming Webhooks integration turns any space into an endpoint — no bot to build, no Webex developer account, no admin change request. Connect it to a space, and xengo posts straight in.
Open the Incoming Webhooks integration on Webex App Hub, sign in, name the webhook and choose the space that should receive scan alerts. Webex gives you a webexapis.com URL.
Console → Notifications → Add channel → Webex. Paste the URL into the Incoming Webhook URL field, name the channel, save — then press Send test and see it arrive in the space.
Attach the channel to the links and QR codes that should report to that space — facilities codes to the estates space, campaign links to marketing. Routing is set per link, so each code posts only where it belongs.
Each Webex space is its own named channel on the console's Notifications page, next to whatever else you run — with send counts, last-delivery timestamps and a pause switch that keeps the configuration intact.
The message in the space and the analytics page describe the same event with the same facts — source, destination, device, tags. Webex tells you it happened; analytics tells you how often and from where.
The scan hits the redirect plane, the event is processed, and the Webex space gets its message — typically inside two seconds.
Link title, short URL, click vs QR scan, destination, UTC timestamp, device and your custom tags — no console visit needed to understand it.
Webex webhook URLs are validated as HTTPS when you save the channel, so a bad paste fails at setup rather than silently later.
A failed post retries up to six times on a widening ladder — roughly 43 minutes of coverage — with every attempt in the delivery log.
Add as many Webex channels as you have spaces; each keeps its own name, counters and routing, so estates never drowns out marketing.
The same event can also raise a PagerDuty incident or hit a signed webhook — Webex is for the humans, the rest is for the systems.
No. xengo posts through Webex's Incoming Webhooks integration from App Hub — no bot creation, no developer-portal tokens, no code. You connect the integration to a space and paste the URL it gives you.
Yes. Set up the Incoming Webhooks integration once per space, add each URL as its own xengo channel, then attach channels per link or QR code. If one space should see everything, tick that channel on each link — routing always lives on the link.
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 — where available — the device and your custom tags. Identical facts to what the console's analytics record.
No — the incoming webhook is a Cisco-hosted URL that ignores extra headers, so signature headers would prove nothing and we don't add decorative ones. For verifiable deliveries, run the signed generic webhook alongside; one scan feeds both.
The attempt is recorded in the delivery log with its HTTP response, then retried on a backoff ladder — up to six attempts in total. Email is the only channel xengo never retries; Webex gets the full ladder.
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 from App Hub and the test message is in Webex.
