Resources · Make integration

SmartThings Make integrationAutomate SmartThings with Make.

Can Make run your SmartThings scenes and keep your locations tidy without a single line of code? The SmartThings Make integration offers 15 modules: 11 actions and 4 searches. This guide connects your account and walks you through a first working scenario.

Try the SmartThings integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SmartThings Make integration do for you?

The SmartThings Make integration links your SmartThings account to Make so a scenario, the automation you build in Make, can create and edit locations and rooms, run rules and scenes, and read what your account holds. Each step is a module, one brick of that scenario, and you set it up with clicks instead of code.

Fire a scene from another tool. A booking confirmed in your calendar app or a form sent by a guest can start a scenario whose next step is Execute a Scene. The scene you already designed in SmartThings runs without anyone opening the phone app.

Set up a new site in one pass. Facilities teams that open offices or rental units can chain Create a Location and Create a Room, fed by a row in a sheet or a base. If that list lives in Airtable, the Airtable Make integration covers the starting side.

Keep an inventory you can read. List Locations and List Rooms return every item as a separate bundle, the unit Make passes from one module to the next, so you can write them into a spreadsheet and spot empty or duplicate entries.

What Make does not do here: SmartThings has no trigger module in Make, so nothing starts on its own when a device changes state. A scenario begins on Make's schedule or on another app's event. For anything the 15 modules skip, Make an API Call reaches the rest of the API. The same app is often available as a node in n8n too; the n8n vs Make comparison lays out the criteria, and the Make training helps if this is your first scenario.

Connect

How do you connect SmartThings to Make?

  1. 01

    Generate a token in SmartThings

    You need an active Samsung account. In your SmartThings account settings, open the Tokens section, click Generate New Token, tick the scopes your scenario needs, then click Generate and copy the token shown on screen.

  2. 02

    Add a SmartThings module in Make

    Open your scenario in Make, add any SmartThings module and click Create a connection. A connection is your SmartThings account linked to Make once, then reused by every SmartThings module. The Connection name field is optional but helps when you manage several homes.

  3. 03

    Paste the credentials and save

    Paste the token you copied, or follow the instructions Make shows on screen, and confirm. A Personal Access Token is meant for testing; OAuth credentials are the route when you build an integration for others.

First scenario

Your first scenario: open a new site in SmartThings

GoalWhen a new site shows up in the tool where you track your properties, Make creates its SmartThings location and a first room inside it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where your sites are listed as the first module, since SmartThings has no trigger of its own.

  2. 02

    Add Create a Location

    Click the + on the right, search for SmartThings and choose Create a Location. Click Create a connection, then map the site details coming from the first module.

  3. 03

    Chain Create a Room

    Add Create a Room after it. Map the location returned by the previous module so the room lands in the site you just created, not in an older one.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Read the bundles each module received to confirm the location and the room exist.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and turn the scenario on. From then on, each new site creates its SmartThings space without a manual step.

Modules

The 15 SmartThings modules in Make

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

SmartThings1

Create a Location

Action

In Make“Creates a location for a user.”

Gives you a brand new location in your SmartThings account, the top-level space that later holds rooms, rules and scenes. The result comes back as a bundle you can pass on to other modules.

When to use it
a new office, shop or rental unit enters your property list and needs its own SmartThings space.
Watch out
Run once really creates the location, so test with a sample row you are happy to delete afterwards.
SmartThings2

Create a Room

Action

In Make“Creates a room.”

Adds a room inside a location you choose, so devices and routines can be grouped the way the building is actually laid out. It pairs naturally with Create a Location placed just before it.

When to use it
a floor plan changes, or a freshly created site needs its first rooms.
Watch out
map the location from the previous module rather than picking one by hand, or every run fills the same place.
SmartThings3

Delete a Location

Action

In Make“Deletes a location.”

Removes a location from the account, which clears a site you no longer manage and keeps your lists short and readable. It acts on one location per bundle it receives.

When to use it
a lease ends or a property leaves your portfolio and its SmartThings space should go too.
Watch out
treat the deletion as final and add a filter that checks the exact location before this module runs.
SmartThings4

Delete a Room

Action

In Make“Deletes a room.”

Takes one room out of a location while leaving the rest of the site untouched. Useful when a space is merged, closed or renamed into something else and the old entry only adds noise.

When to use it
a renovation removes a meeting room and your records say so.
Watch out
fed by List Rooms, it deletes every room that search returns, so narrow the list with a filter first.
SmartThings5

Execute a Rule

Action

In Make“Executes a rule.”

Runs a rule you already built in SmartThings on demand, straight from your scenario. The logic stays inside SmartThings; Make simply decides the moment it fires.

When to use it
an event in another tool, like a signed check-in form, should kick off a rule that already exists.
Watch out
the rule has to exist in the location first; List Rules shows what is available before you pick one.
SmartThings6

Execute a Scene

Action

In Make“Executes a scene.”

Plays one of your SmartThings scenes the moment the scenario reaches this step. It is the shortest path from an outside event to a visible change in the building.

When to use it
a booking is confirmed in your calendar app and the room should switch to its welcome scene.
Watch out
each run uses an operation, one execution counted on your Make plan, so avoid calling the same scene from several branches.
SmartThings7

