Resources · Make integration

Rhombus Make integrationAutomate Rhombus with Make.

Can Make open a door or restart a camera when something happens in another tool? The Rhombus Make integration gives you 19 action modules for access control, cameras, buttons and audio. This page shows how to connect your account and build a first scenario.

Try the Rhombus integration on MakeSee the 19 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Rhombus Make integration automate?

The Rhombus Make integration links your Rhombus account to Make, a tool where you build automations without code. Each automation is a scenario, a chain of modules, and each module is one brick: here, an action on your Rhombus doors, cameras, buttons or audio clips. Rhombus has no trigger in Make, so another app or a schedule starts the scenario.

Door access that follows your HR tool. When a hire starts, Create an Access Control Group and Add Users to an Access Control Group set up their access. When they leave, Delete a User takes them out. Nobody has to remember to open the console.

A camera fleet you can check from a spreadsheet. Get the Minimal Camera State List and Get Details for Devices send what Rhombus knows about your cameras to a sheet or a chat channel, and Reboot a Camera restarts the one your team flags.

Events marked on the footage. Create a Custom Seekpoint leaves a marker on a camera when a refund, an alarm or a ticket shows up in another tool, and Fetch Sensor Seekpoints for Cameras brings those marks back when you review an incident.

What Make does not do here: nothing in Rhombus can start a scenario by itself, and Make's documentation for this app is AI-generated from the Rhombus docs, so check important details with Rhombus. The same app may also exist in n8n, and the n8n vs Make page lays out both tools. The Make training covers scenario design, and Make troubleshooting helps when a run fails.

Connect

How do you connect Rhombus to Make?

  1. 01

    Generate an API key in Rhombus

    In the Rhombus Console, open Settings, then API Management. Generate a new API key if you do not have one yet, copy the key displayed on screen and keep it at hand for the next step.

  2. 02

    Add a Rhombus module in Make

    Inside your scenario, add any Rhombus module and click Create a connection. A connection is your Rhombus account linked to Make once: every Rhombus module you add later reuses it.

  3. 03

    Name the connection and paste the key

    The Connection name field is optional, but a clear label helps when you manage several accounts. Paste the API key you copied from Rhombus, or follow the on-screen instructions, to finish.

First scenario

Build your first scenario with Rhombus

GoalWhen a visit is approved in another app, Make unlocks a Rhombus door and leaves a seekpoint on the camera you chose.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. The first module comes from the app where visits get approved, a booking tool or a form, because Rhombus has no trigger of its own.

  2. 02

    Add the door module

    Click the + on the right of that first module, search for Rhombus and pick Unlock an Access Controlled Door. Click Create a connection and paste your API key.

  3. 03

    Choose the door and add the seekpoint

    Fill the fields of the door module; once the connection exists, Make lists what it can read. Then add Create a Custom Seekpoint and map the visit details that the first module sent.

  4. 04

    Test with Run once

    Click Run once and read the bundles, the items each module received. The test opens the door for real, so run it while someone expects it on the other side.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default, unless the other app has an instant trigger) and switch the scenario on. Each module run on a bundle counts as one operation.

Modules

What each Rhombus module does

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

Rhombus1

Add Users to an Access Control Group

ActionIn the docs only

New people join a team, and their door access should follow them. This module places the users you pick into a Rhombus access control group, so the rules of that group apply to them without anyone opening the console.

When to use it
when a hire is marked as started in your HR tool, to add them to the group of their office.
Watch out
every bundle that reaches the module costs an operation, so trim the incoming list before this step rather than after.
Rhombus2

Assign an Access Control Credential

ActionIn the docs only

Linking a credential to a person is the step that actually lets them through the door. Assign an Access Control Credential does it from your scenario, which spares a trip to the Rhombus console every time someone receives a new one.

When to use it
when the front desk logs a handed-out credential in a form and that entry should reach Rhombus on its own.
Watch out
Make's documentation gives no field detail here, so open the module and read what it asks before mapping data.
Rhombus3

Create a Custom Seekpoint

ActionIn the docs only

Finding the right minute of footage gets easier when a marker is already waiting there. This module adds a seekpoint of your own on a camera at the moment another app reports something, so the moment is labeled before anyone goes looking.

When to use it
when a refund at the register or an alarm in another tool should leave a trace on the matching camera.
Watch out
map the camera from an earlier module instead of typing it, or every run marks the same one.
Rhombus4

Create a Raw HTTP Stream

ActionIn the docs only

Some screens and tools outside Rhombus need a stream address rather than the Rhombus app itself. This module asks Rhombus for a raw HTTP stream and passes its details to the next module of your scenario.

When to use it
when a lobby display or an internal page should show one camera on request.
Watch out
the documentation says nothing about how long a stream stays usable, so run the scenario with Run once and read the bundle before you share the result with anyone.
Rhombus5

Create an Access Control Group

ActionIn the docs only

A new site, floor or team usually calls for its own set of access rules. Create an Access Control Group builds that group in Rhombus straight from your scenario, ready for Add Users to an Access Control Group in the next step.

When to use it
when a new location is added in your project tool and needs a group before anyone gets assigned to it.
Watch out
running the scenario twice on the same input may leave you with two groups, so test with a dummy name first.
Rhombus6

Delete a User

ActionIn the docs only

Offboarding is where forgotten access does the most harm. Delete a User removes a person from your Rhombus organization as soon as the scenario receives the signal, instead of waiting for someone to think of it.

When to use it
when an employee is marked as departed in your HR tool.
Watch out
a deletion cannot be undone from Make. Keep the test on a dummy account, and make sure only confirmed departures ever reach this module in the live scenario.
Rhombus7

Fetch Sensor Seekpoints for Cameras

ActionIn the docs only

Scrolling through hours of video is slow; reading the marks sensors left is faster. This module pulls the sensor seekpoints recorded on the cameras you choose, ready to be mapped into a sheet, a message or a report.

When to use it
when you review an incident and want every sensor mark for the cameras involved gathered in one place.
Watch out
check in the Run once output how many bundles come back before deciding what the next module does with them.
Rhombus8

Get Button Press Events

ActionIn the docs only

A Rhombus button is only useful if someone reacts to it. Get Button Press Events reads the presses Rhombus logged, so Make can hand them to the people or tools that should respond.

When to use it
at a reception desk or in a warehouse, when a press should end up as a chat message or a ticket.
Watch out
this is an action, not a trigger. It reads events when the scenario runs, on its schedule, never at the exact moment of the press.
Rhombus9

Get Details for Devices

ActionIn the docs only

Before acting on a device, you want to know exactly which one you are dealing with. Get Details for Devices fetches what Rhombus holds about the devices you point it to and hands that record to the following modules.

When to use it
for an equipment inventory in a spreadsheet, or as a check right before a reboot or a settings change.
Watch out
map its output in later modules rather than retyping values, so swapping a device in Rhombus does not break the scenario.
Rhombus10

Get a Base Station

ActionIn the docs only

Pulling up the record of one base station no longer requires the console. This module brings it into your scenario as a bundle that any later module can read, write down or send.

When to use it
when a site audit or a support ticket needs the facts about one base station and the person asking has no Rhombus access.
Watch out
it reads a single base station per run; to cover several, feed it a list from an earlier module and budget one operation for each.
Rhombus11

Get a Camera AI Threshold

ActionIn the docs only

Reading a setting comes before changing it. Get a Camera AI Threshold returns the current AI threshold of one camera and passes the value down the scenario, where you can store it or compare it.

When to use it
to keep a log of camera settings, or just before Update a Camera AI Threshold so the old value stays on record.
Watch out
the value only means something next to the camera it came from, so map the camera along with it wherever you write it.
Rhombus12

Get the Audio Upload Metadata for Org

ActionIn the docs only

Every audio clip uploaded to your Rhombus organization carries metadata, and this module lists it for Make. You get the reference needed to pick the right clip before playing it.

When to use it
as the step before Play an Audio Upload, so the scenario picks a clip from fresh data instead of a value typed by hand.
Watch out
a value typed once and never refreshed can point to a clip that no longer exists; reading the metadata at each run avoids that.
Rhombus13

Get the Minimal Camera State List

ActionIn the docs only

In a single run, you see the state of every camera in your organization in a light list. It fits scenarios that only need the status and can skip the full detail of each device.

When to use it
as the first module of a scheduled check that warns a team when a camera needs attention.
Watch out
each camera in the list can turn into its own bundle further down, and every module that processes those bundles adds operations to your plan.
Rhombus14

Get the Rules for a Button

ActionIn the docs only

What does a given button actually do when pressed? This module reads the rules attached to one Rhombus button, so you can document them or check them from Make without clicking through the console.

