Workflows Overview

Workflows Overview

Workflows allow you to automate clinical and administrative tasks in Jump. A workflow is a sequence of steps -- a trigger that starts it, followed by one or more actions that are executed automatically.

Workflows are built using a visual flow builder where you connect trigger, action, and control nodes on a canvas.

What You Can Automate

Common examples include:

• Sending a follow-up email to a patient after an appointment is completed
• Creating a task for a team member when a questionnaire is submitted
• Sending an SMS reminder when a recall is due
• Adding a clinical alert when a lab result arrives
• Updating a recall enrolment when an appointment is booked

Trigger Types

Every workflow starts with a trigger -- the event that kicks it off:

Trigger Type	How It Works
Manual	Started by a team member from a patient, appointment, task, or recall
Event	Fires automatically when a clinical event occurs (e.g. appointment booked, lab result received)
Schedule	Runs on a recurring schedule
Webhook	Triggered by an external system via HTTP

Workflow States

A workflow can be in one of two states:

• Draft -- the workflow is being built or edited and will not run
• Enabled -- the workflow is live and will execute when its trigger fires

The Workflows Page

The Workflows page lists all workflows in your organisation with tabs for:

• All -- every workflow
• Enabled -- workflows that are currently active
• Draft -- workflows that are still being built

Each workflow card shows its name, description, trigger type, and whether it is enabled.

Tip: Start with a simple workflow -- such as sending a confirmation email after an appointment is booked -- to get familiar with the builder before creating more complex automations.

System Workflows

Jump ships a small library of system workflow templates that appear in every organisation's Workflows page under a System workflows section, separate from your own flows. System workflows are maintained centrally and can't be edited in place — click Clone to customise to copy one into your organisation as an editable draft.

Today there's one template: Create task when an invoice is paid. Cloning it gives you a workflow that triggers on the Invoice Paid event and creates a follow-up task linked to the paid invoice. After cloning you can:

• Change the task title, description, due date, priority and assignee (user or team).
• On the Invoice Paid trigger, filter by product category — useful if you only want follow-up tasks for certain services (e.g. consultations, supplements, medications). Leave the filter empty to fire for every paid invoice.

Remember to Publish and Enable the cloned workflow before it will run.