Resources · Make integration

smart.click IoT Make integrationAutomate smart.click IoT with Make.

Can a button press on a smart.click device start an automation? The smart.click IoT Make integration offers 7 modules: 3 triggers and 4 actions. This page is for teams running connected devices, and it walks you from the connection to a first working scenario.

Try the smart.click IoT integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the smart.click IoT Make integration do for you?

The smart.click IoT Make integration links your smart.click account to Make, so a scenario (the automation you build in Make) can react to what your devices report and send them commands. Three modules watch for battery levels, button presses and new measurements; four are actions, among them Toggle Power and a direct API request. No code is involved.

A physical button that does something. Pair Watch Button pressed with Toggle Power, and every press Make picks up runs the power module. Think of a reception desk or a workshop, where one press should switch a device.

Low batteries caught before a sensor goes quiet. Watch Battery Level can feed a scenario that warns whoever maintains the devices, through any app Make connects to.

Readings that land somewhere useful. Watch New Measurement Data hands each reading to the next module as a bundle (one item that flows from a module to the next), so a spreadsheet or a database can keep the history. Configure Thresholds and Configure Time Intervals sit on the action side, for the settings their names describe.

Know the limits before you start. Make's documentation for smart.click IoT is marked as limited: it lists module names but no descriptions, fields or connection steps, and the module types on this page are inferred from those names. Test each module with Run once, the editor button that executes a scenario one time, before relying on it. When a listed module falls short, Make an API Call reaches any endpoint of the smart.click IoT API with the same connection. If you are weighing tools, the n8n vs Make comparison sets out the criteria, the Make training covers the editor from scratch, and Make troubleshooting helps when a run fails.

Connect

How do you connect smart.click IoT to Make?

  1. 01

    Open the connection window

    Add any smart.click IoT module to a scenario and click Create a connection. A connection is your smart.click account linked to Make once; every other smart.click module in your scenarios reuses it.

  2. 02

    Name the connection

    Naming it is optional. A clear label, such as the site or the account owner, still helps later, when you have more than one connection to choose from in a module.

  3. 03

    Authorize and save

    Follow what smart.click IoT asks for: either approve Make on the page that opens, or paste the key your smart.click account gives you. Then click Save, and the module is ready to fill.

First scenario

Build your first scenario with smart.click IoT

GoalWhen a button press shows up in smart.click IoT, Make runs Toggle Power.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. That empty canvas is where the whole automation will live.

  2. 02

    Add the button trigger

    Search for smart.click IoT, pick Watch Button pressed and click Create a connection, or select the one you already made. Fill the fields; Make lists what it can read once the connection works.

  3. 03

    Add Toggle Power

    Click the + on the right of the trigger, search smart.click IoT again and choose Toggle Power. Map data from the button bundle into its fields wherever it fits.

  4. 04

    Test with Run once

    Press the button first, then click Run once and read the bundles each module received. Toggle Power acts on a real device during the test, so pick one where a switch does no harm.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. A press is handled at the next check, not the moment it happens.

Triggers

What starts a smart.click IoT scenario?

3 modules start a scenario when something happens in smart.click IoT. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by smart.click IoT as soon as it happens.

smart.click IoT1Watch Battery Level

Watch Battery Level

triggerIn the docs only

A weak battery can become a message or a task before the device stops reporting: going by its name, Watch Battery Level brings battery readings from your smart.click devices into a scenario. The documentation offers no description of it, so what it returns is something to discover on a first test.

How it fires
scheduled: Make checks the app on the scenario's schedule, every 15 minutes by default and never more often than that on the Free plan.
When to use it
for whoever looks after a set of sensors and would rather replace batteries from a list than hunt for a silent device.
Watch out
read the first bundle before building any filter on it, since no field is documented.
smart.click IoT2Watch Button pressed

Watch Button pressed

triggerIn the docs only

Turning a smart.click button into a starting point is what Watch Button pressed gives you: each press it picks up can kick off whatever the next modules do. Look at the bundle after a test before mapping anything: no field is documented.

How it fires
scheduled: Make checks the app on the scenario's schedule, so a press is handled at the next check rather than the moment it happens.
When to use it
a front desk or a shop floor where one press should trigger an action elsewhere, such as Toggle Power.
Watch out
the type comes from the module name only; if the editor shows a lightning badge instead of a clock, the trigger is instant and fires as soon as the app calls Make.
smart.click IoT3Watch New Measurement Data