When to use it
during a site audit, to write each button's rules into a shared spreadsheet.
Watch out
it reads rules and does not change them. For anything the listed modules cannot do, look at Make an API Call and the Rhombus API documentation.
Rhombus15

Make an API Call

ActionIn the docs only

When no listed module covers your need, this one reaches any endpoint of the Rhombus API with the connection you already set up. No second login, no separate setup.

When to use it
for a Rhombus feature that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the Rhombus API documentation open. Make also warns that its own Rhombus page is AI-generated and may contain mistakes, so verify what matters with Rhombus.
Rhombus16

Play an Audio Upload

ActionIn the docs only

A clip you already uploaded to Rhombus can be played on cue from a scenario, started by an event in another tool rather than by someone on site pressing play.

When to use it
when an after-hours alert in another app should be answered with a recorded message, picked with Get the Audio Upload Metadata for Org.
Watch out
Run once plays the clip for real, so test at a moment when nobody nearby will be surprised by it.
Rhombus17

Reboot a Camera

ActionIn the docs only

Restarting a camera from a scenario spares someone a trip to the console or to the device. Reboot a Camera sends the restart order to the camera you choose or map from an earlier module.

When to use it
after Get the Minimal Camera State List, for a camera your team has flagged as misbehaving.
Watch out
a Run once test reboots the camera for real. Pick one where a restart during working hours would not bother anyone.
Rhombus18

Unlock an Access Controlled Door

ActionIn the docs only

Opening a door from an automation is the most tangible thing Rhombus does in Make. This module unlocks the access controlled door you select, driven by whatever event starts the scenario.

When to use it
when a delivery is confirmed in another tool, or a visitor is approved in a booking app.
Watch out
anyone allowed to edit or run the scenario can open that door. Limit who edits it, and test only when someone is there to close it.
Rhombus19

Update a Camera AI Threshold

ActionIn the docs only

Changing the AI threshold of many cameras by hand gets tedious fast. This module sets it from Make, one camera per bundle, using values that can come from a sheet or from another app.

When to use it
when an area changes use, a stockroom turned into a loading bay for example, and its cameras need a new setting.
Watch out
read the current value with Get a Camera AI Threshold first and store it, so you can put it back if the result disappoints.
Need help

Need help automating Rhombus with Make?

A person reads every message.

FAQ

Rhombus and Make: common questions

01Is the Rhombus Make integration free?
Yes. Rhombus is a standard app in Make, so its 19 modules work on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between 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) lower the interval to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution, with usage counted in operations each month. You still need your own active Rhombus account, billed by Rhombus.
02What do you need to connect Rhombus to Make?
An active Rhombus account and an API key. You generate the key in the Rhombus Console: open Settings, then API Management, create a new key if you have none, and copy it. In Make, add any Rhombus module, click Create a connection, give it a name if you like, and paste the key. That single connection then serves every Rhombus module, Make an API Call included, so you set it up once per Rhombus account. If you manage several organizations, name each connection after the account it covers.
03Can a Rhombus event start a Make scenario in real time?
No. Rhombus has no trigger module in Make, neither scheduled nor instant, so nothing on the Rhombus side starts a scenario by itself. You have two ways in. Put a Rhombus module first and let the scenario's schedule run it, every 15 minutes by default and down to 1 minute on paid plans. Or open the scenario with a trigger from another app, a form or an HR tool, and place Rhombus modules after it. Get Button Press Events, for example, reads presses when the scenario runs, not at the moment of the press.
04What if a Rhombus module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Rhombus API through the connection you already have, so the listed modules are not a ceiling. You write the request yourself, which means reading the Rhombus API documentation. Make's own page for this app states that it was AI-generated from the Rhombus documentation and may contain mistakes, so confirm important details with Rhombus, the right contact for questions about its API. When the need sits outside Rhombus, such as sending a message, add another app's module to the same scenario.
05Should you use Make or n8n for Rhombus?
It depends on your criteria, and this page only covers the Make side. In Make, Rhombus comes with 19 action modules, Make an API Call among them, no trigger, and it works from the Free plan. Many apps also have an n8n node, so check whether Rhombus has one before comparing anything. Then weigh which editor your team already knows, how your flows start, since Rhombus in Make relies on a schedule or another app's trigger, and which other tools each flow touches.
Same platform

Other docs you might need on this stack.

Browse all integrations