- Home
- Resources
- Integrations
- The Keys Pro
The Keys Pro Make integrationAutomate The Keys Pro with Make.
Can Make act on The Keys Pro for you? Yes, through one action module. This The Keys Pro Make integration guide shows how to link your account, where that module fits in a scenario, and how to test it before it runs on its own.
Verified Trustpilot reviews · AI, automation & growth agency
What can the The Keys Pro Make integration do?
This integration lets a Make scenario, the automation you build in Make, send a request to your The Keys Pro account. It offers a single module, one brick of that scenario: the action Create Keypad Share. Something else has to start the scenario, because the app brings no trigger of its own.
Start from another tool. Since The Keys Pro has no trigger, the first bubble of your scenario belongs to another app, a form, a booking tool or a spreadsheet, and Create Keypad Share comes right after it. Each item passed from one module to the next is called a bundle.
Start from the clock. You can also let Make launch the scenario on its schedule, every 15 minutes by default, and run the action each time. The module name points to a share on a keypad; Make does not describe it further, so read the fields the module shows once your connection exists.
Know the limits. Make itself warns that its documentation for The Keys Pro is limited, because there is not enough public information about the app. No module watches events, looks data up or opens a generic route to the rest of the app. Test every scenario with Run once before you rely on it, and keep the Make troubleshooting guide open if a run fails.
If you are weighing tools, the n8n vs Make comparison sets out the criteria, and the Make training covers scenario building from the ground up.
How do you connect The Keys Pro to Make?
- 01
Add the module
In a scenario, click the +, search for The Keys Pro and pick Create Keypad Share. Then click Create a connection. A connection is your The Keys Pro account linked to Make once and reused by every module of the app.
- 02
Name and authorize
Give the connection a name if you like, which helps when several accounts exist. Then authorize Make on the page The Keys Pro opens, or paste the key the app gives you, depending on what the connection window asks for.
- 03
Save the connection
Click Save. Make returns to the module, and the connection now appears in its dropdown. From there you can fill the fields of Create Keypad Share and keep building the rest of the scenario.
Your first scenario with The Keys Pro
GoalWhen something happens in another app, Make runs Create Keypad Share in The Keys Pro.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app whose event should start everything, such as a form tool.
- 02
Add The Keys Pro
Click the + on the right of that first module, search for The Keys Pro and choose Create Keypad Share. Select your connection, or create it now with Create a connection.
- 03
Fill and map the fields
Fill the fields the module shows. Where a value should come from the first app, click the field and map data from the previous module instead of typing it, so each bundle carries its own values.
- 04
Test with Run once
Click Run once to execute the scenario one time. Open the bubbles to read the bundles each module received, then check in The Keys Pro that the result is the one you expected.
- 05
Schedule and switch on
Set the schedule on the first module, every 15 minutes by default, or 15 minutes at the shortest on the Free plan. Then switch the scenario on so it keeps running without you.
What the The Keys Pro module does
The Keys Pro gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Keypad Share
ActionIn the docs onlyGoing by its name, this action creates a share tied to a keypad each time a bundle reaches it. As the app's only module, it always follows another app's trigger or Make's schedule.
Need help automating The Keys Pro with Make?
A person reads every message.