Watch New Measurement Data

triggerIn the docs only

Every new reading your devices send can reach the rest of your tools through Watch New Measurement Data. Each measurement it collects travels to the next module as a bundle, which can mean a spreadsheet row, a database entry or an alert per reading.

How it fires
scheduled: Make checks the app on the scenario's schedule, which you set on the clock of the first module.
When to use it
when you want a history of sensor values outside smart.click IoT, or a warning whenever a check brings back a value you care about.
Watch out
each bundle a later module handles counts as an operation, so a busy sensor can use your plan faster than expected.
Modules

What can smart.click IoT do in a scenario?

smart.click IoT gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

smart.click IoT1

Configure Thresholds

ActionIn the docs only

Device limits can change from a scenario, without opening the smart.click interface: that is what Configure Thresholds is for, and its name points to the values at which a device reacts or reports. Make publishes no description or field list for it.

When to use it
when a rule kept elsewhere, a value in a spreadsheet or a form answer, should decide how sensitive a device is.
Watch out
this action touches a live device, so try it on one test unit with Run once first.
smart.click IoT2

Configure Time Intervals

ActionIn the docs only

Adjusting device timing from a scenario is the job of Configure Time Intervals, which by its name targets how often a device does its work. The documentation says nothing about its fields, so a first test shows what it expects.

When to use it
after Watch Battery Level spots a weak battery, to space out a device's activity instead of sending someone at once.
Watch out
do not confuse it with Scheduling, the clock on the first module that sets when Make runs your scenario.
smart.click IoT3

Make an API Call

ActionIn the docs only

What the other actions leave out can still be reached: Make an API Call sends a request to any endpoint of the smart.click IoT API and reuses the connection you already created.

When to use it
when the documentation stays thin and you need a device operation that no dedicated module names.
Watch out
you write the request yourself, so the endpoint and its parameters come from smart.click's own API reference, which Make does not describe.
smart.click IoT4

Toggle Power

ActionIn the docs only

Toggle Power is the action that turns a button press or a reading into something physical; its name suggests it flips a device's power state. Make gives no further detail on it.

When to use it
right after Watch Button pressed, for the device that button is meant to control.
Watch out
a toggle depends on the current state, so two runs in a row can cancel each other out; test with Run once on a device nobody depends on.
Need help

Need help automating smart.click IoT with Make?

A person reads every message.

FAQ

smart.click IoT and Make: common questions

01Is the smart.click IoT Make integration free?
Yes. smart.click IoT is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one execution of one module on one bundle. Any cost on the smart.click side is outside the scope of this page.
02What do you need to connect smart.click IoT to Make?
A smart.click IoT account and a Make account. Make's documentation lists no prerequisites and no connection steps specific to this app, so the generic flow applies: add a smart.click IoT module, click Create a connection, optionally name it, authorize Make on the app's page or paste the key the app gives you, then click Save. The connection is created once, and every smart.click module reuses it afterwards. If the window asks for something you cannot find, the person who manages your smart.click account is the right contact.
03Does the smart.click IoT trigger react in real time?
No, not as far as the available information goes. All three triggers, Watch Battery Level, Watch Button pressed and Watch New Measurement Data, are listed as scheduled: Make checks the app on the scenario's schedule, every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans go down to 1 minute. These types are inferred from the module names because the documentation gives no detail, so check the badge on each module in the editor: a clock means scheduled, a lightning bolt would mean instant.
04What if a smart.click IoT module is missing in Make?
Use Make an API Call. It is available for smart.click IoT and calls any endpoint of the app's API with the connection you already have, which covers what Configure Thresholds, Configure Time Intervals and Toggle Power do not. Keep in mind that Make marks its smart.click IoT documentation as limited, for lack of public information about the app, so no field lists or limits are published. Plan a Run once test for each module before trusting it, and keep the smart.click API reference open when you build a raw request.
05Make or n8n for smart.click IoT?
It depends on what you check. On Make, smart.click IoT comes with 7 modules: 3 scheduled triggers and 4 actions, including Make an API Call for the rest of the API. Whether n8n offers a node for this app is not covered here, so verify that on the n8n side before comparing anything. Then weigh the practical points: which tool your team already uses, which triggers your devices need, and whether a generic API request is acceptable for the missing pieces. Neither tool is ranked on this page; the n8n vs Make comparison linked above lists the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations