Quick Start
1
Get API Key
Generate at Rhombus Console → Settings → API Management
2
Connect in Zapier
Search “Rhombus” in Zapier, authenticate with your API key
3
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
Common Patterns
Emergency Alerts
Access Automation
Incident Logging
Scheduled Maintenance
Zapier 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 unlocking door |
| Formatter | Transform data | Format timestamps, parse JSON |
Pricing
| Plan | Tasks/Month | Zaps | Polling Interval | Use Case |
|---|---|---|---|---|
| Free | 100 | 5 | 15 min | Testing |
| Starter | 750 | 20 | 15 min | Small setups |
| Professional | 2,000+ | Unlimited | 1-2 min | Production |
| Team/Enterprise | Custom | Unlimited | 1 min | Large deployments |
Each trigger fire = 1 task. Multi-step Zaps count each action as 1 task. Example: Button press → 3 actions = 3 tasks.
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 |
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 |