Xpert Flows lets you turn a task you do repeatedly into an automation. Once you build a flow, it runs on the schedule, event, or command you choose, instead of you doing the steps yourself each time.
This section covers why you might use a flow, how a flow is put together, and the building blocks you choose from when you create one.
Why use a flow
If you already do a task the same way every time, a flow lets you build it once and stop repeating it. For example, you can use a flow to:
Send a performance report to your team on a schedule, instead of pulling the numbers yourself each time.
Post a Slack alert when a metric crosses a threshold you set.
Pull data from one system, filter or merge it, and pass it to another.
Generate personalised content at scale, or analyse sentiment across a batch of customer feedback.
If the task is bigger or less repeatable, and you would rather hand over an objective than define every step, a Crew may suit it better. See Understanding Xpert Crews for that comparison.
How a flow is put together
Every flow follows the same pattern:
Trigger - starts the flow: a schedule, an event, or a manual run.
Process - one or more blocks act on the data, for example querying, transforming, or analysing it.
Output - delivers the result, for example by email, in Slack, or as a saved artefact.
Blocks connect in sequence, and the output of one block becomes the input to the next, so you can build a multi-step process without writing any code.
Context builds up on longer flows
As a flow runs, the context passed between blocks keeps growing. On longer flows, be aware that XpertOS condenses earlier context to keep things manageable, so something detailed built a few steps back (an email, for example) can come through summarised rather than in full, and a later step may end up rebuilding something similar rather than reusing the original.
The building blocks you choose from
Category | What it does | Examples |
|---|---|---|
Triggers | Starts the flow | Manual, Scheduled, Webhook |
Integrations | Connects to an external service | Intelligence Query, Google Drive, Jira |
Actions | Acts on the data | Build Email, Slack Message |
Xperts | Adds intelligence to the flow | AI Action (content generation, analysis, personalisation) |
Logic | Controls how the flow runs | Conditional Split, Data Filter, Loop, Wait |
Approval Gates | Pauses the flow for a human check | Waits for a user to approve or reject before continuing |
Adding a human check with approval gates
An Approval Gate pauses a flow at a point you choose and notifies a designated approver. The flow continues only after the approver approves or rejects it. Use one wherever a flow should not proceed without a human check first, for example to:
Review AI-generated content before it reaches customers.
Validate a data transformation before it writes to another system.
Sign off on campaign parameters before activation.
What's next
See Creating and running a flow to build one, and Using Team Flows to run or share a flow with your organisation.