Visual Automation Scenes
The Zapier‑style
automation engine for your buildings
Automation Scenes let you build “if this, then that” rules between your systems—when something happens in one module (Easyset, Tuya, fire panel, parking camera, etc.), TheBuildingCloud automatically runs one or many follow‑up actions.
Think of it as Zapier for your estate: choose a trigger, stack actions, set additional fields, share with operators, test safely and track every run in a central automation log.
Example automation scene
Parking → Lights & Access
Parking camera reads specific number plate
Module: Parking camera (ANPR) · Event: read_specific_number_plate
• Open Easyset entrance relay and log the access event
• Switch on Tuya car‑park lights to 80% brightness
• Email on‑duty operator with plate, time and scene details
Modules
Tuya, Easyset, Parking‑camera
Last run
Just now · Success
Logs
10 events · 0 errors
One visual scene builder for all your systems
Automation Scenes sit on top of your existing devices and services. Each scene has a single trigger module (for example Easyset, Tuya, firebird or parking camera) and one or more action modules that define what should happen next.
Under the hood, each scene is stored as structured JSON (mainSelectedModule + actionSelectedModule), evaluated by a central automation engine and written to an automation‑scene log so you can see exactly what ran, when, and why.
Choose a trigger module & event
Use module events (from AutomationScene events) to define what starts the scene—like a device state change, new PIN, fire input or ANPR read.
Add one or many actions
Chain actions across Tuya, Easyset, firebird, email notifications and more. Each action has its own device, event and optional additional fields and device outputs.
Share, test and go live
Share scenes with operators, test them safely via the built‑in test runner (self‑webhook payloads), then activate with a single toggle—everything audited in automation logs.
Trigger modules
Use real device and system events as the starting point for automation:
- • Easyset entrance PIN events
- • Tuya device events (lights, IoT)
- • Firebird and firebird‑IO inputs
- • Parking‑camera number plate reads
- • Other webhook‑based integrations
Action modules
Combine multiple actions in a single scene:
- • Tuya: switch lights, change brightness
- • Easyset: open relays, trigger access
- • Custom email notifications
- • Firebird event responses
- • Operator & engineer notifications
- • Parking workflows with VRM lists
Enterprise‑grade controls
Built‑in safety and governance designed for large portfolios:
- • Role‑based access (organization, operators)
- • Scene assignment to specific operators
- • Detailed automation logs per scene
- • Safe “Test Scene” runner for payloads
- • Enable/disable scenes with a single toggle
How an automation scene is built
Every scene follows the same pattern: Trigger → optional filters → one or many Actions, with safe testing and logs.
1 · Trigger (mainSelectedModule)
Choose where the automation starts: an Easyset entrance event, Tuya device change, firebird input, parking‑camera read, etc.
- • Module (e.g. easyset, tuya, firebird, parking-camera)
- • Event (e.g. new PIN, fire input open/close, number plate read)
- • Device and optional device category / outputs
2 · Actions (actionSelectedModule[])
Add one or many actions that should run whenever the trigger fires—across any supported module.
- • Tuya: switch lights, change brightness, toggle devices
- • Easyset: fire relays, unlock entrances, manage outputs
- • Custom email notifications and operator / engineer alerts
- • Parking flows: update VRM lists, open barriers and more
3 · Sharing, testing & logs
Control who can see and run scenes, test them safely, and troubleshoot with full history.
- • Assign scenes to specific operators or keep them organization‑only
- • Use the “Test Scene” endpoint to simulate triggers without waiting for live events
- • Review automation‑scene logs to understand each run and outcome
- • Toggle scenes on/off without deleting configuration
Why it feels like Zapier (but built for buildings)
Instead of connecting web apps like email and CRMs, TheBuildingCloud connects panels, cameras, access controllers and IoT devices—using the same “when X happens, do Y and Z” mental model your team already understands.
No‑code editor
Create and update scenes from the UI—no scripts or custom code required.
Device‑aware
Understands device types, outputs, categories and events in your portfolio.
Safe by design
Role‑based permissions, scene‑level sharing and explicit test mode.
Fully auditable
Every run is logged with timestamps, modules, events and outcomes.
Real‑world automation playbooks
A few examples of what teams build with Automation Scenes in TheBuildingCloud.
01 · Secure visitor parking
When an ANPR camera recognizes a registered plate, automatically open the barrier, switch on bay lighting and notify security with the full access log.
Parking‑camera trigger · Easyset + Tuya + email actions
02 · After‑hours access
When a late‑night PIN is used, turn on corridor and lobby lights, temporarily enable CCTV recording profile, and email the duty manager with a summary.
Easyset trigger · Tuya + firebird actions · Custom emails
03 · Alarm‑driven response
On a firebird input change, unlock emergency exits, trigger signage, email safety officers and create a full incident log in the automation scene history.
Firebird trigger · access + notification actions · full logs
Ready to automate your building?
See Automation Scenes in a live demo
Our team can walk you through real configurations—from simple “lights on” rules to complex, multi‑module incident playbooks—so you can see exactly how Automation fits your portfolio.