Capture the lead code
Use a browser camera, USB/Bluetooth scanner input, or manual entry when a badge or label is hard to scan.
Use Scan2Flow to capture badge, label, or QR values in the browser and route them to your CRM, API, spreadsheet, or webhook workflow.
Event teams and field teams often collect leads in one place, then re-type or export them later. That delay creates missed follow-ups, duplicate work, and bad records.
Scan2Flow keeps the capture step simple: scan the QR code, badge, barcode, or typed fallback value, then send that value to the workflow endpoint you configure.
Use a browser camera, USB/Bluetooth scanner input, or manual entry when a badge or label is hard to scan.
Use the selected workflow and optional patterns to decide whether the scanned value should be accepted and where it should go.
Route the value to your API, webhook, spreadsheet receiver, CRM automation, or backend lead handler.
The exact fields depend on your receiver. A simple webhook or API workflow can send the scanned value with context your CRM or automation tool can map.
{
"scan_value": "{{data}}",
"source": "event-lead-capture",
"capture_method": "camera_or_scanner_or_manual",
"captured_at": "2026-06-05T00:00:00.000Z"
}No. This page describes sending scanned lead values to an endpoint, webhook, or automation receiver that you configure.
Yes. Manual entry can run through the same workflow as camera or scanner input.
Yes. Use an API workflow when your backend needs to check, enrich, or reject a scanned value.
The workflow sends the scan value to your configured destination. Your receiving system should store and manage the lead record.
Start with the browser scanner, then route the scanned value to your API or webhook.