A QR code scan notification in Slack arrives within seconds of somebody scanning, carries the city and device that scanned it, and needs the Business plan because it runs on a webhook rather than a schedule.
The appeal is obvious. A code goes out on a mailer, a banner, a pallet of boxes, and you want to know the moment it starts working instead of refreshing a dashboard all afternoon.
The part worth thinking about first is which scans deserve a message, because a code that does well will fill a channel faster than a person can read it.
How do I send scans to Slack?#
3 steps, and the middle one is the one people skip:
- QRFLOW.codes: New Scan. The trigger. 1 optional field: pick a single QR Code, or leave it blank for every code in the account.
- A filter or a digest. Not required, and the difference between an alert and a mess. More on this below.
- Slack: Send Channel Message. Build the sentence from the scan's own fields.
The ready-made version is Send Slack channel messages for new scans, which covers steps 1 and 3.
The alert is instant rather than polled, because the scan is pushed out the moment it lands. The other trigger, New QR Code, is checked every 15 minutes on Zapier's free plan. A scan alert 15 minutes late would be a report, not an alert.
What can the message actually say?#
A scan message can say the time, the country, the city, the device type, the browser, the operating system and the referrer. It cannot say a name, an email, or a precise location.
So a useful one reads: Warehouse pallet code, 2:14pm, Las Vegas, iPhone. Enough to tell you the mailer landed, the banner is in the right spot, or the boxes reached the floor.
Knowing who scanned needs the code to open something that asks them, like a form or a sign-in page. The scan itself is anonymous by design, and what a scan records lists every field that exists.
One detail that quietly helps: link-preview crawlers and bots are filtered out before a scan counts, so a message in the channel means a person with a phone, not a service fetching the short link to build a preview card.
How do I stop it flooding the channel?#
Stopping the flood means narrowing the trigger, batching the messages, or filtering to the unusual ones. A banner at a trade show can take hundreds of scans in a day. One customer's code took 1,203 scans across 3 days at a single show, which as individual messages is a channel nobody will read again.
Pick 1 code, not all of them. The trigger's QR Code field exists for exactly this. Alert on the thing you are watching, not the whole account.
Batch them. Put Digest by Zapier between the trigger and Slack. Scans collect through the day and arrive as 1 message at 5pm.
Filter to what is unusual. A filter step can pass only scans from outside your own country, only the first of the day, or only the code you shipped yesterday. The rest stays in the dashboard where it belongs.
Pick 1 of the 3 before switching it on. Turning it on first and tuning it later means somebody mutes the channel, and a muted channel is worse than no alert.
Why does this one need the Business plan?#
The live alert needs the Business plan because the New Scan trigger works by subscribing a webhook, and webhooks are a Business feature at $29 a month. On any other plan Zapier tries to subscribe and the request is declined with that reason.
The rest of the app does not work this way. Creating codes, updating them, looking them up and pulling scan totals all run on plans below Business. It is this 1 trigger, because it is the only one that needs us to call out to you rather than you calling us.
If the live alert is the whole reason you are here, pricing is the page to read first. If you only want the numbers rather than the moment, a scheduled report costs nothing extra and is a different build.
What to check once it is live#
Scan the code yourself, from a phone, off the office Wi-Fi so the city is not your router's city, and watch 4 things:
- The message arrives in seconds, not minutes.
- The city and device look right.
- It is the code you expected, not every code in the account.
- The channel is one people actually read.
Then leave it a day and ask whether you would read it again tomorrow. If not, add the digest.
Questions people ask about a QR code scan notification#
Can I send it somewhere other than Slack?#
A scan notification can go anywhere, not only Slack. Microsoft Teams, Discord, SMS, a spreadsheet row or a push alert all work.
The trigger does not care what comes after it. Slack is simply the one most teams already watch.
Does every scan fire the alert?#
Every scan that counts fires the alert. Bots and link-preview crawlers are filtered out before counting, so they never reach the automation at all.
Repeat scans by the same person do fire, because telling a second look from a second person would mean tracking people, which the scan record deliberately does not do.
Will it tell me who scanned?#
Nothing here will tell you who scanned, and nothing honest would. A scan is a phone asking for a web address.
If you need an identity, the destination has to ask for one.
What happens if Slack is down?#
If Slack is down the scan is still counted and still appears in your analytics. The alert is a copy of the news, never the record of it.
Can I get the alert without Zapier?#
You can get the alert without Zapier. Webhooks are a Business feature in their own right, so your own endpoint can receive the same event directly, and the developer docs cover the payload.
The wider picture of scans starting automations is in QR codes in Zapier, Make and n8n, the app is listed in Zapier's directory, and a code to test with takes about 10 seconds in the free QR code generator.