CodeREADr

Connect AI agents to CodeREADr for barcode scanning, validation, and scan records. Agents manage scanning services and validation databases so a scan at the door or the dock resolves against live data.

1 trigger 40 actions API key available

Platform Documentation ↗ Capability data verified 2026-07-31

A ticket order is confirmed in the commerce system before doors open

Agent reads the ticket reference, holder name and access tier from the order

Agent confirms the reference is not already stored in the event's validation database

Agent calls Upsert Database Value to write the barcode with the response text the scanner will show

Agent calls Generate Barcode Image and attaches the QR Code to the confirmation email

Agent watches On New Scan for barcodes the gate rejected and pulls their scan history

The gate supervisor decides whether to invalidate a pass while its holder is standing at the door

What This Integration Enables

Most of the systems FlowRunner connects to give an agent a second chance. A record can be corrected, an email can be followed by a retraction, a ledger entry can be reversed next month. A barcode scan cannot. The scan happens in the physical world, at a gate or a dock or a shelf, with a person standing in front of the device waiting for a green tick. Whatever the validation database says at that instant is the answer they get, and the cost of a wrong answer is paid immediately by the human being turned away.

CodeREADr is the connector for teams whose automation has a queue in front of it. Agents own the whole loop rather than one end of it: they build and configure the scanning service, keep the validation database in step with the ticketing, membership or inventory system that is the real source of truth, issue the barcode image that will later be scanned, and then read every scan record back as it lands. They can attach data-collection questions so the scanner captures a photo or a GPS confirmation alongside the code, stamp scan records with an external order number after the fact, and provision the app users and devices that do the scanning. The result is that the list on the handheld is never a copy of yesterday's truth, and the automation exceptions that matter, the duplicate pass and the code that should have been revoked, reach a person while they can still be acted on.

Without FlowRunner

Snapshot ticket list The validation list is exported the night before and is stale by the time doors open

Unexplained refusals A scanner says no and nobody at the gate can see why, so the queue stops while it is argued out

After-the-fact reconciliation Scan counts are matched against sales days later, from a spreadsheet export

With FlowRunner

Live validation list Every new order writes into the database the handheld checks against

Traceable refusal Each rejected scan carries its device, app user, service and prior scan history

Reconciliation as devices sync Scan records reach reporting as upload batches arrive, not at the end of the week

Use Case Scenarios

Event access from a live ticket list

Tickets sell continuously up to and through the doors opening. Each confirmed order in the commerce platform triggers an agent that writes the ticket reference into the event's validation database with Upsert Database Value, setting the response text the gate staff will read on screen: the holder's name and their access tier. The same flow calls Generate Barcode Image and stores the QR Code in FlowRunner file storage so it can be attached to the confirmation email. A cancellation runs the reverse path through Update Database Value, flipping the value to invalid without disturbing anything else in the database. Because the list is written continuously rather than exported once, a ticket bought in the queue outside works on the scanner inside.

Warehouse receiving reconciled against the purchase order

A pallet arrives and a receiver scans each carton at the dock. On New Scan fires for each record, and the agent looks the barcode up against the open purchase order in Acumatica or NetSuite. Cartons that match are stamped with the purchase order number using Set Scan Property, so the scan record itself carries the reconciliation. Cartons that do not match, an unexpected SKU or a quantity over the order, are posted into the receiving channel in Slack with the device name and the app user who scanned them, so the question goes to the person holding the handheld rather than to a report nobody opens.

Provisioning scanning staff for a seasonal site

A new site opens for a season and needs eight scanning staff on shift by Monday. The agent reads the roster from the HR system, calls Create App User for each person, and calls Authorize Users For Services to give them exactly the services that site runs and nothing else. It calls Create Question and Add Question Answer Option to attach a photo capture to the returns service, then Add Questions To Services to put that question on the right jobs only. When the season closes, Revoke Users From Services removes access while leaving every scan record those people produced intact for audit.

Human-in-Loop Highlight

