Getting started

Launch your first workflow

Take one repetitive business motion from connected systems to a working Operator workflow using Trigger, Reason, Act and Approve.

6 min read

A workflow is one repeatable business motion written down as a loop: something happens, Operator works out what it means, prepares the next action and stops where a person has to decide. Four stages, in the same order every time.

1. The four stages

Every Operator workflow follows the same motion: a signal starts the process, Operator interprets the context, work moves forward, and anything consequential pauses at a checkpoint.

  1. 01 / Trigger

    Signal arrives

    An email, meeting, CRM change, form, file or schedule starts the workflow.

  2. 02 / Reason

    Context is understood

    Operator establishes what the signal is about, how urgent it is and who owns it.

  3. 03 / Act

    Work is prepared

    Drafts, record updates and tasks are prepared before anything leaves the company.

  4. 04 / Approve / Human checkpoint

    Human checkpoint

    Consequential actions wait for a person to approve, edit or skip.

This guide walks through each stage using lead response as the example, because it shows all four clearly.

FLOW STUDIO

The same four stages as real nodes in the Flow Studio editor: an integration event triggers the workflow, the agent reasons over the context, a Review and approve step holds anything consequential for a person, then the approved action runs and a summary is sent.

WHERE WORKFLOWS LIVE

Workflows are owned per profile. Open an agent's settings and switch to the Workflows tab to see what is published, when it last ran, and to start a new one with Create Workflow.

2. Trigger: what starts the workflow

A trigger is the signal Operator watches for. It can be an incoming message, a meeting that ended, a record that changed, a form submission, a new file or simply a scheduled check.

In lead response, the trigger is a new enquiry arriving through a form, an inbox or the CRM.

3. Reason: what Operator works out

Before preparing anything, Operator reads the situation using the context in your connected systems. It establishes what the signal is about, how urgent it is, whether there is any history and who is likely to own it.

This is the stage that separates a useful action from a generic one. A lead that already spoke to sales last month should not receive a first-contact email.

4. Act: what Operator prepares

Operator then does the preparation work: a drafted reply in your tone, an update to the record, a task or reminder with an owner attached. Nothing here has left the company yet, which is why preparation can usually run without a checkpoint.

5. Approve: where you decide

Anything consequential pauses for a person. The proposed action arrives with the evidence behind it: the original signal, the context Operator used and what it intends to do next. You approve, edit or skip.

Which action types stop here is something you configure. How approvals work

6. The example from beginning to end

  1. 01

    Lead submits form

  2. 02

    Operator gathers relevant context

  3. 03

    Lead is classified

  4. 04

    Response is drafted

  5. 05

    Human reviews the response

    Human checkpoint
  6. 06

    Approved response is sent

    Human checkpoint
  7. 07

    CRM is updated

  8. 08

    Follow-up is scheduled

Run the loop end to end once before you widen it. A small workflow you trust beats a large one you keep checking.

PUBLISHED

Once published, the workflow appears in the Workflows menu on the dashboard. The badge counts live workflows across all profiles, and each entry shows the trigger and the profile that owns it.

Continue learning