Field kit gets scanned, a delivery label gets checked, a poster link gets clicked — and a Power Automate flow picks it up seconds later. From there it's your Microsoft stack: post to a Teams channel, append an Excel row, create a Dynamics activity, file it in a SharePoint list.
Power Automate's 'When an HTTP request is received' trigger generates a URL when you save the flow. That URL is the whole integration: we POST the scan event to it, your flow parses it with a schema you generate from our sample, and the rest is ordinary flow-building.
In Power Automate: create an instant cloud flow starting from 'When an HTTP request is received'. Save the flow once — that's what generates the logic.azure.com HTTP POST URL. Copy it.
Console → Notifications → Add channel → Power Automate. Paste the URL into the HTTP POST URL field, save, then hit Send test — use that sample body with 'Use sample payload to generate schema' so every field becomes typed dynamic content.
Attach the channel to the links and QR codes that should start it — warehouse labels to the inventory flow, event badges to the follow-up flow.
Channels attach per link. Open a link in the console, tick the Power Automate channels that should hear about it, and the next scan starts that flow — and no other.
Power Automate shows each flow run; the console's delivery log shows each POST we made — attempt by attempt, response code by response code. Reconciling the two takes minutes, not a support ticket.
Not a bare ping: the full scan event — code, source, destination, tags, timestamp, device — arrives at your HTTP POST URL within seconds of the scan.
Every delivery carries Svix-compatible signature headers
(webhook-id, webhook-timestamp,
webhook-signature) signed with your channel's
whsec_ secret, and failures retry on a backoff
ladder for up to six attempts — with every attempt visible in
the console's delivery log. Verification docs →
{
"event": "click",
"source": "qr",
"code": "spring-launch",
"shortUrl": "go.yourbrand.com/spring-launch",
"title": "Spring launch pack",
"destination": "https://yourbrand.com/spring",
"tags": { "campaign": "spring-24", "sku": "SB-114" },
"createdAt": "2026-05-02T09:14:11Z",
"ts": 1752319441000,
"at": "2026-07-12T10:44:01+00:00",
"ip": "203.0.113.7",
"ua": "Mozilla/5.0 (iPhone; …)",
"referer": null,
"customerId": "cus_9f2k…"
}Generate the trigger's JSON schema from our Send test sample and code, source, destination, tags and timestamp all appear as pickable dynamic content in every action.
The POST fires as the redirect completes. The flow starts within seconds of the scan — no recurrence schedule doing the waiting.
Deliveries carry Svix-compatible webhook-id, webhook-timestamp and webhook-signature headers keyed to your whsec_ secret, available in the trigger outputs if you choose to verify.
If the flow endpoint errors or times out, we retry at 30s, 2m, 10m, then 15m twice — six attempts, all visible in the delivery log.
Custom link tags arrive as a structured object — a Condition or Switch on tags.campaign routes the flow without string surgery.
Want the flow and a human-readable ping? Add the Microsoft Teams channel alongside — the same scan feeds both independently.
No certified connector — you paste the URL from the built-in 'When an HTTP request is received' trigger, which ingests our POST natively. The flow starts just as fast as it would from a connector; the set-up is a paste instead of a search.
Microsoft classes 'When an HTTP request is received' as a premium trigger, so check what your Power Automate licensing includes. On the xengo side nothing extra is required — every plan can add Power Automate channels.
Hit Send test in the console, copy the JSON body from the flow's run history (or the delivery log), and paste it into the trigger's 'Use sample payload to generate schema'. After that, every field — code, source, shortUrl, destination, tags — is ordinary dynamic content.
The delivery carries Svix-scheme signature headers signed with your channel's whsec_ secret, and they're readable from the trigger outputs. Many teams simply treat the long generated URL as the secret; the headers are there when policy demands more.
The POST fails and we retry on a backoff ladder — six attempts spanning roughly 43 minutes, each recorded with its response code in the console's delivery log. Delivery is at-least-once, so de-duplicate on the webhook-id header if a run must never repeat.
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 HTTP POST URL and run the flow on real scans.