Uniqode
Analytics & DataCreate, style, track, and retire QR codes with the Uniqode QR Code API. Agents mint codes for campaigns and assets, then read scan data to see which placements actually worked.
What This Integration Enables
Most QR tools treat a code as a one-time export. Uniqode treats it as an asset with a lifecycle, and that is the part agents can actually manage. FlowRunner agents mint dynamic codes that resolve through a Uniqode short link, apply an account template so brand styling is not re-decided per batch, tag them into campaigns, pull scan analytics broken down by city, operating system and time of day, and then do the thing almost nobody automates: take the code out of service when its campaign ends.
That last step is why the connectors matter here. Uniqode exposes two ways to end a code's life, and they are not the same. Deactivate QR Code puts a dynamic code to sleep and keeps its history, so it can be woken later. Delete QR Code removes the code and its scan history permanently, and every printed copy stops resolving that instant. An agent can execute either one. Deciding which is the right call for a code sitting on ten thousand pieces of packaging is a judgment about physical inventory that lives outside the API, so the agent stops there and asks.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Minting a code fleet from a product catalog
A packaging refresh needs a distinct code on every SKU. The agent reads the catalog from Shopify, calls List QR Templates to pick the organization's default design so nothing is styled by hand, then loops Create Dynamic QR Code per product with the SKU as the code name and the season's tag attached. Download QR Code returns hosted image URLs in the format the print vendor requires, and the agent writes each short URL and image link back into a Google Sheets row the packaging team already works from. The codes are dynamic, so the destination behind every SKU can move later without touching the artwork.
Reading which physical placement actually earned scans
Codes go on shelf talkers, on the receipt, on the box and in the window. Only one of those usually works. The agent runs Get QR Analytics per code across the campaign window, requesting the breakdown by city and by time of day, and joins the result to the placement notes carried in each code's tags. The output is a ranked placement report posted to Slack: which surface produced scans, where, and at what hour. Reprint spend then follows evidence instead of habit.
Closing out a campaign without breaking what is still in the wild
A promotion ends. The agent lists every code on the promotion tag, checks each one's recent scan activity, and splits the estate into two piles. Codes with no scans in the trailing window are proposed for retirement. Codes still being scanned are repointed to an evergreen page with Update QR Code, because somebody is still holding the printed piece. The proposal, with the scan evidence attached, goes to the brand owner before any state change is applied.
Human-in-Loop Highlight
The gate sits on the difference between sleeping a code and destroying it. When the retirement sweep reaches a code that has not been scanned recently, the agent does not call Delete QR Code. It posts the decision to Slack with the evidence already gathered: "QR code SPRING-SHELF-04 has 312 lifetime scans, 0 in the last 60 days, and is printed on the in-store shelf talkers shipped to 84 locations. Deactivate puts it to sleep and keeps the 312 scans on record, and it can be woken later. Delete removes the code and its scan history permanently, and every printed talker stops resolving the moment you confirm. Which one?" A person who knows whether those talkers were actually pulled from stores makes the call, and the agent applies it. This is the digital andon cord applied to physical collateral: the agent runs the whole sweep, gathers the numbers, and stops at the one operation that reaches into the real world and cannot be undone. That stop is the default behavior of human-in-the-loop in FlowRunner, not a setting somebody remembered to switch on.
Agent Capabilities
18 actionsCode Creation
3- Create Dynamic QR Code Creates a dynamic QR code that resolves through a Uniqode short link, so the destination stays editable after printing and every scan is recorded. Used whenever the code will outlive the campaign that created it.
- Create Static QR Code Creates a static code whose payload is encoded directly into the image and can never be changed. Used for payloads that are genuinely fixed, such as a WiFi network or a plain address, where there is nothing to track and nothing to repoint.
- Download QR Code Returns hosted download URLs for a code's image in the requested format and size. Used to hand a print vendor a direct link rather than shuttling files around.
Code Lifecycle
4- Update QR Code Partially updates a code's name, dynamic destination, styling or tags. This is how a printed code gets repointed at a new landing page without reprinting anything.
- Deactivate QR Code Puts a dynamic code to sleep so scans stop resolving, without deleting the code or losing its history. Used to retire a campaign whose printed material is still circulating.
- Activate QR Code Wakes a sleeping dynamic code so it resolves and records scans again. Used when a seasonal placement comes back into service.
- Delete QR Code Permanently deletes a code. Printed copies stop resolving immediately and the scan history goes with it. This is the operation an agent should route to a person rather than execute on a schedule.
Estate Inventory
3- List QR Codes Retrieves codes in the account with their name, type, scan-through URL and lifecycle state, filterable by campaign type or state. Used to audit an estate or to resolve an ID for any other operation.
- Get QR Code Retrieves one code with its payload, customization attributes, campaign configuration and tags. Used to inspect exactly what a code is configured to do before changing it.
- List Organizations Retrieves the Uniqode organizations the API key can reach. Almost every other operation needs an organization ID, so this is the natural first call in a new flow.
Design and Grouping
4- List QR Templates Retrieves the reusable design templates on the account, including the organization default. Used so a new batch inherits brand styling instead of being restyled by hand.
- Create QR Template Creates a reusable design template. Used once, so every future code in the organization comes out looking the same.
- List Tags Retrieves the account's tags with their display colours. Tags are how Uniqode groups codes; there is no folder resource.
- Create Tag Creates a tag for grouping codes by campaign, region or print run. Used to make an estate reportable later.
Analytics
1- Get QR Analytics Returns scan analytics for a code across a date range, as a scans-over-time series or broken down by operating system, city, visitor or time of day. Used to judge which physical placement is actually working.
Webhook Subscriptions
3- List Webhooks Retrieves the outbound webhook subscriptions on an organization and which QR, form and geofence events each one listens for. Useful for auditing integrations that have started failing.
- Create Webhook Creates an outbound webhook subscription on an organization for selected QR, form and geofence events. Uniqode publishes no schema for the delivered payload, so plan to inspect a live delivery when building the handler.
- Delete Webhook Removes a webhook subscription so Uniqode stops posting events to that endpoint.
Frequently Asked Questions
What can FlowRunner do with Uniqode?
FlowRunner agents can run List QR Codes, Get QR Code, and Create Static QR Code in Uniqode, plus 15 more actions.
Does connecting Uniqode to FlowRunner require OAuth?
No. Uniqode connects to FlowRunner with an API key, no OAuth flow required.
Can Uniqode trigger a FlowRunner workflow automatically?
Uniqode doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Uniqode
$100 in credits. No card required. Connect in minutes.