10 Zaps You Can Build From an SMLLR Webhook
Ten realistic Zapier automations built entirely on SMLLR's six real webhook events and Zapier's own 'Webhooks by Zapier' trigger — no invented apps, no invented actions.
The Short Answer
Every Zap in this list starts the same way: Zapier's own built-in 'Webhooks by Zapier' app, using its 'Catch Hook' trigger, pointed at a generic SMLLR webhook endpoint URL. From there, any of SMLLR's six real event types — scan.created, qr.created, qr.updated, qr.scan_limit_reached, qr.scheduled_redirect_fired, qr.device_redirect_matched — can feed into any of Zapier's 6,000+ downstream apps. This post assumes you've already got the trigger side wired up — see QR Code Automation with Zapier & Make for the general setup, or How to Set Up SMLLR Webhooks for the SMLLR-side endpoint creation — and focuses purely on what to actually build once the trigger fires.
10 Zaps, Built on Real Events and Real Zapier Apps
Each one below uses only the real six SMLLR event types and well-established Zapier app categories — no invented apps, no invented capabilities.
- **1. Log every scan to Google Sheets.** Trigger: `scan.created`. Action: Google Sheets → Create Spreadsheet Row, mapping device, browser, and coarse location into columns. Gives you a running raw log outside SMLLR's own analytics, useful if another team wants to build their own pivot tables from scan data.
- **2. Text yourself when a launch-day QR gets its first scan.** Trigger: `scan.created`, filtered (via Zapier's Filter step) to a specific QR code name. Action: SMS by Zapier → Send SMS. Confirms a billboard, mailer, or packaging placement is actually being scanned within minutes of going live.
- **3. Create a Trello restock card the moment a promo runs out.** Trigger: `qr.scan_limit_reached`. Action: Trello → Create Card on an ops board, pre-filled with the QR code's name. Turns a scan-limit crossing into an actionable task instead of something someone has to notice in the dashboard.
- **4. Add every new QR code to a master Airtable base.** Trigger: `qr.created`. Action: Airtable → Create Record. Useful for agencies or marketing teams who want one central, filterable table of every QR code across campaigns, independent of SMLLR's own dashboard views.
- **5. Email stakeholders when a campaign QR goes live.** Trigger: `qr.created`, filtered to a specific campaign naming pattern. Action: Gmail → Send Email, with the QR's target URL in the body. Replaces a manual 'it's live' message with an automatic one the moment the QR is actually saved.
- **6. Log every QR edit to a Notion audit page.** Trigger: `qr.updated`. Action: Notion → Create Database Item, recording the QR name, the account that changed it (if available in your payload), and a timestamp. Gives an agency or multi-editor account a change history outside SMLLR's own dashboard.
- **7. Split iOS vs Android scans into separate Sheet tabs.** Trigger: `qr.device_redirect_matched`. Action: Zapier's Paths (conditional branching) routes to one of two Google Sheets → Create Spreadsheet Row actions depending on whether the matched device was iOS or Android, building a running count for an app-install funnel.
- **8. Post a confirmation when a scheduled menu switch fires.** Trigger: `qr.scheduled_redirect_fired`. Action: Slack → Send Channel Message (via Zapier's own Slack app, useful if you want custom formatting or filtering logic beyond SMLLR's native pre-formatted Slack messages). Confirms a time-window redirect rule actually switched at the right moment.
- **9. Request a reorder over email when stock runs out.** Trigger: `qr.scan_limit_reached`. Action: Gmail → Send Email to a supplier or warehouse contact, using the QR name to identify which product's promo or stock-tracking code crossed its limit.
- **10. Build a rolling weekly scan count in Airtable.** Trigger: `scan.created`. Action: Airtable → Create Record into a table filtered by week, then a separate Airtable view or formula field totals scans per QR — a lightweight alternative to exporting SMLLR's own analytics manually each week.
A Note on Zapier's Own Filter and Paths Steps
A few of the Zaps above (#2, #7, #8) lean on Zapier's built-in Filter and Paths steps rather than a plain trigger-to-action Zap. Filter stops a Zap from continuing unless a condition is met (say, only continuing if the QR name matches a specific campaign); Paths splits one trigger into multiple conditional branches (say, one branch for iOS, one for Android). Both are standard, well-documented Zapier features — worth knowing about since several of the more useful automations here need one or the other rather than a single straight line from trigger to action.
What It Costs
The SMLLR side is free once you're on Pro (₹4,999/month) or above — no per-Zap or per-endpoint charge from SMLLR. Zapier itself has its own separate pricing based on how many Zaps you run and how often it checks for new events, entirely independent of your SMLLR plan — check Zapier's own pricing page for current limits if you're planning a high-volume setup.
Related Reading
Frequently Asked Questions
Do I need a published SMLLR app inside Zapier to build these?
No. Every Zap here uses Zapier's own generic 'Webhooks by Zapier → Catch Hook' trigger pointed at a plain SMLLR webhook endpoint URL — SMLLR doesn't have a published app in Zapier's directory, and doesn't need one for this to work.
Which SMLLR event type is most useful to start with?
scan.created is the most broadly useful starting point since it fires on every scan, but qr.scan_limit_reached is often the highest-value one for operational alerts, since it fires exactly once at a meaningful moment rather than on every scan.
Can one SMLLR webhook endpoint feed multiple Zaps?
Yes — a single generic webhook endpoint's Catch Hook URL can be used as the trigger for as many separate Zaps as you want inside Zapier, each with its own filter and action.
Do any of these Zaps expose lead or contact data?
No. Every SMLLR webhook event carries only QR and scan analytics — device, browser, coarse location, timestamps, target URL — never a scanner's name, email, phone number, or Lead Hub consent record.
What plan do I need for these Zaps to work?
Pro plan and above (₹4,999/month) for the SMLLR webhook side. Zapier itself has its own separate plan and pricing, unrelated to your SMLLR plan.
Is Make.com a better fit than Zapier for any of these?
Either works from the same SMLLR webhook endpoint — the choice comes down to which platform's pricing and interface you prefer. See Make.com + SMLLR for the Make-specific setup.