Available Actions

Last updated: 16 April 2026

Available Actions

This article lists all the action and control nodes you can add to a workflow.

Action Nodes

Create Task

Creates a new task in the task list.

  • Title -- the task name (supports merge fields)
  • Description -- optional detail (supports merge fields)
  • Assigned to -- a specific user or team
  • Due date -- when the task should be completed
  • Urgency -- routine or urgent
  • Linked to -- automatically linked to the triggering patient, appointment, or other record

Send Email

Sends an email to the patient or a specified recipient.

  • To -- patient email (from trigger context) or a custom address
  • Subject -- email subject line (supports merge fields)
  • Body -- email content (supports merge fields)
  • Provider -- uses your connected email provider

Send SMS

Sends an SMS message via Firetext.

  • To -- patient mobile number (from trigger context)
  • Message -- SMS content (supports merge fields)
  • Quiet hours -- respects your organisation's quiet hours configuration

Update Record

Updates a field on a database record.

  • Record type -- the type of record to update
  • Field -- which field to change
  • Value -- the new value (supports merge fields)

Update Recall

Updates a recall enrolment's status.

  • Status -- set to active, deferred, fulfilled, or cancelled
  • Reason -- optional note for the change

Add Alert

Creates a clinical alert on a patient record.

  • Title -- alert title (supports merge fields)
  • Priority -- the alert severity level
  • Patient -- automatically linked to the triggering patient

Close Task

Marks a task as done or cancelled.

  • Status -- completed or cancelled
  • Task -- the task from the trigger context

Control Nodes

Wait

Pauses the workflow for a specified duration before continuing to the next step.

  • Duration -- configurable delay (e.g. 1 hour, 24 hours, 7 days)

The workflow is suspended during the wait and resumes automatically when the duration elapses.

Branch

Splits the workflow into two paths based on a condition.

  • Condition -- an if/else expression using trigger variables
  • Yes path -- executes if the condition is true
  • No path -- executes if the condition is false

For example, branch on whether the patient has an email address to decide between sending an email or an SMS.

Filter

Stops the workflow if a condition is not met.

  • Condition -- if the condition evaluates to false, the workflow ends
  • Unlike Branch, Filter does not offer an alternative path -- it simply stops execution

Useful for adding guard conditions, such as "only continue if the patient is on the diabetes register".

Tip: All text fields in action nodes support merge fields. Click the { } button in any text field to browse available variables and insert them.