Dokumentace

Automations

Build, publish, activate, and monitor Workspace rules across supported collections.

automationsworkflowsrulestriggerstasks

Automations

Automations run Workspace-wide rules against the collections registered in the automation catalog. Open Automations to build and manage them.

Build a rule

Each rule contains one trigger, one action, and its run behavior. It can also include a condition and, for supported triggers, a wait:

  • Record changed reacts to a create or update operation and matches a selected field against the configured value.
  • Date reached runs before or after a selected date or date-time field by a whole number of minutes, hours, days, or weeks.
  • Domain event received uses an event exposed by the current automation catalog.
  • The optional condition compares one source field with a value. Record-change and domain-event triggers can also wait before their action.
  • The current rule builder can create a task from a title template or delete the matching record when the selected collection supports deletion. Task titles can insert source fields with placeholders such as {{title}}.

For record-based triggers, Future changes only starts with new matches. Include records that already match also starts a bounded activation scan when the automation is turned on. For repeated matches on the same record, choose whether a newer run replaces the older waiting run or runs proceed in parallel. Review this setting carefully before publishing a rule that deletes records.

Drafts, publishing, and activation

Save draft stores authoring changes without affecting the published version. Publish makes that draft the current version but leaves the automation off; Publish and activate publishes and turns it on in one step. Later draft edits remain unpublished until you publish again.

A published automation has a separate On / Off switch. Turning it off stops new runs and cancels queued, running, or waiting runs. Turning it on again starts from the published version and does not restore canceled runs.

Runs and safety

The Recent runs card shows run state, time, source record, and any error summary. Queued, running, or waiting runs can be canceled. Failed and canceled runs can be retried when the pinned version is still valid.

Every automation has an owner. Publishing and execution recheck that member's current Workspace-wide access to the source and action. For example, a delete action needs unrestricted delete access to the source collection, and task creation needs unrestricted Tasks create access. If required access is lost, the automation needs attention instead of continuing with stale authority.

Record triggers also pin evidence about the watched fields. Before a delayed action runs, Einblick checks that evidence again; if the relevant record change has been superseded, the old run performs no action.

The older graph-prototype authoring endpoints and runtime are retired. Legacy prototype automations are not editable or runnable in the current rule builder, and the former /automation-webhook endpoint has been removed.