No-code
Choose the event, configure the rule and select the action. Most automations never need more than this.
Trigger
Choose the event
Action
Select what happens
Automate · Triggers & Actions
Turn every event
into the next action.
Connect what happens across your patient journeys, teams and systems to what should happen next — automatically.
Trigger · Patient event
Appointment booked
Cardiology · 12 Oct, 10:30
Condition
New patient?
- Yes
- No
Action
Welcome message
SentAction
Reminder message
Not this runThe core idea
When something happens, MeloHealth knows what to do next.
Triggers detect an event. Conditions determine what should happen. Actions execute the next step.
Trigger
Appointment bookedCondition
New patient?Action
Send a messageTrigger
Ticket raisedCondition
Priority?Action
Assign a teamTrigger
Message receivedCondition
No response yet?Action
Create a taskFrom patient activity to system events, MeloHealth can turn the right signal into the right response.
Trigger sources
Start from whatever happens.
Not every automation begins with a patient message. MeloHealth can respond to events from your application, connected systems, APIs, webhooks, schedules and operational activity.
Trigger library
App events
Events your MeloHealth application raises as your teams work — a record created, a status moved, a ticket opened.
App event
Appointment created
MeloHealth
Trigger matched
Action
Start the workflow
- Appointment created
- Ticket raised
- Ticket status changed
- Patient registered
- Lead created
- Record updated
API
Let external applications send events into MeloHealth. Your hospital system calls the endpoint, the trigger fires, and the configured action runs.
External
Hospital system
API
Event received
Trigger
MeloHealth trigger
Action
Configured action
- HIS and EMR events
- Billing system events
- Lab and radiology results
- Any system that can call an endpoint
Webhooks
Receive events from another platform the moment they happen, without anyone having to check for them.
External
External system
Webhook
Event delivered
Action
Run the action
- Form platforms
- Payment gateways
- Ad and lead platforms
- Partner portals
Timers
Start an action at a specific time, after a delay, or around a scheduled event — the day before an appointment, three days after a discharge.
Scheduled
Appointment tomorrow
Timer
24 hours before
Action
Send the reminder
- At a fixed time
- After a set delay
- Before a scheduled event
- On a repeating schedule
Patient events
Anything the patient does across the channels you have connected — a booking, a message, a form, a request.
Patient event
Message received
MeloHealth
Trigger matched
Action
Create a ticket
- Appointment booked
- Appointment cancelled
- Message received
- Form submitted
- Request raised
- Patient responds
Record changes
A field moves on a record and the automation picks it up — a status, an owner, a stage, a completed task.
Record change
Ticket assigned
MeloHealth
Trigger matched
Action
Notify the team
- Patient status changed
- Ticket assigned
- Lead stage changed
- Record updated
- Task completed
Events can come from anywhere. MeloHealth decides what happens next.
One event, many actions
One event can set everything else in motion.
A patient books an appointment. The confirmation, the notification, the record and the reminder all follow from that one event.
Trigger · Patient event
Appointment booked
Cardiology · 12 Oct, 10:30
Action
Confirm the patient
Patient
Your appointment is confirmed.
Sent
Action
Notify the front desk
Front desk
New appointment — Cardiology
Delivered
Action
Update the record
Patient record
Appointment added to the timeline
Updated
Delay
Wait until one day before
Action
Send the reminder
ScheduledOne event. Multiple coordinated responses.
Conditions, delays and escalations
Not every event needs the same response.
Some events need a decision, some need to wait, and some need somebody told when the expected thing does not happen.
Conditions
Choose the right path based on configured information.
- New patient?
- High priority?
- Patient responded?
- Department assigned?
Delays
Wait before taking the next action.
- 24 hours after an appointment
- 2 hours before
- 3 days after discharge
Escalations
If the expected action does not happen, bring the right team into the process.
- Create a task
- Notify the team
- Raise the priority
Trigger
Appointment completed
Delay
Wait 24 hours
Action
Send the follow-up
Condition
Response received?
- Yes
- No
Outcome
Nothing more to do
Not this runEscalation
Create a task
Action
Notify the team
Execution
Every automation leaves a trail.
Automation should not become a black box. See which trigger fired, which conditions were evaluated and which actions were completed.
Trigger
Appointment created
Condition
New patient?
Action
Send the message
Complete
Automation run
Complete
-
Appointment created Trigger received
-
New patient? YesMatched on mobile number. No earlier record was found, so the new-patient path was taken.
-
Confirmation message SentWhatsApp · +91 ••••• 4821 Template
appointment_confirm_v3 -
Front desk notification Delivered
-
Patient record Updated
Simple, then flexible
Start with a simple trigger. Add more control when you need it.
Advanced
Extend the automation when the operation needs custom logic or external systems.
Trigger
The event
Condition
The rule to apply
Custom logic
Your own step
External
API or webhook
Common automations stay simple. Advanced use cases can connect to APIs, webhooks and custom logic.
In practice
From patient request to the right team.
MeloHealthRoom 412 · Cardiology
Live
Patient
I need a nurse in my room.
MeloHealth
Your request has been raised.
- Ticket
- #4821
- Team
- Nursing
- Status
- Assigned
Trigger
Message received
Action
Create a ticket
Action
Assign the nursing team
Action
Notify the staff on shift
What the staff see
New request- Room
- 412
- Request
- Nurse assistance
- Assigned
- Nursing team
One patient message can trigger the right operational response.
FAQ
Frequently asked questions
What are Triggers & Actions?
Triggers detect events and actions define what MeloHealth should do when those events occur.
What can start a trigger?
Triggers can be based on supported app events, patient activity, record changes, API events, webhooks and scheduled or timed events.
Can one trigger perform multiple actions?
Yes. A single event can initiate multiple configured actions.
Can I add conditions?
Yes. Conditions can determine which path or action should execute based on configured information.
Can actions happen later?
Yes. Supported delays and scheduled events can be used when an action should happen at a specific time or after a defined period.
Can I connect APIs and webhooks?
Yes. APIs and webhooks can be used to bring events into MeloHealth or send configured actions to external systems.
Can I track automation activity?
Yes. Supported automations can provide execution information so teams can see what happened during a run.
Do I need coding knowledge?
No. Common automations can be configured visually. Advanced use cases can be extended with APIs, webhooks and custom logic.