Get QR Code Scan Alerts in Slack, in Real Time
SMLLR can post QR code scans, edits, and redirect-rule events straight to a Slack channel — no Slack App to install, no OAuth approval, just a pasted Incoming Webhook URL. Here's how teams actually use it.
The Short Answer
SMLLR's Slack integration (Pro plan and above) posts a message to a Slack channel every time a QR code event you've subscribed to happens — a scan, a QR being created or edited, or a dynamic redirect rule firing. Setup is one field: paste a Slack Incoming Webhook URL into Settings → Webhooks & Slack. There's no Slack App to request, no OAuth approval flow, and no bot token to manage — the URL itself is the connection.
Why Slack Specifically
A dashboard only tells you something happened when you go look at it. For a team that already lives in Slack, having QR activity show up where the conversation already is closes that gap without adding another tab anyone has to remember to check — a manager doesn't need a login to SMLLR to see that a campaign just went live, or that a scan-limit promo just ran out.
How It Works, Without an App Install
Most Slack integrations require adding a Slack App to your workspace and going through an OAuth "Allow" screen. SMLLR's Slack integration skips that entirely by using Slack's own Incoming Webhook feature instead: you create an Incoming Webhook URL from inside Slack (Slack's own "Incoming Webhooks" app, added to whichever channel you want), and that URL — which looks like https://hooks.slack.com/services/... — is itself the secret. Paste it into SMLLR, pick which events you want, and SMLLR POSTs a formatted message to it whenever one fires. Because the URL is the credential, there's no signature header to verify the way SMLLR's generic webhooks have one — treat the URL the same way you'd treat an API key.
What Actually Shows Up in the Channel
Each event type gets its own one-line message, built from the same data a generic webhook endpoint would receive as raw JSON — Slack just gets it pre-formatted instead:
- A scan: "📱 *Menu QR* was scanned from Mumbai, MH, IN on iPhone."
- A new QR code: "🆕 QR code *Menu QR* was created → https://example.com"
- An edited QR code: "✏️ QR code *Menu QR* was updated → https://example.com/new"
- A scan-limit crossing: "🚦 QR code *Promo QR* hit its scan limit (100 scans) and switched to its fallback URL."
- A scheduled redirect firing: "⏰ QR code *Menu QR* redirected via scheduled rule \"Lunch Special\" → https://example.com/lunch"
- A device redirect matching: "📲 QR code *App QR* redirected an ios scanner → https://apps.apple.com/example"
Where This Actually Gets Used
The pattern that repeats is small teams wanting ambient awareness without building a dashboard habit: a restaurant manager sees the moment a table-tent QR's early-bird offer switches over to the regular menu, so they know to swap the physical signage too. An agency running QR campaigns for several clients posts each client's scans into a client-specific channel, giving the account manager live visibility without logging into SMLLR on the client's behalf. A marketing team launching a new print or packaging QR watches the first scans arrive in a shared channel on launch day, which is a faster confirmation the placement is actually working than waiting for a scheduled report.
Setting It Up
The full step-by-step — creating the Incoming Webhook URL in Slack, then adding it in SMLLR — is in the Slack Integration setup guide. It takes about the same amount of time as creating a generic webhook endpoint, since it's the same form with a different endpoint type selected.
What It Costs
Slack, along with Webhooks and Zapier, is available on the Pro plan (₹4,999/month) and above — no separate charge for choosing Slack over a generic endpoint. See the full Webhooks overview for what all six event types cover, or the Zapier guide if Slack is one step in a longer automation rather than the destination itself.
Related Reading
Frequently Asked Questions
Do I need to install a Slack App to use this?
No. SMLLR uses a Slack Incoming Webhook URL, which you generate from Slack's own "Incoming Webhooks" app added to a channel — there's no separate SMLLR Slack App to request or approve.
What plan do I need for Slack notifications?
Pro plan and above (₹4,999/month) — the same plan requirement as Webhooks and Zapier.
Is there a signature to verify, like the generic webhook has?
No. A Slack Incoming Webhook URL is itself the secret — anyone with the URL can post to that channel, so treat it like an API key rather than a public link.
Can I send different events to different Slack channels?
Yes — each Slack endpoint is its own Incoming Webhook URL tied to one channel, and each endpoint has its own event-type selection, so you can route, say, scan-limit alerts to one channel and every scan to another.
Can Slack and a generic webhook endpoint both be active at once?
Yes. Up to 10 endpoints per account, generic and Slack combined, each with its own event subscriptions.
Does the Slack message include who scanned the code?
No — the message only ever contains QR and scan analytics (device, browser, coarse location, timestamp), never a scanner's name, email, phone number, or any Lead Hub contact data.
Can I customize the Slack message text?
Not currently — each event type has a fixed, pre-formatted message. If you need custom formatting, route the event through a generic webhook endpoint into Zapier instead, which can reformat it before posting to Slack.