Capture the code
Point the camera, wedge scanner, or keyboard input at the label - UPC, EAN, Code 128, QR, or internal SKU formats.
Capture Barcode Scan Events with Webhooks
When an operator scans in the browser, Scan2Flow sends an HTTP request to your webhook with the decoded value and workflow context. Use it for inventory receiving, cycle count middleware, asset tracking, or automation chains in Zapier, Make, or n8n.
Real-time HTTP POST on every matched scan
Match a workflow
Format rules, pattern rules, and enabled workflows decide which task runs - receiving, count, pick, lookup, or custom automation.
POST to your webhook
Route the decoded value to your HTTP endpoint, webhook receiver, or automation tool URL. Your server owns validation, storage, and inventory updates.
Example webhook workflow
A simple webhook workflow can log each scan event in another system without building a native scanner app. Works with Zapier, Make, and n8n via webhook URLs - see the linked example pages below.
- Create a workflow with an API call style action.
- Paste the webhook or endpoint URL into the workflow.
- Use {'{{'}data{'}}'} where the scanned barcode or QR value should be inserted.
- Test with webhook.site or a local tunnel, then scan with camera, wedge input, or manual entry before go-live.
Example payload
You control the schema. A common starting point is the scanned value, a workflow name, and optional static fields. Your receiver adds timestamps, user IDs, and inventory context.
{
"scan_value": "{{data}}",
"source": "scan2flow",
"workflow": "webhook-example",
"captured_at": "2026-06-05T00:00:00.000Z"
}What this page claims
- Capture can start from a browser camera, USB or Bluetooth scanner input, or manual entry on phones, Android handheld terminals, enterprise mobile computers, or wedge workstations.
- Workflow actions can call an HTTP endpoint, display returned data, render HTML/JS, open a URL, or show an iframe.
- Rules can match specific barcode or QR values with formats and patterns before an action runs.
- The receiving system stays the source of truth; Scan2Flow routes the scanned value to the workflow you configure.
- Browser-based capture can replace dedicated scanners when the use case is capture-and-send; installable as a PWA on supported devices.
- Scan2Flow is the browser trigger; your server or automation platform decides what happens next.
- Comparing hosted sheet capture apps? See the Scan2Flow vs Orca Scan comparison page for positioning.
Scan to webhook FAQ
Is this a native connector?
No. This page describes sending scan data to a webhook or HTTP endpoint. The receiving service decides what to do next.
What happens when someone scans?
Scan2Flow matches the scan to a workflow, then runs the configured action - typically an HTTP POST to your URL with the decoded value in the body or query string you define.
What fields are in a typical scan webhook payload?
You control the schema. A common starting point is the scanned value, a workflow name or ID, and any static fields you add in the workflow editor. Your receiver adds timestamps, user IDs, and inventory context.
How do I test a webhook workflow before production?
Point the workflow at a request inspector such as webhook.site, or expose a local server with a tunnel (for example npx localtunnel --port 3000). Scan a test barcode in the browser, confirm the POST payload, then switch to your production URL and auth.
How do I secure my webhook endpoint?
Use HTTPS on the receiving URL. Add authentication headers or query tokens in your workflow configuration and validate them on your server. Scan2Flow sends what you configure; your endpoint enforces access control.
Can scan webhooks drive inventory updates?
Yes, when your middleware maps the POST into WMS, ERP, or Shopify inventory APIs. Scan2Flow captures and sends; it does not adjust stock levels itself.
How is this different from Orca Scan webhooks?
Orca Scan sends sheet row events from its hosted app. Scan2Flow sends scan-triggered workflow actions from the browser with no sheet lock-in. See /compare/orca-scan for a positioning comparison.
Does this work with Zapier, Make, or n8n?
Yes, when you use a webhook URL from those platforms as the workflow destination. Scan2Flow does not ship native connectors - see the barcode-to-zapier, barcode-to-make, and barcode-to-n8n pages for example patterns.
Can I use this without a camera?
Yes. Scan2Flow also supports scanner input and manual entry, so a camera is not the only input path.
Where does the scanned data live?
Your configured workflow sends the value to the destination you choose. Your webhook, API, CRM, ERP, or automation platform remains the system of record.
Open the scanner - test a webhook workflow
Start with one workflow and one endpoint. See workflow docs for API-call actions, then point a test scan at your URL.