Resources · Make integration

Taphome Make integrationAutomate Taphome with Make.

Want your TapHome devices to act on their own when a value changes? The Taphome Make integration gives you 5 modules: one trigger, three actions and one search. This guide is for people who know TapHome but are new to Make, and it walks you from the API token to a scenario that runs.

Try the Taphome integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Taphome Make integration do for you?

The Taphome Make integration links your TapHome installation to Make, a no-code tool where you build a scenario: the automation itself, made of modules placed one after the other. Each module is one brick, like a trigger that watches a device or an action that changes one, and Make carries the data between them.

React when a device reading moves. Watch Device Value keeps an eye on one device, and every new value it finds can feed the rest of the scenario, for example a message to the person on call or a row in a shared sheet from another app.

Drive one device from another. Pair that trigger with Update Device Value and a change on the first device sets a new value on a second one, without a rule to write inside TapHome.

Build a picture of the installation. List Devices returns the devices your token can reach, and Get Device Value reads the current value of one of them, which is handy for a status report sent to a facility manager.

Know the limits before you start: the Make documentation for this app lists five modules with no official descriptions, and it warns that its content is AI-generated from the TapHome documentation, so check anything important with TapHome. When a need falls outside these modules, Make an API Call reaches the TapHome API with the same connection. If you are weighing tools, the n8n vs Make comparison and the Make review give you the wider view, and Make training helps if you want to go further on your own.

Connect

How do you connect Taphome to Make?

  1. 01

    Generate an API token in TapHome

    You need an active TapHome account. In the TapHome app, open Settings, then Expose devices and TapHome API. Open the menu with three dots, click Generate and copy the token shown on screen.

  2. 02

    Add a Taphome module in Make

    In your scenario, add any Taphome module and click Create a connection. A connection is your TapHome account linked to Make once, then reused by every Taphome module. You can give it a name in Connection name, which is optional.

  3. 03

    Paste the token and save

    Paste the API token you copied into the credential field, or follow the instructions Make shows on screen, then confirm. The module can now read and change what the token exposes.

First scenario

Build your first scenario with Taphome

GoalWhen a watched device value changes in Taphome, Make sets a new value on another device.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + in the middle of the canvas to place your first module.

  2. 02

    Add Watch Device Value

    Search for Taphome, pick Watch Device Value and click Create a connection with your API token. Then choose the device to watch from the list Make builds once the connection works.

  3. 03

    Chain Update Device Value

    Click the + on the right of the trigger and add Update Device Value. Pick the second device and map the value it should take, using data from the first module when that helps.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received; a bundle is one item passed from a module to the next, here one device value.

  5. 05

    Schedule and switch on

    On the first module, open the clock to set the schedule, every 15 minutes by default, and switch the scenario on. From then on Make checks the device at that pace.

Triggers

What starts a Taphome scenario

1 module starts a scenario when something happens in Taphome. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Taphome as soon as it happens.

Taphome1Watch Device Value

Watch Device Value

triggerIn the docs only

Gives your scenario a starting point tied to one TapHome device: each time Make looks, the value it finds becomes a bundle that the next modules can use, whether to alert someone, log the reading or adjust another device.

How it fires
it is a scheduled trigger, so Make checks the app on the scenario's schedule, every 15 minutes by default and never more often than the interval your plan allows.
When to use it
any time the question is "what should happen when this device reports something new" and a short wait between checks is acceptable.
Watch out
the Make documentation gives no description here and the scheduled type is inferred from the name, so check for the clock badge and read the bundle after Run once.
Modules

Everything else Taphome can do in Make

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

Taphome1

Get Device Value

ActionIn the docs only

Reads the current value of one device at the moment the scenario reaches it, so you can put a fresh figure into an email, a sheet or a condition further down.

When to use it
the scenario starts elsewhere, from a form or another app, and needs to know where a TapHome device stands right now.
Watch out
each read counts as one operation, the unit Make counts on your plan, so avoid reading the same device twice in one run.
Taphome2

List Devices

SearchIn the docs only

Returns the devices your API token exposes, one bundle per device, which is the quickest way to see what Make can actually reach in your installation.

When to use it
for an inventory or a status report covering every device rather than a single one.
Watch out
a search can return zero, one or many bundles, and every module placed after it runs once per device, which multiplies operations.
Taphome3

Make an API Call

ActionIn the docs only

Opens the whole TapHome API to your scenario with the connection you already set up, so you are not stuck when the four other modules stop short of what you need.

When to use it
only once you have checked that no listed module does the job and you know which TapHome endpoint to call.
Watch out
you write the request yourself, so keep the TapHome API documentation open; Make does not fill the fields for you here.
Taphome4

Update Device Value

ActionIn the docs only

Sets a new value on a TapHome device from Make, which turns an event anywhere in your scenario into a visible change in the building.

When to use it
after a trigger or a check has decided what the device should do, such as reacting to a reading from another device.
Watch out
test it with Run once on a device you can watch, because a wrong mapping changes a real device in a real room.
Need help

Need help automating Taphome with Make?

A person reads every message.

FAQ

Taphome and Make: common questions

01Is the Taphome Make integration free?
Yes, Taphome is a standard app in Make, available from the Free plan. The Free plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, 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 count usage in credits per month. Your TapHome subscription is a separate matter; the TapHome pricing page covers it.
02What do you need to connect Taphome to Make?
An active TapHome account and an API token generated in the TapHome app. You create the token under Settings, Expose devices, TapHome API, then the three dots menu and Generate, and you copy it right away. In Make, add a Taphome module, click Create a connection, optionally name it, then paste the token or follow the on-screen steps. The same connection then serves every Taphome module, including Make an API Call, so you only do this once per account.
03Does the Taphome trigger in Make fire instantly?
No. Watch Device Value is a scheduled trigger: Make checks TapHome on the scenario's schedule, which is every 15 minutes by default for a new scenario. On the Free plan the shortest gap between two checks is 15 minutes, and paid plans go down to 1 minute. A value that changes and changes back between two checks may go unseen, so keep this trigger for readings where a short delay does not matter. The type is inferred from the module's name, so confirm the clock badge when you add it.
04What if a Taphome module is missing in Make?
Use Make an API Call. It calls any endpoint of the TapHome API with the connection you already created, which covers what Watch Device Value, Get Device Value, List Devices and Update Device Value do not. You build the request yourself, so the TapHome API documentation becomes your reference. Keep in mind that the Make documentation for this app says its content is AI-generated from TapHome sources and may contain mistakes; confirm anything important with TapHome directly.
05Should you use Make or n8n for Taphome?
It depends on the tool your team already works in. On the Make side, the facts are simple: Taphome is a standard app open from the Free plan, with one scheduled trigger, three actions, one search and Make an API Call for the rest. Many apps also have an n8n node, and this page does not rank the two tools or compare their costs. The n8n vs Make comparison linked earlier on this page puts both side by side if you want to weigh them before you build.
Same platform

Other docs you might need on this stack.

Browse all integrations