Put a dynamic QR code on the thing you worry about — the tamper seal, the plant-room door, the decommissioned rack — and the moment it's scanned, xengo triggers a PagerDuty incident through Events API v2. Your escalation policies and on-call schedules take it from there; the analytics keep the full history.
No email-to-PagerDuty bridge, no marketplace app, no OAuth grant. xengo posts the trigger event directly to PagerDuty's Events API v2 with the routing key you paste — the same integration path your monitoring stack already uses.
In PagerDuty: open the service that should own these incidents → Integrations → Add integration → Events API v2. Copy the Integration Key it generates — that's your routing key.
Console → Notifications → Add channel → PagerDuty. Paste the key into the Integration / routing key field, save — then hit Send test and watch a test incident open on the service.
Channels attach per link, so nothing pages until you say so. Tick the PagerDuty channel on the specific links and QR codes that are genuine signals — and leave the marketing links to Slack.
Notifications attach per link — each code carries its own channel list. Open the QR code on the emergency stop, tick the PagerDuty channel, and the next scan opens an incident — while the rest of the account stays quiet.
Every delivery attempt to PagerDuty is recorded in the delivery log with its HTTP response — first try and every retry. When someone asks whether the trigger actually reached PagerDuty, the answer is a row, not a shrug.
xengo POSTs the trigger event straight to events.pagerduty.com with your routing key — the standard integration path, not an email inbox pretending to be one.
The incident summary carries what was scanned: link title, short URL, source (click vs QR scan), destination, time, device, IP and your tags — within PagerDuty's 1,024-character limit.
A failed delivery retries on a backoff ladder — up to six attempts over roughly 43 minutes — and every attempt lands in the delivery log.
Every event arrives as severity info with source xengo. Escalation is your call: use the service's event rules or orchestration to raise what matters.
xengo opens incidents; it never acknowledges or resolves them. Closing the loop stays with the human who investigated.
The Send test button fires a real Events API call, so you can watch the test incident open — and your escalation policy react — before anything is live.
Through Events API v2. You create an Events API v2 integration on a PagerDuty service, paste the routing key into the xengo console, and every routed scan or click triggers an incident on that service. No app to install, no OAuth, no email bridge — deliveries are authenticated by the routing key itself.
xengo sends each scan as its own trigger event and doesn't set a dedup key, so PagerDuty treats each one as a distinct event. How they roll up into incidents is then governed by your service's own grouping and event rules — which is exactly where that decision belongs.
No, and honestly it shouldn't. Every event arrives as severity info and xengo only ever sends trigger — never acknowledge or resolve. Use PagerDuty's event orchestration or service rules to escalate specific codes, and close incidents from PagerDuty once a human has looked.
The failed attempt is logged and retried on a backoff ladder — 30 seconds, 2 minutes, 10 minutes, then 15-minute steps, six attempts in total. Each retry gets its own delivery-log row, so an outage reads as a timeline rather than a mystery.
No — PagerDuty receives the readable summary via Events API v2, not the structured JSON event, and the delivery isn't signed (the routing key is the credential). If your tooling wants the full signed event, run the generic webhook alongside; the same scan feeds both.
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 routing key, one test incident, and on-call hears about the scans that matter.