Get a Location

Action

In Make“Retrieves a location.”

Fetches the details of a single location when you already know which one you need. The data then flows into the next modules, ready to be mapped into a message, a sheet or a condition.

When to use it
before updating a site, you want its current details to compare or to copy elsewhere.
Watch out
it needs one precise location; to browse them all, List Locations fits better.
SmartThings8

Get a Room

Action

In Make“Retrieves a room.”

Reads one room and brings its details into the scenario, which lets later modules work with accurate information instead of a guess typed by hand.

When to use it
a support ticket names a room and you want its SmartThings record attached to the reply.
Watch out
the room belongs to a location, so make sure both references come from the same site when you map them.
SmartThings9

Make an API Call

Action

In Make“Performs an arbitrary authorised call.”

Opens the rest of the SmartThings API to your scenario, using the connection you already set up. Whatever the other listed modules leave out can be reached here with a custom request.

When to use it
you need something none of the listed modules covers, such as working with devices directly.
Watch out
you write the request yourself, so keep the SmartThings API reference open and test with Run once.
SmartThings10

Update a Location

Action

In Make“Updates a location.”

Changes an existing location so SmartThings stays in step with the source you trust, whether that is a property list, a CRM or an internal base. Nothing new is created.

When to use it
a site is renamed in your records and the SmartThings name should follow.
Watch out
pick the location from a Get or List module upstream, never from a typed name that might have changed.
SmartThings11

Update a Room

Action

In Make“Updates a room.”

Edits a room you already have instead of deleting and recreating it, so the room keeps its place in the location while its details change.

When to use it
an office becomes a meeting space and the room should carry its new name in the app.
Watch out
the room is found through its location, so map both from the same bundle to avoid editing the wrong one.
SmartThings12

List Locations

Search

In Make“Lists all locations currently available in a user account.”

Returns every location available in the connected account, each one as its own bundle. That turns a scattered setup into a list you can sort, filter or copy into a sheet.

When to use it
you manage several homes or sites and want an up-to-date inventory in one table.
Watch out
every module placed after it runs once per location, which adds operations quickly.
SmartThings13

List Rooms

Search

In Make“Lists rooms.”

Pulls the rooms of a location so you can check how a building is organized without opening the SmartThings app. It can return zero, one or many bundles.

When to use it
after a move or a renovation, compare the rooms in SmartThings with your own floor plan.
Watch out
the search can return several rooms, so add a filter before any module meant to act on one room only.
SmartThings14

List Rules

Search

In Make“Lists rules.”

Shows the rules configured for a location, handy for finding the one you want before you run it or for documenting how a site behaves.

When to use it
you are about to add Execute a Rule and need to know which rules exist on that site.
Watch out
the search returns several bundles, so place a filter before any module that should act on a single rule.
SmartThings15

List Scenes

Search

In Make“Lists scenes.”

Gathers the scenes available for a location, a quick way to see what can be triggered and to catch names that are no longer in use.

When to use it
you prepare an Execute a Scene step and want the exact scene rather than a similar-looking one.
Watch out
connect it to Execute a Scene only with a filter, or the scenario would play every scene on the list.
Need help

Need help automating SmartThings with Make?

A person reads every message.

FAQ

SmartThings and Make: common questions

01Is the SmartThings Make integration free?
Yes, on the Make side. SmartThings is a standard app, available from the Free plan. That 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 and count usage in credits per month. On the SmartThings side you need an active Samsung account; for any subscription, the SmartThings pricing page is the reference.
02What do you need to connect SmartThings to Make?
An active Samsung account and credentials from SmartThings. For testing, a Personal Access Token is enough: open Tokens in your account settings, click Generate New Token, select the scopes, click Generate and copy the token. For integration development, the doc points to OAuth credentials instead. In Make, add a SmartThings module, click Create a connection, name it if you like, paste the credentials or follow the on-screen steps. That single connection then serves all 15 modules.
03Can the SmartThings Make integration react in real time?
Not by itself. SmartThings has no trigger module in Make, neither scheduled nor instant, so a scenario never starts because something changed in SmartThings. Two ways work instead. Start the scenario on Make's schedule, set on the first module, every 15 minutes by default and down to 1 minute on a paid plan. Or open the flow with a trigger from another app, such as a form or a calendar, and let the SmartThings modules follow.
04What if a SmartThings module is missing in Make?
Use Make an API Call. It calls any endpoint of the SmartThings API with the same connection, which covers what the listed modules leave aside: the 15 modules focus on locations, rooms, rules and scenes. Keep in mind the warning attached to the doc: its content is AI-generated from the official SmartThings documentation and may contain mistakes. Check important details against the vendor, and contact SmartThings directly for questions about their documentation.
05Should you use Make or n8n for SmartThings?
It depends on the tool your team already runs and on the modules your case needs. On Make, SmartThings brings 11 actions and 4 searches, plus Make an API Call for the rest, all without a trigger. The same app is often available as a node in n8n as well. List the steps your scenario requires, check that each one exists in the tool you pick, and see which one fits the way your team already works.
Same platform

Other docs you might need on this stack.

Browse all integrations