Automation
Planned
What it is
An automation is drawn as triggers, conditions and actions, then published as a version. Each run keeps a history, with sensitive values hidden.
| Building block | Role in the flow |
|---|---|
| Trigger | The event that starts the flow. |
| Condition | A check that decides whether the flow goes on. |
| Action | What the flow does. |
A step that changes something important can wait for a person, and that person sees a preview before deciding. Agents that draft tasks or notifications stay inside an allowlist, and a manager approves an assignment before it is carried out. The institution can also author its own flows.
Describing a flow
On the automations page, and inside a flow, you can describe in your own words what the flow should do. You see a suggestion and what it would change. Saving keeps a draft. The flow does not start, and nothing is published, until you do that yourself later.
A support session can see the box and cannot ask for a suggestion.
FAQ
No. This area is planned and not yet part of the current release.
No. Saving keeps a draft. The flow does not start, and nothing is published, until you do that yourself.
A step that changes something important can wait for a person, who sees a preview before deciding. Assignments drafted by agents are approved by a manager before they are carried out.
No. Each run keeps a history, with sensitive values hidden.