Skip to main content

Workflows Overview

Automate repetitive tasks, streamline patient journeys, and ensure consistent processes with Praxi's visual workflow builder.

What Are Workflows?​

Workflows are automated sequences of actions that run when specific events occur. They help you:

BenefitExample
Save timeAuto-send appointment reminders
Reduce errorsStandardise intake processes
Improve consistencyEnsure every client gets follow-up
Scale operationsHandle growth without more staff

Workflow Components​

Node Types​

NodePurposeExample
TriggerStarts the workflowAppointment booked
ActionPerforms an operationSend email
AgentAI-powered decision/taskDraft follow-up note
ApprovalRequires human approvalManager sign-off
ConditionBranch based on criteriaIf client is new
RouterMulti-path branchingRoute by funding source
DelayWait before continuingWait 24 hours
LoopRepeat for a collection of itemsFor each appointment
Fork / JoinRun branches in parallelSend SMS and email simultaneously
Entity SelectorSelect entities to processChoose clients matching criteria
NotificationSend targeted notificationAlert supervisor
FormSend a form and wait for responseRequest intake details
Document GenerateCreate a document from a templateGenerate GP referral letter
EndTerminates workflowComplete

Visual Builder​

Workflow builder with node canvas, triggers, and action configuration

The drag-and-drop builder lets you:

  • Add nodes from the palette
  • Connect nodes with arrows
  • Configure each node's settings
  • Preview workflow logic
  • Test before activating

Common Workflow Examples​

Appointment Reminders​

Trigger: Appointment created
↓
Delay: Wait until 24 hours before
↓
Action: Send SMS reminder
↓
Condition: Client confirmed?
↓ Yes ↓ No
End Action: Send follow-up SMS

New Client Intake​

Trigger: Client created
↓
Action: Send welcome email
↓
Action: Assign intake forms
↓
Delay: Wait 48 hours
↓
Condition: Forms completed?
↓ Yes ↓ No
End Action: Send reminder

Invoice Follow-Up​

Trigger: Invoice overdue
↓
Action: Send payment reminder
↓
Delay: Wait 7 days
↓
Condition: Still unpaid?
↓ Yes ↓ No
Action: Escalate End

Unsigned Notes Alert​

Trigger: Schedule (daily at 9am)
↓
Loop: For each unsigned note > 24h
↓
Action: Send reminder to practitioner
↓
End loop

Workflow Categories​

Workflows are organised into categories to keep your list manageable:

CategoryExamples
Client ManagementWelcome sequences, consent expiry, inactive re-engagement
AppointmentsReminders, no-show follow-up, telehealth checks, recurring books
BillingAuto-invoicing, payment reminders, Medicare bulk billing
ClinicalNote signing, risk escalation, MHCP tracking, assessment follow-up
CommunicationsBirthday messages, recall campaigns, feedback requests
MHCP ComplianceSession tracking, plan expiry, limit warnings
TasksTask creation, assignment, completion workflows
AdministrativeCredential checks, document retention, daily summaries

Getting Started​

Creating Your First Workflow​

  1. Go to Workflows in the Practice section of the sidebar
  2. Click Create Workflow
  3. Choose a template or start blank
  4. Add your trigger
  5. Add actions and conditions
  6. Test the workflow
  7. Activate when ready

Using Templates​

Praxi includes a large library of pre-built templates across clinical, billing, communication, and administrative categories. Some commonly used templates include:

TemplateDescription
Appointment Reminder SequenceSMS and email before sessions
New Client Welcome SequenceEmail, intake forms, and scheduling prompt
Invoice Overdue EscalationMulti-step payment reminder sequence
Unsigned Notes ReminderDaily AHPRA compliance check
Client Birthday GreetingAnnual client message
MHCP Session TrackingMonitor Mental Health Care Plan sessions
Post-Session Note ReminderPrompt practitioners to complete notes
No-Show Follow-upAutomatic follow-up after missed sessions

