1. Open the flow or actions page
From your project, look for the menu or button named Actions, Flows, or Automation.

In some versions, the flow page may be accessible from the project dashboard or the sidebar.
2. Click New Flow or Add Flow
Find a button with a + icon, or labels such as Create New Flow or New Flow.

If your interface first shows existing flows, the button is usually in the top right corner.
3. Give the flow a clear name
Enter a title that explains what the flow does, such as Create Meeting Report or Automatic Invoice Extraction.
Add a short description if a description field is available.
4. Add the first action
Choose an action type from the available list, for example:
- Create a document
- Extract data
- Send an email
- Create a widget or report
For each action, click Add or Select and then fill in the required settings.
5. Configure the action settings
For each action in the flow, specify:
- The input data (tags, sources, files, project, etc.)
- The expected output (document type, destination, email, etc.)
- Any run conditions if those options are available
Review each action before moving to the next one.
6. Add additional actions if needed
A flow can contain multiple actions executed in order.
After adding the first action, use the Add an action button to chain the next steps.

7. Check the order and dependencies
Make sure the action order matches the process you want to automate.
For example, extraction should happen before generating a report and sending an email.
8. Save the flow
When the flow is complete, click Save, Publish, or the equivalent button.
If a validation warning appears, fix any missing fields and save again.
9. Test the flow
Run the flow with an example or test input if that option is available.
Check the result and adjust actions if needed.
10. Activate or schedule the flow
If your interface offers an activation option, turn on the flow so it runs automatically.
You may also be able to schedule regular runs (daily, weekly, etc.).
Tip: Start with a simple flow and add steps one at a time. This makes testing and fixing easier.