Resources · Make integration

Home Assistant Make integrationAutomate Home Assistant with Make.

Your house already knows things your other apps never hear about. The Home Assistant Make integration brings 9 modules, the bricks of a Make automation, to read an entity, flip a switch or write a value. It has no trigger module, so the page shows how to start a run.

Try the Home Assistant integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Home Assistant Make integration actually do?

It links your Home Assistant instance to Make so an automation can read what your sensors say and act on your entities. In Make you build a scenario, a chain of modules that run one after the other, and Home Assistant supplies nine of those modules. Eight act on the house, one hands back the full list of what exists.

Three results come back over and over. A status check that pulls the state of one sensor with Read an Entity and stops the rest of the scenario when the value is fine. A remote command that ends on Fire an Action, so a form, a calendar or a support ticket handled elsewhere can act on the house. And a value pushed the other way with Update a Numeric Entity, when a figure computed somewhere else belongs on your dashboard.

What Make cannot do here is wait. Home Assistant gives Make no trigger module, so nothing arrives on its own. Make is the one that asks, on the schedule set on the first module of the scenario, 15 minutes by default and 15 minutes minimum on the Free plan, and Make pricing covers the rest. When the reaction has to be quick, start the scenario on a trigger from another app.

One honest caveat about the official page: Make states that its Home Assistant documentation is AI-generated and may contain mistakes. Check anything critical against Home Assistant itself.

The same app exists on the other side. There is a Home Assistant n8n integration, and the n8n vs Make comparison lays out the criteria if the tool is not picked yet.

Connect

How do you connect Home Assistant to Make?

  1. 01

    Create a long-lived token in Home Assistant

    Log in to your Home Assistant instance and copy its URL from your browser's address bar. Open your user profile, scroll down to Long-Lived Access Tokens, click Create Token, give it a name, then copy the token shown on screen.

  2. 02

    Add a module and open the connection window

    In Make, drop any Home Assistant module into your scenario and click Create a connection. A connection is your account linked to Make once, then reused by every Home Assistant module you add after that one.

  3. 03

    Name it and paste your credentials

    The Connection name field is optional, but a clear name helps the day a second instance shows up. Paste the URL and the token you copied from Home Assistant, or follow what the window asks for, then confirm.

First scenario

Your first scenario: read a sensor, then act

GoalWhen the schedule fires, Make reads one Home Assistant entity and acts on the house if the value calls for it.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + to place your first module. Search Home Assistant by name and pick Read an Entity.

  2. 02

    Link your account

    Click Create a connection, paste the instance URL and the long-lived token, then confirm. Every Home Assistant module you add afterwards reuses the same connection, so this happens once.

  3. 03

    Point the module at one entity

    Tell Read an Entity which sensor you want. Once the connection exists, Make queries your instance and offers what it can read, so you pick from a list instead of typing from memory.

  4. 04

    Add the action

    Click the + on the right of the module and add Fire an Action. Map the entity you just read into it, so the action lands on the same thing the first module looked at.

  5. 05

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundle each module received, a bundle being one item that travels from module to module. Read the state that came back before going further.

  6. 06

    Set the clock and switch it on

    Open Scheduling on the first module to choose how often Make asks, 15 minutes by default, then flip the scenario on. Nothing runs until that switch is on.

Modules

What each Home Assistant module does

Home Assistant gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Home Assistant1

Fire an Action

Action

In Make“Fires specified Home Assistant action. Returns a list of states that have been changed during action execution.”

This is the module that makes something happen at home. You name the action and the entity it applies to, Home Assistant runs it, and the module hands back the entities whose state changed while it ran.

When to use it
a support ticket is marked urgent and the lights in the workshop have to come on.
Watch out
there is no undo, so test with Run once on a harmless entity before you point it at anything that matters.
Home Assistant2

Fire an Event

Action

In Make“Fires specified Home Assistant event. Returns `message` property if successful.”

Instead of acting on an entity, this one raises a named event inside Home Assistant and returns a short confirmation when it went through. Your own Home Assistant automations listen for that event and take over from there.

When to use it
the logic already lives in Home Assistant and you only want Make to give the signal.
Watch out
the confirmation says the event fired, not that anything reacted to it.
Home Assistant3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

The catch-all. It reaches any endpoint of the Home Assistant API, the technical door one tool uses to query another, through the connection you already set up.

When to use it
your instance exposes something the module list does not offer, and you would rather not leave Make for it.
Watch out
you build the request yourself, and it counts as an operation, meaning one module execution billed against your plan.
Home Assistant4

Read an Entity

Action

In Make“Reads the state and details of a specified sensor.”