The gate that matters here is invalidating a credential while its holder is standing in front of a scanner. A pass presents at Gate 1 that On New Scan already recorded at Gate 3 eleven minutes earlier. An agent could resolve this mechanically: call Update Database Value, mark the value invalid, and let the device refuse the second presentation. That is a decision to turn a person away in public on the strength of a timestamp, and the agent cannot see the thing that decides it, which is whether this is a shared ticket or a legitimate re-entry through a different door. So it stops, posts the evidence it does have into the gate supervisor's channel, and asks: "Pass TKT-4471 scanned at Gate 3 Handheld at 18:42 and has just presented at Gate 1. Mark it invalid and refuse entry, admit and log the duplicate, or hold for ID check?" The supervisor answers from their phone at the door, and the agent applies the decision to the database in the seconds before the next scan. The same gate stands in front of Clear Database and Delete Database, both of which are irreversible and both of which would reject every ticket at every gate at once. An agent never reaches for either of those on its own, because the digital andon cord exists precisely for the operations that cannot be walked back once the line has moved.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

40 actions

Scanning Services

List Services Retrieve the scanning services in the account with their validation method, linked database, postback URL, authorized app users and attached questions. Used as the starting point for almost every other operation, because most of them need a service ID.
Create Service Create a scanning service and return its ID, choosing how scans are handled: recorded online or on device, validated against a database online or on device, or forwarded to your own postback URL. Used when a new event, site or inventory count needs its own scanning job.
Update Service Change the settings of an existing service. Used to open or close an active period, change duplicate handling, or turn on GPS capture. Note that barcode symbologies reset to the account default when an update omits them, so resubmit the full list for services with a restricted set.
Delete Services Permanently delete one or more scanning services. Used for cleanup after a season closes, once the scan records have been exported.
Authorize Users For Services Grant app users permission to run one or more services, which is what makes a service appear in the CodeREADr app for those users. Used to provision scanning staff for a shift or a site.
Revoke Users From Services Remove app users' permission to run services. Used at the end of a season or a shift; existing scan records are untouched.
Add Questions To Services Attach data-collection questions to services so app users answer them around each scan, controlled by when the question appears: as shared session info, before the scan is sent, after it is sent, or only on a valid or invalid result. Used to capture a photo, a count or a reason code at the moment of the scan.
Remove Questions From Services Detach questions from services without deleting the questions themselves. Used when a seasonal capture requirement ends.

Validation Databases

List Databases Retrieve the validation databases in the account with their names, stored value counts and the services linked to them. Used to resolve the database ID the value operations need.
Create Database Create an empty validation database and return its ID. Used at the start of an event or inventory cycle. Case sensitivity is fixed at creation, so decide up front whether two codes differing only in case are the same barcode.
Rename Database Change the display name of a database. Used for housekeeping; stored values, case sensitivity and service links are unaffected.
Clear Database Remove every barcode value from a database while keeping the database, its ID and its service links. Used to reload a validation list from scratch before the next event. The removal cannot be undone.
Delete Database Permanently delete a validation database and every value in it. Used only after unlinking it from every service, because a linked database cannot be deleted.

Database Values

Search Database Values List or search the barcode values in a database with their response text and validity, filtering by exact or partial match and paging through large lists. Used to check whether a code is already issued before minting another.
Add Database Value Add a single barcode value with the response text the app user sees when it is scanned. Used where a duplicate should be reported rather than silently overwritten, because the call fails if the value already exists.
Upsert Database Value Insert a barcode value or update it if it is already present. Used as the default sync operation from a ticketing or inventory system, because it never fails on duplicates.
Upsert Database Values In Bulk Insert or update up to one hundred values in a single call, each optionally targeting its own database with its own response text and validity. Used for batch sync from an external source without falling back to a CSV import.
Update Database Value Change the response text and the validity of a value that already exists, using the barcode as the lookup key. Used to invalidate a single ticket or pass without touching anything else in the database.
Delete Database Value Permanently remove a single value from a database, after which no linked service recognizes that barcode. Used for one-off corrections rather than bulk resets.
Import Database CSV Import barcode values from CSV content, each row holding the value and its optional response text. Used to load a full ticket or inventory list in one operation, with deferred import for files over ten thousand rows.

