Say you want a performance report emailed to your team every Monday morning, instead of pulling the numbers yourself each week. This page walks through building that as a flow, running it, and checking the result. See the Xpert Flows overview first if you have not already, for what a trigger, block, and approval gate are.
Start the flow
Click Xpert Flows in the sidebar.
Check the Team Flows tab and the Inspiration library first - someone may have already built something close to what you need.
If not, go to My Flows and click Create Flow to open the builder on an empty canvas.
Example: Build a report flow
Click the flow name at the top and rename it, for example "Weekly Campaign Report".
Add a trigger block and choose Scheduled and select when you would like the report to run. (You can use the Test run button at the bottom of the flow to check your progress as you build).
Add an AI Xpert block below it. In this example, use the Data Analyst, and enter a query that pulls your report data. The Data Analyst block also requires you to select the source of the data, but with all AI Xpert blocks, it is important to enter your instructions so the agent understands what it is expected to do. If this includes working with the output from previous steps, include clear details about what you expect and how to use it.
Add a Content Specialist to take the data and build the report as HTML, which can then be used in an email.
Add a Send Email block below that, and set the recipient, subject, and body. Reference the HTML content from the Content Specialist block in the body so the report content updates automatically each run.
Click Save.
Run it
Click Turn on. The flow will run at the scheduled day and time. A flow can also run from a webhook or another event instead of a schedule, if that fits the task better.
Add a check before it goes out
If the report includes AI-written commentary, or anything else you want to review before it reaches its recipients, add an Approval Gate between the query and the email block. When the flow reaches it, execution pauses and a notification appears in your Inbox. Open it to review what the flow has produced so far, then approve to let the email send, or reject to stop it.
Check the result
After a run, click any block to see the data it received and produced, or the error message if it failed. If the flow saves a file rather than emailing it, find it afterwards in Artefacts.
If a run does not behave as expected, check the following first:
Issue | Check |
|---|---|
The flow will not run | Confirm it has a trigger block - every flow needs one. |
A block did not receive the expected data | Confirm the blocks are connected in the right order. |
A block shows an error | Click it and check its configuration is complete. |
Your changes did not apply | Save the flow before the next run. |
What’s next
See Using Team Flows to publish this flow for your team once it is working reliably, or to run a flow a teammate has already published.