Approval Workflows
An approval workflow pauses an automated workflow at a chosen step and waits for a person to review and authorise it before the workflow continues. You build one by dropping an Approval node into the workflow at the point where you want a human in the loop — for example, before a refund is issued, before a discharge letter is sent, or before a high-value claim is submitted.
This page covers the Approval node in the workflow builder. For how approval tiers work across every action in Praxi (the system that decides which actions need sign-off and who can give it), see the Approval Workflows guide.
What the Approval node does
When a running workflow reaches an Approval node, it:
- Pauses at that step — no later steps run yet.
- Creates an approval request and notifies the assigned approver.
- Resumes down the approved path when the approver approves, or down the rejected path when they reject.
Because the workflow suspends rather than failing, an approval can sit pending for as long as you allow without losing the workflow's progress.
Adding an approval gate
In the workflow builder, add an Approval node where you want the gate, then configure it:
| Setting | What it does |
|---|---|
| Title | A short label for the approval request. |
| Message | The detail the approver sees when deciding — give them enough context to approve or reject. |
| Assign to | A specific user, or a role (any holder of that role can action it). |
| Timeout | Optional. How many hours to wait before the gate acts on its own. |
| On timeout | What happens if no one responds in time: approve, reject, or escalate. |
Connect the node's approved and rejected outputs to the steps that should run in each case. A common pattern is to send the action down the approved path and send a notification (or simply stop) on the rejected path.
How an approver responds
The assigned user or role receives the approval request and can approve or reject it from their notifications or the command palette. The Approval Workflows guide covers where pending approvals appear and how to action them, including handling several at once.
Requiring approval before an AI-triggered workflow runs
If a workflow can be started by one of Praxi's AI agents, you can require human approval before the workflow runs at all, and restrict which roles are allowed to give that approval. This keeps a person in control of anything an agent might set in motion. You can also mark individual action steps within a workflow so that every action execution waits for approval.
Permissions
| Action | Who can do this |
|---|---|
| Add or edit an approval gate | Practice owner, practice manager |
| Approve or reject a request | The assigned user or role |
Related
- Workflows Overview
- Workflow Triggers
- Workflow Conditions
- Creating Workflows
- Approval Workflows guide — approval tiers and managing pending approvals.