Skip to main content
Traducción en progreso: Esta página muestra el contenido en inglés mientras finalizamos la traducción al español.
Automate Rhombus API operations using Make.com’s (formerly Integromat) visual workflow builder. Alternative to writing custom code for common integration patterns.

Quick Start

1

Get API Key

Generate API key at Rhombus Console → Settings → API Management
2

Connect in Make

Add Rhombus module in Make.com, authenticate with your API key
3

Build Scenario

Add modules, configure actions, test and activate

Available Modules

Access Control

ModuleFunctionAPI Equivalent
Add Users to GroupAdd users to access control groupsPOST /api/accesscontrol/addUsersToAccessControlGroup
Create GroupCreate new access control groupPOST /api/accesscontrol/createAccessControlGroup
Assign CredentialAssign unassigned credential to userPOST /api/accesscontrol/assignUnassignedCredential
Delete UserRemove user from organizationDELETE /api/user/deleteUser

Camera & Video

ModuleFunctionAPI Equivalent
Create HTTP StreamGenerate raw HTTP video streamPOST /api/camera/createRawHttpStream
Create SeekpointAdd custom marker to video timelinePOST /api/camera/createCustomSeekpoint
Get AI ThresholdsRetrieve AI confidence thresholdsGET /api/camera/getAINormalizedConfidenceThresholds
Get Hardware DetailsFetch camera hardware specificationsPOST /api/camera/getHardwareDetailsForMultipleCameras

Sensors

ModuleFunctionAPI Equivalent
Get BLE Base StationsRetrieve Bluetooth sensor base stationsGET /api/sensor/getBaseStationsForBleSensors

Universal

ModuleFunction
Make API CallExecute any Rhombus API endpoint with custom parameters
All modules map to Rhombus REST API endpoints. See API Reference for detailed endpoint documentation.

Authentication

# Get API key from Rhombus Console
https://console.rhombussystems.com/settings/api-management/

# Use in Make.com connection
API Key: YOUR_RHOMBUS_API_KEY
Base URL: https://api2.rhombussystems.com
Treat API keys as passwords. Each key has full API access with your account permissions.

Common Patterns

Employee Onboarding

HR System → Make.com → Rhombus
1. Trigger: New employee in HRIS
2. Create/update access group
3. Assign credential
4. Log to audit system

Video Stream Integration

Schedule → Make.com → Rhombus → Analytics Platform
1. Trigger: Scheduled interval
2. Get camera list
3. Create HTTP streams
4. Send URLs to analytics system

Temporary Access

Check-in System → Make.com → Rhombus
1. Trigger: Visitor check-in
2. Add to temporary access group
3. Schedule removal (time-based)
4. Send notification when access expires

Make.com Platform Features

FeaturePurpose
RoutersBranch workflows based on conditions
FiltersExecute modules conditionally
IteratorsProcess arrays item-by-item
AggregatorsCombine multiple operations
Error HandlersCatch and handle failures
WebhooksTrigger scenarios from external events

Pricing

PlanOperations/MonthUse Case
Free1,000Testing, personal use
Core10,000+Small teams
ProCustomProduction workloads
Each module execution = 1 operation. A 5-module scenario running 100 times = 500 operations.

Troubleshooting

IssueSolution
Auth failsVerify API key is active at console.rhombussystems.com
Module errorsCheck execution history for error details; verify required fields
Rate limitsRhombus API: 1000 req/hr. Add delays between operations if hitting limits
Data mappingUse Make.com’s data structure viewer; verify field paths

When to Use Make vs Custom Code

Use Make.com WhenWrite Custom Code When
Standard CRUD operationsComplex business logic required
Connecting existing appsBuilding custom UI/UX
No-code team membersNeed sub-second latency
Rapid prototypingHighly customized workflows
Visual workflow preferredVersion control critical

Resources