Loading…
About Us
Pricing Contact Us Login Start Free Trial

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.

Talk to our automation team → Available on the Enterprise plan with full scene logs and testing tools.
WHEN THEN LIVE PIN entry Fire panel ANPR Unlock Lights CCTV Notify IF → THEN ANPR · NJ12 CGK matched → barrier open PIN · Main entrance → camera + push Fire · Block A → exits released + SMS
Automation

If/then scenes across access, parking and devices

Triggers

ANPR · Alarms · Pins

Actions

Unlock · Notify · IoT

Scene builder

One visual scene builder for all your systems

Every scene has a single trigger module and up to five ordered action steps. Pick them from dropdowns, no code, and the automation engine runs them the moment the trigger fires.

Build a scene in 3 steps

  1. Step 1

    Choose a trigger module & event

    Pick the module, device and event that starts the scene: a PIN entrance opening, a fire input, a Tuya switch or an ANPR plate read.

  2. Step 2

    Stack your action steps

    Add up to five steps across Easyset, FireBird, Tuya, CCTV, notifications and webhooks, each with its own device, outputs and message.

  3. Step 3

    Test, share and go live

    Run a safe test, share the scene with operators, then switch it on. Every run is written to the scene log.

scene.json
"mainSelectedModule": {
  "module": "Cam Capture",
  "event": "Read Match Data"
},
"actionSelectedModule": [
  { "module": "Easyset", "event": "Open entrance" },
  { "module": "Notification", "event": "Email" }
]

Trigger modules

What starts a scene

  • Easyset

    Entrance open, PIN changes, intercom calls

  • FireBird

    Fire, fault, input open/close, offline

  • Tuya

    Switch, brightness, SOS, door contact

  • Cam Capture ANPR

    Plate reads with allow/deny lists

Filter with

Specific device Plate allow list Plate deny list IO board input

Action modules

What happens next

  • Easyset

    Open entrance with device outputs

  • FireBird

    Open/close relays, reports, commands

  • Tuya

    Switch on/off, set brightness

  • CCTV Camera

    Pop the live view up for operators

  • Notifications

    Email, SMS, voice, push, Telegram, Slack

  • Webhook

    Call any URL with body and headers

Enterprise‑grade controls

Safety and governance for large portfolios

  • Role‑based access for organizations and operators
  • Share scenes with specific operators
  • Detailed run log for every scene
  • Safe “Test Scene” runner
  • Enable or disable with one toggle
  • Message variables for plate, user and device

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.

See a scene run

Real‑world automation playbooks

A device event comes in, the matching scene is queued, each action step runs in order and the whole run is written to the scene log. Pick a playbook to watch it happen.

Automation scene

Visitor parking

Active
Automation scene run A device trigger reaches the automation engine, which matches the active scene and queues a job. Each action step then runs in order and the run is written to the scene log. TRIGGER SCENE ENGINE ACTIONS Automation If / then scene Active scene matched Job queued Scene log Waiting 1 2 3

Run history

Live scene log

Idle

    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.

    AI Assistant

    Ask your question to chat

    Hello! 👋 I'm your AI assistant for TheBuildingCloud. I can help you learn about our platform features, pricing, and capabilities. Sign in to ask about your own account.