Guides
Workflows
A workflow is a repeatable automation made of rules: a trigger starts it, rules execute the steps. Polaris writes it for you.
What it is for
Section titled “What it is for”Workflows take over routine work that always runs the same way. Examples: a task is created on a data change. An agent summarizes new issues. A record is completed according to fixed rules.
Where in the app
Section titled “Where in the app”Workflows have no page of their own and no graphical editor. You describe to Polaris what should happen automatically. Polaris writes the workflow as a rules document, validates it and saves it. You see runs under Executions.
Key terms
Section titled “Key terms”- Rules document – the workflow itself: trigger (
on), optionally a condition (when), the rules and optionally a result (return). - Rule – one step: a CEL expression or a call, such as reading or changing Aligia data, starting an agent or another workflow.
- Trigger – what starts it: manually or on a data change (see Triggers).
- Version – every save creates a new version. Runs remember the version they ran with.
- Proposal – a saved version that only applies once the owner or an admin accepts it.
How it works
Section titled “How it works”Polaris reads existing workflows, knows the available calls and data types and always saves the whole document. The validation reports errors with their location; Polaris fixes them and saves again. Polaris can also run a manual workflow once in the chat without saving it permanently.
A new workflow is disabled at first. If Polaris changes a workflow that is already enabled, a proposal is created. Polaris cannot enable workflows or accept proposals; that is left to the owner or an admin.
Permissions: only owners and admins may create and change workflows.
Interplay
Section titled “Interplay”- Every run appears under Executions.
- A rule can start an Agent or another workflow.
- Polaris shows started workflows in its sidebar under „Agenten“.