Guides
Build & trigger a workflow
A recurring routine becomes an automation that runs reliably and traceably.
An enabled workflow that starts manually or on a data change. Each of its runs is traceable.
Who is involved
Section titled “Who is involved”AI & automation owner (concept), Admin (creation, enabling). Only owners and admins may create and change workflows.
Prerequisites
Section titled “Prerequisites”- Admin permissions.
- A clear routine: what triggers it, which steps follow, what is the result?
- If an agent is to take part: an active Agent or Polaris.
The workflow
Section titled “The workflow”- Describe the routine – in Polaris: trigger, steps, result.
- Have the workflow written – Polaris creates the rules document. The trigger is either manual or a data change in a table (create, update or both; see Triggers).
- Wait for validation – Polaris saves; the validation reports errors with their location. Polaris fixes them until the save succeeds. The new workflow is disabled.
- Test – Polaris can run a manual workflow once in the chat.
- Enable – the owner or an admin enables the workflow. Polaris cannot do this.
- Trigger – a manual workflow starts on request, a CDC workflow by itself as soon as data in the table changes.
- Monitor – under Executions you check status, rules and child runs. Failed runs are listed first.
- Adjust or pause – Polaris saves changes to an enabled workflow as a proposal; it only applies after the owner or an admin accepts it and must then be enabled again. Disabling stops the trigger; the workflow is kept.
Result
Section titled “Result”The routine runs automatically and versioned. Every run is traceable in the Executions.