Low Code / No Code
Integrate with Zapier
Connect Rhombus to thousands of apps with the native Zapier integration — build event-driven automations for camera alerts, doors, and sensors without code.
On this page
Native Zapier integration for Rhombus. Create automated workflows triggered by camera events, door activity, button presses, and sensor alerts. No-code alternative to webhook integrations.
Quick start
- Get API Key
Generate an API key in the Rhombus Console under Settings → Integrations & Developer Resources → API Tokens → Add API Key
- Connect in Zapier
Search "Rhombus" in Zapier, authenticate with your API key
- Create Zap
Choose trigger → Configure action → Test → Activate
Available triggers
| Trigger | Type | Description |
|---|---|---|
| New Rule Event | Instant | Fires when Rhombus Rules Engine condition is satisfied |
| New Button Event | Instant | Button device pressed (e.g., panic button) |
| New Door Sensor Event | Instant | Door open/close/forced events |
| New Environment Sensor Event | Instant | Temperature, humidity, air quality alerts |
| New Audit Record | Polling | Security event audit logs created |
| New Camera Clip | Polling | Video clip saved to library |
| New Custom Footage Seekpoint | Polling | Custom marker added to video timeline |
Instant triggers use webhooks (real-time). Polling triggers check every 1-15 minutes depending on plan.
Available actions
| Action | Description | Key Parameters |
|---|---|---|
| Unlock Door | Remotely unlock access-controlled door | Door ID, duration |
| Create Clip | Save video clip from camera | Camera, start/end time, title |
| Create Live Stream | Generate shareable stream URL | Camera, expiration, password |
| Reboot Camera | Restart camera device | Camera ID |
| Toggle Privacy Mode | Enable/disable camera feed visibility | Camera ID, state |
| Play Audio | Broadcast audio message | Gateway ID, audio file |
| Create Seekpoint | Add timeline marker to footage | Camera, timestamp, label |
| Update Camera Config | Modify camera settings | 20+ configuration options |
| Toggle Audio Recording | Enable/disable audio capture | Gateway ID, state |
Authentication
Generate your API key in the Rhombus Console. EU organizations use console.eu.rhombussystems.com — see API Regions.
API keys have full account permissions. Treat as passwords.
Common patterns
Emergency alerts
Button Press (Instant) → Zapier → Multiple Actions
1. Send SMS via Twilio
2. Post to Slack #security
3. Create ServiceNow ticket
4. Email security teamAccess automation
Google Form Submit → Zapier → Rhombus
1. Visitor submits check-in form
2. Post the visitor's name to Slack #front-desk
3. Play welcome message via audio gateway
4. Log entry in Google SheetsDon't unlock a door from a form anyone can submit: let the front desk admit the visitor, or issue a guest pass.
Incident logging
Door Forced Event (Instant) → Zapier → Logging
1. Capture door event data
2. Create video clip of incident
3. Log to Google Sheets/Airtable
4. Send alert to security channelScheduled maintenance
Schedule by Zapier → Rhombus Actions
1. Weekly trigger at 3 AM
2. Reboot cameras in sequence
3. Toggle privacy mode during maintenance
4. Send completion reportZapier platform features
| Feature | Purpose | Rhombus Use Case |
|---|---|---|
| Filters | Conditional execution | Only alert if event type = "forced entry" |
| Paths | Branch workflows | Route different door events to different teams |
| Multi-Step | Chain multiple actions | Alert → Create clip → Log → Notify |
| Delay | Time between actions | Wait 30 seconds before creating a clip |
| Formatter | Transform data | Format timestamps, parse JSON |
Pricing
For current pricing details, see Zapier Pricing.
Troubleshooting
| Issue | Solution |
|---|---|
| Auth fails | Verify API key active at console.rhombussystems.com |
| Trigger not firing | Check Zap history; verify event occurring in Rhombus Console; check polling interval |
| Action fails | Review Zap history errors; verify required fields populated; test individually |
| Instant triggers delayed | Webhook delivery can take 1-30 seconds; check Zapier webhook logs |
| Polling triggers slow | Free/Starter: 15 min intervals; Upgrade for faster polling |
Instant vs polling triggers
| Type | Triggers | Speed | How It Works |
|---|---|---|---|
| Instant | Rule Event, Button, Door, Environment Sensor | 1-30 sec | Rhombus sends webhook to Zapier when event occurs |
| Polling | Audit Record, Clip, Seekpoint | 1-15 min | Zapier checks Rhombus API on schedule |
Use instant triggers for time-sensitive alerts (panic buttons, door forced). Use polling for logging and reporting.
When to use Zapier vs webhooks
| Use Zapier When | Use Native Webhooks When |
|---|---|
| Need visual workflow builder | Writing custom code anyway |
| Connecting to 3rd party apps | Handling webhooks internally |
| No developer resources | Need sub-second latency |
| Rapid prototyping | Complex data transformations |
| Team collaboration via UI | Webhook-native architecture |
See Webhook Listener Implementation for native webhook setup.
Resources
Official Rhombus triggers and actions
1,000+ API endpoints for custom integrations
Generate and manage API keys
Contact Rhombus Support for help with your integration.