Reads one entity and gives you its current state with its details, without changing anything. That reading is what the rest of the scenario decides on: a temperature, a door, a battery level.

When to use it
before any action, to check the situation instead of acting blind.
Watch out
it reads at the moment the scenario runs, so a value that moves between two runs is simply never seen.
Home Assistant5

Toggle a Boolean Entity

Action

In Make“Toggle the state of a specified boolean entity. If the entity is off, turn it on. If an entity is on, turn it off.”

Flips a yes/no entity to the opposite position: off becomes on, on becomes off. You do not have to know where it stands, the module works it out.

When to use it
one switch driven from a button that lives elsewhere in your tools, behaving exactly as if someone pressed it.
Watch out
two runs bring you back where you started, so it is the wrong pick when the end position matters.
Home Assistant6

Update a Boolean Entity

Action

In Make“Sets the boolean value of a specified entity.”

Sets a yes/no entity to the exact value you give it. Whatever position it was in, it ends up where you said, which makes the outcome of the scenario predictable.

When to use it
the end of a scenario where a switch has to be off whatever state it was in.
Watch out
it overwrites without asking, so an entity someone moved by hand a second earlier gets pushed back.
Home Assistant7

Update a Entity State

Action

In Make“Updates or creates the state of a specified entity.”

Writes the state of an entity, and creates that entity when it does not exist yet. It is how a value living in another tool, a stock level, a booking count, ends up visible in Home Assistant.

When to use it
you want your own dashboard to show something Home Assistant has no sensor for.
Watch out
a name it does not recognize becomes a new entity, so a typo leaves you with a duplicate instead of an error.
Home Assistant8

Update a Numeric Entity

Action

In Make“Sets the value of a specified entity.”

Numbers get their own module: you hand it the value, the entity takes it. The figure can come from a calculation done earlier in the scenario or from a different app entirely.

When to use it
a target temperature that follows the occupancy of a room booked in your scheduling tool.
Watch out
it sets the value, it does not add to it, so compute the new figure in Make before you send it.
Home Assistant9

List Entities

Search

In Make“Lists all existing entities, including state and attributes.”

The only search of the set. It brings back every entity of your instance with its state and attributes, one bundle per entity, ready for the next module to filter or walk through.

When to use it
the first time you wire a scenario, to find the exact name of the entity you are after.
Watch out
a search returns nothing, one item or a long list, and every item the next module handles costs another operation.
Need help

Need help automating Home Assistant with Make?

A person reads every message.

FAQ

Questions that come up next

01Is the Home Assistant Make integration free?
Yes on the Make side. Home Assistant is a standard app, so it is available from the Free plan, and there is nothing extra to pay Make for the app itself. What the Free plan frames is the running: 2 active scenarios, 15 minutes minimum between two scheduled runs, 5 minutes of execution, files up to 5 MB and 512 MB of transfer. Paid plans drop the interval to 1 minute, lift the cap on active scenarios and go up to 40 minutes of execution. Your own Home Assistant instance is billed on its own side, per the Home Assistant pricing page.
02What do you need to connect Home Assistant to Make?
Three things, gathered before you open Make. An active Home Assistant instance, otherwise Make has nobody to talk to. The URL of that instance, copied from your browser's address bar once you are logged in. And a long-lived access token, created from your user profile under Long-Lived Access Tokens. In Make you then add a Home Assistant module, click Create a connection, optionally name it in the Connection name field, and enter the credentials you copied. Every module of the app reuses that connection afterwards.
03Does Home Assistant react in real time with Make?
No, and that is the thing to understand before building. The app ships 9 modules and not a single trigger, so Home Assistant never calls Make on its own. There is no instant module here, nothing arrives by webhook from your instance, meaning no call the app would send to Make the moment something happens. Make is the one that asks, at the interval set on the first module of the scenario, 15 minutes by default. Two ways around it: start the scenario on a trigger from another app, or give Make its own webhook and have something outside call it.
04What if a module is missing or a limit gets in the way?
Use Make an API Call. It is one of the 9 modules, it goes through the same connection, and it reaches any endpoint of the Home Assistant API, so whatever the other eight do not cover stays inside the scenario. Worth knowing too: Make flags its own Home Assistant documentation as AI-generated and possibly wrong, so verify anything important with Home Assistant. If something still does not add up, go back to the connection: the instance has to be up and the token still valid.
05Make or n8n for Home Assistant?
It depends on what you want to carry. Make fits if you want to see the scenario as a chain of round modules, build it without writing code and stay inside the editor. n8n fits if you already self-host, want the logic sitting next to your instance, and do not mind a bit of code in a node. Both cover Home Assistant. The honest test is everything else: count the other apps you need in the same automation, and take the tool that already talks to them.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations