Trigger and action engine

Automations

Open templates
Accessno session
TenantNot selected
Enabled rules0
Queued events0
Failed runs0
ORBIT_AUTOMATION_WORKER_SETUP_REQUIRED

Automation rules can be managed, but event execution is fail-closed until a dedicated Orbit automation worker/provider is configured.

Allowed triggers: item.created, item.updated, status.changed, due_date.approaching, form.submitted. Allowed actions: notify, create_update, set_item_state.

Rule builder

Create tenant-scoped rule

Rules

Lifecycle controls

No automation rules configured yet.

Create a tenant-scoped rule from a board; execution remains setup-required until a worker is configured.

Workflow library

Create recipe

Library

Workflow recipes

No workflow recipes configured yet.

Create reusable automation recipes after tenant admin review.

Execution

Queue and run history

Event queue

No queued automation events are visible for this tenant.

Runs

No automation runs have been recorded for this tenant yet.

Run steps

No run steps have been recorded for this tenant yet.

Audit events

No automation audit events have been recorded for this tenant yet.

Triggers

Board, item, due date, and intake events are modeled as tenant-scoped queue entries.

Actions

Rules store ordered notification, update, and item-state actions only from the supported catalog.

Runs

Runs and steps expose execution state without customer-ready claims.

Worker gate

Background execution is setup-required until Orbit worker/provider readiness is configured.