Workflows - Custral Docs

A Workflow is an event-driven automation: a trigger fires, a chain of actions runs, and edges decide which path each run takes. Workflows run as soon as the originating event is emitted.

Anatomy

Every workflow has:

A single Trigger. See Triggers.
One or more Actions wired up by Edges. See Actions and Edges & logic.
A status (enabled / disabled).

When to use a Workflow vs a Sequence

Use case	Pick
Fires immediately on a record, field, or conversation change	Workflow
Spans days or weeks with explicit waits	Sequence
Runs on a cron schedule over a filtered set of records or conversations	Job
Background bulk operation	Job

Scheduled, recurring runs are modelled as Jobs. An automation that runs on a schedule and selects which records or conversations to process each time. See Jobs.

Authoring

Open Automations → New workflow. Pick a trigger from the catalog, add actions onto the canvas, wire them with edges, and enable.

Run history

Each workflow run is recorded with the data that triggered it, what each action received and produced, and any error message. Open the workflow → Runs to inspect.

See also