A new patient arrives.
Identify them, route them into the right journey and let the configured process carry on.
Trigger
Lead submitted
Smart query
Patient exists?
Action
Registration
Action
Appointment booked
Automate · Workflow Builder
Build the logic behind
every patient interaction.
Connect triggers, patient data, decisions, AI, actions and integrations on one visual canvas — and build workflows around the way your organisation actually works.
Patient event
Appointment created
Configure
Smart query
Patient exists?
- Next
- Fallback
Patient
Existing patient
Registration
New patient
The trigger
Every workflow starts with something happening.
A patient submits a request. A lead comes in. An appointment is created. A ticket is raised. Turn that event into the first step of a workflow.
Start workflows from supported events instead of waiting for someone to move the process along by hand.
Event → Workflow
Trigger
Facebook lead form submitted
Configure
Record
Patient / lead created
Workflow
Start workflow
RunningSmart query
Don’t ask the patient twice. Ask the data first.
Before asking a patient for something your system may already hold, query the available data and decide what should happen next.
An existing patient continues with the context you already have. A new one starts the configured new-patient journey. Neither is asked to repeat themselves.
Query → Decide
Smart query
Patient exists?
Match on mobile number
- Next
- Fallback
Continue
Use existing patient context
Start
New-patient journey
Conditions
Make every decision part of the workflow.
Healthcare processes rarely follow one straight path. Use conditions, branches and rules to route patients and operational work on the information you have.
The same event can lead to completely different actions depending on patient status, responses, tags, fields, appointment information or other configured logic.
One decision, two paths
Patient request
Wants an appointment
Condition
Is this a registered patient?
- Yes
- No
Action
Offer appointment slots
Action
Send registration first
AI as a step
Put AI where the workflow needs understanding.
AI does not have to run the whole process. Use it as one step inside a larger workflow, then connect the result to the next action.
“Do I need to bring anything for my appointment?”
Let AI handle configured conversational tasks, and send anything it cannot resolve to the people who can.
AI → Decision → Action
Message
Patient asks a question
AI agent
Understand the request
Approved content only
- Next
- Fallback
Action
Send the answer
Handover
Route to the care team
Actions
Turn decisions into actions.
Once the workflow knows what needs to happen, it can move the process forward on its own — book the slot, raise the ticket, take the payment, send the confirmation.
Where a payment integration is configured, success continues the workflow and failure follows the fallback path you set. Nothing stops at a dead end.
Decide → Do
Condition
Does this service need payment?
Payment · Razorpay
Collect payment
Where the integration is configured
- Success
- Failure
Continue
Confirm the booking
Fallback
Retry or hand to the desk
Advanced
When your process is different, make the logic your own.
Not every healthcare operation fits a predefined block. Use the blocks Wisemelon provides — or add custom logic where your process needs more control.
- Transform data before it reaches another system
- Apply a rule that is specific to your organisation
- Format information for an external API
- Validate or restructure workflow data
Where supported
Data
Patient data
Custom code
Your logic
- Next
- Fallback
Condition
Route on the result
Beyond Wisemelon
Let the workflow move information where it needs to go.
The next step in a workflow does not always happen inside Wisemelon. Connect supported systems, APIs, webhooks and services as part of the same flow.
Wisemelon
The workflow
- APICall out
- WebhookBoth ways
- External systemWhere supported
- PaymentWhere configured
- CRMWhere supported
- Custom codeAdvanced
A workflow can orchestrate actions beyond one system.
Exceptions
Every workflow needs a way forward.
Not every condition will be met. Not every question will be understood. Not every action will succeed.
Build fallback paths so exceptions do not become dead ends — and so the thing that could not be automated becomes work for a named team instead of silence.
Ticketing owns the request that comes out of a fallback; Staff & Access decides whose queue it lands in.
No dead ends
AI agent
Understand the request
- Next
- Fallback
Continue
Carry on with the flow
Action
Create a ticket
Action
Assign the department
Action
Notify the staff on shift
In practice
Build workflows around real healthcare moments.
A patient needs help.
Let the workflow understand the request, and turn what it cannot resolve into work for the right team.
Trigger
Patient message
AI agent
Classify the intent
Action
Create a ticket
Action
Assign the team
A patient chooses a service.
Connect the decision to the action so the next step happens without anyone chasing it.
Trigger
Service selected
Condition
Payment required?
Action
Collect payment
Outcome
Success or fallback
All together
From one event to an entire process.
Combine triggers, queries, conditions, AI and actions to build workflows around the processes your teams already follow.
Trigger
Facebook lead submitted
Smart query
Patient exists?
- Next
- Fallback
Continue
Existing patient
Action
Register patient
Action
Appointment
AI agent
Answer the question
Action
Send the reply
Payment
Collect payment
Outcome
Payment succeeded
Action
Confirmation sent
CompleteBefore and after
Build it. Test it. See what happened.
Validate a workflow before you deploy it, and inspect execution activity when you need to understand how a configured workflow behaved.
A run that ends on a fallback is not a failed run. It is a run whose exception had somewhere to go — and a log line that says so.
- Test flow
- View logs
Execution · run #4,1821 fallback
- Trigger0.02s
- Smart query0.31s
- Condition0.01s
- AI agent1.14s
- PaymentFailed · gateway timeout
- Fallback · ticket created0.08s
Automation handles the process. People handle what matters.
Give teams a structured workflow for the repetitive steps, and keep the escalation and handover paths open for the moments that need a person.
A good workflow is not one that never reaches a human. It is one that reaches the right human, with the context already attached.
The blocks
Use the blocks your workflow needs.
Build with configurable blocks and connect them into the process you need.
Triggers
- Patient events
- Lead triggers
- Webhooks
- Configured events
Data and queries
- Smart query
- Patient data
- Variables
Logic
- Conditions
- Branches
- Rules
- Filters
Communication
- Text
- Audio
- Video
- Interactive messages
AI
- AI agent
- Intent
- Smart query
Actions
- Create a ticket
- Assign
- Notify
- Update status
Connections
- APIs
- Webhooks
- Supported integrations
- Payment
Advanced
- Custom code
One canvas. Any logic.
FAQ
Frequently asked questions
What is Wisemelon Workflow Builder?
A healthcare workflow builder is a visual tool that lets a healthcare organisation connect events, data, decisions, AI and actions into automated operational or patient workflows. Wisemelon Workflow Builder does that by connecting triggers, data, logic, AI, actions, integrations and custom logic into configurable healthcare workflows.
Do I need to code to build a workflow?
The visual builder is designed around configurable blocks and connections. Advanced workflows can also use supported APIs, webhooks or custom code where available.
What can trigger a workflow?
Workflows can start from supported events such as patient interactions, lead triggers, system events, webhooks and other configured triggers.
Can I check patient information inside a workflow?
Yes. Supported query and data blocks can be used to retrieve or evaluate available patient information and determine the next step.
Can I create different paths in one workflow?
Yes. Conditions and branches can route the workflow into different paths based on configured rules or information.
Can AI be used inside a workflow?
Yes. AI can be configured as a step within a workflow for supported conversational, intent or decision-related tasks, with configured fallback or human handoff paths where required.
Can I add custom logic?
Supported workflows can use custom code and other advanced blocks when a process requires logic beyond standard nodes.
Can I test and inspect workflows?
Wisemelon provides workflow testing and execution-log capabilities for supported workflows so teams can validate and inspect configured workflow activity.