Scan Records

Search Scans Retrieve scan records in bulk with their barcode value, validation status, response, timestamps, device, service, app user, question answers and scan properties. Used for reporting, reconciliation and export, filtered by service, device, user, status, date range, upload batch or barcode match.
Delete Scans Permanently delete scan records by ID. Used to remove test scans, with the caveat that a deleted scan no longer counts as a duplicate the next time the same barcode is presented.
List Scan Uploads List the upload batches that carried on-device scans to CodeREADr, each with its service, device, app user, scan count and status. Used to confirm a device has finished syncing before reconciling.

Scan Properties

Set Scan Property Attach a named property to one or more scan records, overwriting it if it already exists. Used to stamp a scan with an external order number, a processing state or a batch reference from the workflow that handled it.
Get Scan Property Read a single named property on a scan record. Used to check a flag the workflow set earlier, so the same scan is not processed twice.
Delete Scan Property Remove a named property from a scan record, leaving the scan and its other properties intact. Used for correction workflows.

App Users and Devices

List App Users Retrieve the app users in the account with their usernames, device activation limits and the services each is authorized to run. Used to resolve the user ID needed for authorization and scan filtering.
Create App User Create a login for the CodeREADr scanning app and return its ID, optionally capping how many devices that user may activate in a billing period. Used to onboard scanning staff.
Update App User Change an app user's username, password or device activation limit. Used for routine account maintenance.
Delete App Users Permanently delete app users so they can no longer sign into the scanning app, while keeping their scan records. Used when staff leave.
Validate App User Credentials Check an app user's username and password and return their profile including the services they may run. Used to authenticate scanning staff inside your own kiosk or portal without maintaining a second user directory.
List Devices Retrieve the devices activated against the account with their identifiers, display names and activation dates. Used to audit what hardware is in the field.
Rename Device Change a device's display name. Used to make scan records readable, because the device name is what identifies the hardware in every report.

Questions

List Questions Retrieve the data-collection questions in the account with their text, input type and answer options. Used to resolve question IDs and to interpret the answers returned with scan records.
Create Question Create a question and return its ID, choosing the input the app shows: short answer, numeric, single or multiple choice, photo capture, GPS confirmation, or a custom web question. Used to add a capture step around a scan.
Add Question Answer Option Add a selectable answer option to a question. Used to populate choice questions, which need at least two options, and to carry the implementation of a custom web question.
Delete Question Answer Option Remove answer options by ID, subject to choice questions keeping at least two. Used to retire options without affecting answers already recorded on past scans.
Delete Questions Permanently delete questions and detach them from every service that used them, while leaving recorded answers in the scan records. Used for cleanup.

Barcodes and Account

Generate Barcode Image Generate a QR Code or PDF417 image for a value and store it in FlowRunner file storage, returning a URL to email, print or attach. Used alongside the database value operations to issue a pass and the code that validates it in a single flow.
Get API Limits Report how many API requests the account may make per period and how many remain in the current window. Used as a pre-check before a large import or export loop, so a bulk job does not stop halfway.

Triggers

1 triggers

Event Triggers

On New Scan Fires when new scan records reach CodeREADr, emitting each scan with its barcode value, validation status, response, device, service, app user, question answers and scan properties. Watch a single service or the whole account, and narrow to valid or invalid results to drive follow-up work such as alerting on a rejected pass. On-device scans fire when their upload arrives rather than when they were made, which matters when reconciling a site that scans offline. The first cycle records the newest scan without firing, so existing scans are never replayed.

Frequently Asked Questions

What can FlowRunner do with CodeREADr?

FlowRunner agents can run List Services, Create Service, and Update Service in CodeREADr, plus 37 more actions.

Does connecting CodeREADr to FlowRunner require OAuth?

No. CodeREADr connects to FlowRunner with an API key, no OAuth flow required.

Can CodeREADr trigger a FlowRunner workflow automatically?

Yes. CodeREADr supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with CodeREADr

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us