Make.com + SMLLR: Automating QR Events Without Code
A step-by-step Make.com (formerly Integromat) walkthrough for receiving SMLLR webhook events with a Custom Webhook trigger and building a simple no-code scenario from them.
The Short Answer
Make.com's equivalent of Zapier's 'Catch Hook' is its Webhooks app with a Custom webhook trigger module. Create that module inside a new Make scenario, copy the URL it generates, paste it into a generic SMLLR webhook endpoint (Settings → Webhooks & Slack → Add Endpoint), send a test delivery so Make can learn the payload's data structure, then add whatever downstream modules you want — Google Sheets, Slack, email, or any of Make's other supported apps. This is the Make-specific deep dive; for a higher-level comparison of Make and Zapier together, see QR Code Automation with Zapier & Make.
Why Make Instead of Zapier
Functionally, both tools do the same job here — receive an SMLLR webhook payload and act on it — since SMLLR's webhook side is identical either way: a signed JSON POST to a URL you control. The difference is entirely in each platform's own interface and pricing structure. Make's scenario builder is visual and module-based, with more granular control over data mapping and branching logic inside a single scenario compared to Zapier's more linear trigger-then-action model. Which one to use comes down to preference and whichever platform's pricing fits your automation volume — not anything specific to how SMLLR sends the webhook.
Setting It Up
The full sequence, from an empty Make scenario to a working automation:
- **Create a new scenario in Make.** From your Make dashboard, start a blank scenario.
- **Add the Webhooks app's Custom Webhook trigger.** Search for 'Webhooks' as the first module, choose 'Custom webhook,' and give it a name (e.g. 'SMLLR Events'). Make generates a unique URL for this trigger.
- **Copy the webhook URL into SMLLR.** In SMLLR, go to Settings → Webhooks & Slack → Add Endpoint, choose Generic, and paste the Make webhook URL as the destination. Select the event types you want this scenario to receive and save.
- **Run once and trigger a test delivery.** Back in Make, click 'Run once' on the Custom Webhook module so it's listening, then go to SMLLR and click Send Test Delivery on the endpoint. Make will capture that payload and use it to auto-detect the data structure (field names like `event`, `timestamp`, and the nested `data` object) for use in later modules.
- **Add a Google Sheets module.** Add a second module — Google Sheets → Add a Row — and map fields from the webhook payload (QR name, device, timestamp) into spreadsheet columns using Make's field picker, which now shows the structure detected in the previous step.
- **Add a Slack module.** Add a third module — Slack → Create a Message — to post a short summary to a channel, using the same mapped fields, if you want both a persistent log and a real-time notification from one scenario.
- **Activate the scenario.** Toggle the scenario to 'On' so it runs automatically going forward, rather than only when you manually trigger it.
What This Scenario Actually Buys You Over Native Slack
SMLLR already has a native Slack integration that needs no Make or Zapier step at all — worth being clear about, since it's easy to build a 3-step Make scenario that duplicates something a single pasted Slack Incoming Webhook URL already does for free. Make earns its place when the destination needs more than one thing to happen (Sheets and Slack together, as above), when the message needs custom formatting or conditional logic SMLLR's fixed Slack message templates don't offer, or when the destination isn't Slack at all — a spreadsheet, a database, an email, or any of the hundreds of other apps Make supports.
A Note on Make's Free Tier
Make offers a free tier with a capped number of operations per month, which is generally enough to build and test a scenario like the one above before deciding whether the automation is worth paying for higher volume. Check Make's own pricing page for current limits, since that's Make's pricing and entirely separate from what SMLLR charges — the SMLLR side of this integration (the webhook endpoint itself) is included in the Pro plan with no extra fee.
What It Costs
The SMLLR webhook endpoint feeding this scenario is included in the Pro plan (₹4,999/month) and above, no separate charge. Make.com's own pricing is independent of your SMLLR plan — check their site for current operation limits and paid tiers if your scenario runs at meaningful volume.
Related Reading
How to Connect SMLLR Webhooks to a Make.com Scenario
- 1
Create a new scenario in Make
Start a blank scenario from your Make dashboard.
- 2
Add the Webhooks app's Custom Webhook trigger
Search for 'Webhooks,' select 'Custom webhook,' name it, and let Make generate a unique trigger URL.
- 3
Add the URL as a generic endpoint in SMLLR
In SMLLR, go to Settings → Webhooks & Slack → Add Endpoint, choose Generic, paste the Make URL, select event types, and save.
- 4
Run once and send a test delivery
Click 'Run once' in Make, then Send Test Delivery in SMLLR, so Make captures the payload and detects its data structure.
- 5
Add downstream modules
Add modules like Google Sheets (Add a Row) or Slack (Create a Message), mapping fields from the detected webhook structure.
- 6
Activate the scenario
Turn the scenario on so it runs automatically on future SMLLR events instead of only on manual runs.
Frequently Asked Questions
What's Make's equivalent of Zapier's Catch Hook trigger?
The Webhooks app's 'Custom webhook' module, which generates a unique URL that acts as the trigger for a scenario, the same role Catch Hook plays in Zapier.
Do I need to know the payload structure in advance to use it in Make?
No — sending one test delivery from SMLLR while Make's Custom Webhook module is set to 'Run once' lets Make auto-detect the payload's field structure for use in later modules.
Is Make better than Zapier for SMLLR webhooks?
Neither is objectively better — the SMLLR side is identical either way (a signed JSON POST to a URL you control). The choice comes down to each platform's own interface and pricing.
Can one Make scenario have more than one downstream action?
Yes — a single scenario can chain as many modules as needed after the trigger, such as writing to Google Sheets and posting to Slack from the same webhook event.
Does this replace SMLLR's native Slack integration?
Not necessarily — SMLLR's native Slack integration needs no Make or Zapier step and is the simpler choice if Slack is your only destination. Make/Zapier earn their place when you need more than one destination or custom formatting.
What plan do I need for this to work?
Pro plan and above (₹4,999/month) for the SMLLR webhook endpoint. Make.com has its own separate plan and pricing.