To use a template:

  1. Go to Workflows → Templates
  2. Browse available templates by category
  3. Click Use Template
  4. Customise as needed
  5. Activate

AI Co-builder (Pro and Enterprise)​

Prefer to describe your automation in plain English? The AI Co-builder lets you type what you want the workflow to do and receive a complete proposal — trigger, steps, and connections — ready to review and apply to the canvas. The AI never saves or activates anything; you stay in control throughout.

Workflow Limits​

By Plan​

What you can do with workflows depends on your subscription tier:

CapabilityEssentialsProEnterprise
View & enable workflowsYesYesYes
Adjust workflow variablesYesYesYes
Clone & edit workflowsNoYesYes
Create custom workflowsNoYesYes
Delete workflowsNoNoYes

Execution Limits​

LimitValueReason
Max nodes100 per workflowPerformance
Max depth50 levelsComplexity
Delay maximumWeeks (no hard cap)Practical limit
Loop iterations1,000 per loopPrevent runaway
Workflow timeout5 minutesResource management

Monitoring Workflows​

Execution History​

View past executions:

  1. Go to Workflows, open the workflow, then select History
  2. See all executions with status
  3. Click to view execution details
  4. Review each node's result

Execution Status​

StatusMeaning
PendingQueued and waiting to start
RunningCurrently executing
PausedWaiting at a delay, approval, or form node
CompletedFinished successfully
FailedError occurred
CancelledManually stopped

Error Handling​

Praxi includes automatic retry and circuit breaker protection. When a node fails, the system retries up to 3 times with increasing delays (exponential backoff). If a service continues to fail, the circuit breaker stops sending requests to allow it to recover.

When workflows fail:

  1. Check execution history for error details
  2. Review the failed node's configuration
  3. Check input data validity
  4. Verify external service availability
  5. Fix and retry if needed

AI Agent Triggers​

Workflows can be triggered by AI agents, but this is disabled by default for safety. When enabled, AI-triggered workflows always require human approval before executing (per PsyBA 2025 Code of Conduct).

To allow AI triggers on a workflow:

  1. Open the workflow in the builder
  2. Go to Settings
  3. Enable Allow AI trigger
  4. Optionally configure which roles can approve AI-triggered executions
AI Clinical Actions

AI-suggested clinical actions (such as notes, assessments, or treatment plan changes) always require human approval regardless of the workflow configuration. This cannot be overridden.

Dry Run and Testing​

Before activating a workflow, you can run a dry run to simulate execution without making any actual changes:

  1. Open the workflow in the builder
  2. Click Test in the toolbar
  3. Enter sample trigger data
  4. Click Run Test
  5. Review the simulated execution step by step -- no emails are sent, no records are created

The dry run shows estimated timing for each node and highlights any potential errors in your configuration.

Best Practices​

  1. Start simple - Begin with 3-5 node workflows
  2. Test thoroughly - Use dry run mode before activating
  3. Monitor executions - Review history regularly
  4. Use descriptive names - "New Client Intake" not "Workflow 1"
  5. Document purpose - Add notes explaining the workflow
  6. Set error notifications - Get alerts on failures
  7. Review monthly - Optimise based on results

Permissions​

ActionWho Can Do This
View workflowsPractice owner, practice manager
Create/edit workflowsPractice owner
Activate workflowsPractice owner
View execution historyPractice owner, practice manager
Delete workflowsPractice owner
View workflow analyticsPractice owner, practice manager

Troubleshooting​

Workflow Not Triggering​

  1. Verify workflow is active (not paused)
  2. Check trigger conditions match event
  3. Verify user has required permissions
  4. Review execution history for errors
  5. Check workflow limits not exceeded

Actions Not Executing​

  1. Check condition logic is correct
  2. Verify action configuration complete
  3. Check external service credentials
  4. Review error messages in history

Performance Issues​

  1. Reduce workflow complexity
  2. Avoid unnecessary delays
  3. Limit loop iterations
  4. Consider splitting into multiple workflows

Was this page helpful?