Resources · Make integration

The Keys Make integrationAutomate The Keys with Make.

Can a door open itself when another tool says so? The Keys Make integration gives you 4 action modules: open the door, close it, create a share with a digicode and read user info. This page shows how to connect your account and build a first scenario.

Try the The Keys integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the The Keys Make integration do?

The Keys Make integration lets a scenario, the automation you build in Make, act on your The Keys access without you touching the app. It has no trigger of its own: another app or the Make schedule starts the scenario, then a The Keys module does the work, such as creating a digicode share or opening a door.

Guest access handed out on its own. A reservation lands in your booking tool, and Create Share with digicode prepares the access for that guest. Each module is one brick of the scenario; this one follows the booking app's trigger.

A door that answers a form or a message. Open the door and Close the door let a scenario act on the lock when another app gives the signal. A cleaning crew checks in through a form, the door opens; the form says the job is done, the door closes.

A quick check before acting. Get User Info reads account information through your connection, which helps confirm the scenario talks to the right The Keys account before it touches a door.

What Make does not give you here: no trigger, so The Keys cannot start a scenario by itself, and no Make an API Call module to reach a feature the four modules skip. The Make documentation for this app is marked as AI-generated and asks you to check important details with The Keys directly.

Before you commit, the Make review covers the tool as a whole, Make pricing explains the plans, and n8n vs Make helps if you still weigh the two platforms.

Connect

How do you connect The Keys to Make?

  1. 01

    Prepare your credentials

    You need a The Keys account and an active Google Cloud account with billing enabled and the right IAM roles. In the Google Cloud console, open APIs and services, then Credentials, and create an OAuth client ID.

  2. 02

    Copy the Client ID and secret

    If Google asks for a callback URI, paste https://www.integromat.com/oauth/cb/the-keys, then click Create. Copy the Client ID and the Client secret shown on screen; Make asks for them next.

  3. 03

    Create the connection in Make

    Add any The Keys module to your scenario and click Create a connection. Give it a name in Connection name if you like, then enter your credentials. This connection is your account linked to Make once, reused by all four modules.

First scenario

Your first scenario with The Keys

GoalWhen a booking arrives in another app, Make checks your The Keys account and creates a share with a digicode for the guest.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app that receives your bookings as the first module: it is the trigger, since The Keys has none.

  2. 02

    Add Get User Info

    Click the + on the right of the first module, search for The Keys and choose Get User Info. Click Create a connection and use the credentials you prepared.

  3. 03

    Add Create Share with digicode

    Add one more module with the + and pick Create Share with digicode. Fill its fields and map the guest data from the booking module into them.

  4. 04

    Test with Run once

    Click Run once and read the bundles each module received. A bundle is one item passed along, here one booking. Use a test booking, because the share is created for real.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Modules

What each The Keys module does

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

The Keys1

Close the door

ActionIn the docs only

This module lets a scenario close a door linked to your The Keys account, so nobody has to remember it once the reason for opening is over. It is an action: it acts on one item each time it runs.

When to use it
at the end of a flow, when another app reports that a visit, a delivery or a cleaning job is finished.
Watch out
Run once acts on the real lock, so test when someone can check the door.
The Keys2

Create Share with digicode

ActionIn the docs only

Here you get access handed out without opening The Keys: the module creates a share with a digicode, which suits guests or contractors who should come in without a physical key.

When to use it
right after a trigger from your booking or scheduling tool, mapping the person's details from that module.
Watch out
the Make documentation lists no fields for this module, so read what the editor shows once the connection exists before you map anything.
The Keys3

Get User Info

ActionIn the docs only

A read step rather than a door step: the module brings back user information from the The Keys account behind your connection, which you can then map into later modules or another app.

When to use it
as a check at the start of a scenario, or when a message to a team needs account details.
Watch out
Make has no official description for it, so run it once and look at the bundle before relying on any value.
The Keys4

Open the door

ActionIn the docs only

With this module a scenario unlocks a door linked to your The Keys account when another app gives the signal, so the right person gets in without a phone call to you.

When to use it
when a form, a check-in or a message from another tool confirms that someone is expected now.
Watch out
a door opened by a scenario stays your responsibility; pair it with Close the door later in the flow, and test with Run once only on site.
Need help

Need help automating The Keys with Make?

A person reads every message.

FAQ

The Keys and Make: common questions

01Is the The Keys Make integration free?
Yes, on the Make side. The Keys is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, and up to 5 minutes per run. Paid plans such as Core, Pro, Teams and Enterprise lower the interval to 1 minute and count usage in credits per month. Your The Keys subscription is separate, and the Google Cloud account the connection requires has to keep billing enabled, so check both costs on the vendors' own pages.
02What do you need to connect The Keys to Make?
Three things: a The Keys account, an active Google Cloud account with billing enabled and the required IAM roles, and an OAuth client ID created in the Google Cloud console under APIs and services, then Credentials. You copy the Client ID and Client secret, click Create a connection in a The Keys module, and paste them. If Google asks for a callback URI, use the Make address given in the documentation for this app.
03Does The Keys trigger Make in real time?
No, because The Keys has no trigger in Make at all. A scenario must start elsewhere: on the trigger of another app, such as a booking or form tool, or on a Make schedule, every 15 minutes by default. If that other app offers an instant trigger, it calls Make through a webhook as soon as something happens, and the The Keys module then runs right after it in the same scenario.
04What if a The Keys module is missing in Make?
It depends on what you need. The app offers only four actions, open the door, close it, create a share with a digicode and read user info, and it has no Make an API Call module to reach anything else. For a missing feature, look for another app in Make that covers the step, or describe your case in the help form on this page. The Make documentation for The Keys is marked as AI-generated, so confirm details with The Keys directly.
05Should you use Make or n8n for The Keys?
It depends on where your other automations live. On Make, The Keys brings four actions and no trigger, with a connection through Google Cloud OAuth credentials. n8n often has a node for the same apps, so check whether The Keys is among them before choosing. Pick the platform where the tools around your doors, booking and forms, already run, since the lock always follows a trigger from one of them.
Same platform

Other docs you might need on this stack.

Browse all integrations