What can an email or chat workflow do?
A workflow can select a branch, wait and perform approved optional actions. It cannot impersonate a client or change issued money.
Watch the walkthrough
Who acts: Authorized workflow editor; Owner or Admin activates
Go straight to the steps
Playback and accessibility
Use Play or Pause, move back or forward 10 seconds, or restart from the title screen. Tab to a button, then press Enter or Space. Action captions are included in the video, and the complete written steps follow below.
Download the action captionsGo straight to the written stepsFollow the steps.
Open a disabled recipe and edit its steps
Open Workflows and select a recipe such as Revision request acknowledgement. Use the graph or Keyboard and mobile step editor. Keep one trigger and terminating branches, and choose authorized recipients and approved message content.
Open workflowsInspect the graph-backed ordered editor
The recording collapses and reopens Keyboard and mobile step editor. This is the actual ordered form for the graph’s nodes, branches and messages, not a screenshot. Review terminating branches and authorized content before saving.
Prepare a sample for dry-run review
The recording types a Sample message while the recipe remains Disabled; it does not invoke a provider or fabricate a trace. In your configured workspace, save the draft and choose Preview trace to inspect matching and nonmatching branches. A dry run has no writes or sends and cannot approve a client’s revision.
Add an optional draft step before publishing
The recording adds a condition: both the graph and ordered form update and the draft becomes unsaved. Review, save and resolve graph/provider requirements before Publish reviewed version. Publishing alone stays disabled; an Owner or Admin explicitly activates. Inspect version-pinned Run history and pause optional actions when needed. Pausing cannot recall sent messages or disable mandatory safety effects.
What changes when you finish
A reviewed immutable version runs only after explicit activation. It can acknowledge a request, never impersonate client consent or mark payment or delivery complete.
Preview before activation
Build a graph with one trigger and reachable terminating branches. Use the ordered form editor if dragging nodes is unsuitable. Preview resolves a trace without writing messages or sending email. Publishing freezes a version, and an owner or administrator must explicitly activate it.
Use bounded actions
Nodes can send an approved email or labeled chat response, assign a conversation, tag a contact, notify an internal participant or call a verified webhook. Delay, condition and end nodes control the path. There is no arbitrary JavaScript, SQL or LLM generation.
Keep safety outside the graph
A revision acknowledgement confirms receipt only; it never creates a priced change or accepts delivery. Runs stay pinned to their published version and recheck permissions before delayed actions. Pausing cancels pending optional work, not a message already sent. Required scope effects, receipts and suppression are not disabled by an optional-action quota.