QR Code Automation With Zapier and Make: What's Really Possible
How to trigger real-time Zaps and Make scenarios from SMLLR QR/scan events via Webhooks (Pro plan and above) — plus what's still not possible, like creating QR codes from a spreadsheet.
Set Expectations First: No Native SMLLR App, But Real-Time Works
If you searched for this hoping to drag a 'SMLLR' trigger into a Zap or Make scenario — SMLLR doesn't have a published app on Zapier or Make today. There's no dedicated 'New Scan' trigger you pick from a dropdown. But real-time, event-triggered automation is genuinely possible: SMLLR's Webhooks feature (Pro plan and above) pushes a signed JSON payload the instant a QR is created/updated, scanned, or a redirect rule fires — and both Zapier and Make can catch that push with their own generic webhook-catching trigger, no native SMLLR app required.
Real-Time Triggers: Webhooks Into Zapier's Catch Hook or Make's Custom Webhook
In Zapier, start a Zap with the 'Webhooks by Zapier' app's 'Catch Hook' trigger event — Zapier gives you a unique URL. In Make, add a 'Custom Webhook' trigger module to a new scenario — Make gives you its own unique URL either way. Paste that URL into SMLLR under Settings → Webhooks & Slack as a Generic Webhook endpoint, pick which events you want (scan.created, qr.created, qr.updated, qr.scan_limit_reached, qr.scheduled_redirect_fired, qr.device_redirect_matched), and save. From that point on, SMLLR pushes a payload to Zapier or Make the instant the event happens — no polling, no scheduled check-ins.
What This Gets You: Instant Slack Alerts, Spreadsheet Rows, and More
Once the webhook is wired up, whatever Zapier or Make can do with an incoming JSON payload is fair game: post an instant Slack message when a QR is scanned (SMLLR can also do this natively for Slack — see the Slack Integration guide — but routing through Zapier/Make adds conditional logic, multi-step workflows, or a different destination app), append a row to a Google Sheet per scan, or kick off a multi-app workflow the moment a scan-limit or scheduled redirect rule fires. What it does NOT get you: individual lead records. The payload only ever carries QR/scan analytics (device, browser, country, timestamp, target URL) — never a scanner's name, email, phone, or consent record. Leads captured via SMLLR live in Lead Hub, which webhooks intentionally never expose.
Creating QR Codes in Bulk: Still Not a Zapier Task Today
A 'new Google Sheet row creates a new QR code' automation is a genuinely useful idea, but it isn't buildable via Zapier or Make today — there's no create-QR-code action to call, whether native or via webhook (QR code creation isn't exposed through any API; it's dashboard-only). Webhooks are one-directional, SMLLR → Zapier/Make, not the other way around. For creating many QR codes at once, see the bulk QR guide for what's actually available.
Polling the Reporting API Is Still an Option Too
If you'd rather pull data on a schedule instead of reacting to events — e.g. a daily digest of campaign-level scan counts — SMLLR's read-only reporting API (Premium plan) still works the same way it always has: a scheduled Zap or Scenario calling the generic HTTP module with your API key in the header. Webhooks and API polling aren't mutually exclusive; use whichever fits a given workflow — instant reaction vs. periodic summary.
Related Reading
Frequently Asked Questions
Does SMLLR have a native Zapier or Make integration?
Not a published app in either directory, but real-time automation works today: SMLLR's Webhooks feature (Pro plan and above) pushes events to Zapier's 'Webhooks by Zapier → Catch Hook' trigger or Make's 'Custom Webhook' module, no native app required.
Can I trigger a Zap the moment someone scans a QR code?
Yes — register a generic webhook endpoint under Settings → Webhooks & Slack, point it at Zapier's Catch Hook URL, subscribe to the scan.created event, and SMLLR pushes a payload the instant a scan happens. This requires the Pro plan or above.
Can I automatically create QR codes from a Google Sheet?
Not today. QR code creation isn't exposed through any API — public or otherwise, it's dashboard-only — so there's no Zapier or Make action that can create one. Webhooks only flow one direction, out of SMLLR.
Do I need to be a developer to set up SMLLR automation with Zapier or Make?
No — since there's no native app, you're copying one URL from Zapier/Make into SMLLR's Settings → Webhooks & Slack page and picking checkboxes for which events to send. No code, no API key required for the webhook path (that's only needed if you're polling the reporting API instead).
Is there an extra cost for using Zapier or Make with SMLLR?
SMLLR doesn't charge extra for Webhooks beyond requiring the Pro plan or above (or a Premium plan for API polling); Zapier and Make both have their own separate pricing for task/operation volume on their end.