MergePoint workflows can run fully autonomously or include checkpoints where a human needs to review, approve, or provide input before proceeding. This is called Human-in-the-Loop (HITL).
There are three primary ways to keep a human in the loop:
Use this for actions with side effects, such as sending emails, updating records, or creating events.
Behavior:
The workflow pauses until a user explicitly approves the action. Tasks appear as drafts in the Workflow Runs panel and must be confirmed in the UI before execution continues.
When to use it:
Outbound communications (e.g. "Send email")
CRM or database updates
Scheduling or calendar events
How to configure:
Enable Ask for Confirmation in the action step
The action is paused and shown as a pending task
A user must manually approve before the workflow proceeds
Where it appears:
Pending tasks show up in the Workflow Runs view
Sidebar badge indicates workflows awaiting confirmation
Use this method to send an email update to a person when a specific condition is met.
When to use it:
Escalating a high-value opportunity
Sharing negotiation outcomes
Intervening before automatic handoff or action
How to configure:
Add a Condition after the relevant action
Write a logic rule (e.g. lead_status = accepted)
Add a Send Email step
Set the recipient manually (e.g. [email protected])
Define the message body with key data points (e.g. lead name, deal amount)
Example:
“Send an email to the partnerships team when a deal closes with the lead name, email, and proposal link.”
Use this option to notify a team via messaging apps when something important happens.
When to use it:
Alerting a team to refund requests
Broadcasting new deal wins
Routing critical errors or flags to support channels
How to configure (Slack example):
Add a Condition step (e.g. refund_requested = true)
Add a Send Channel Message step
Set the target channel (e.g. #support-alerts)
Define the message with relevant data (e.g. customer email, timestamp)
Other supported channels:
Slack
Twilio SMS
Telegram
Microsoft Teams (via webhook)
MergePoint supports additional Human-in-the-Loop step types inspired by task-based approval workflows.
Step Type | Use Case |
|---|---|
Approval | Pause workflow and require a user to approve before continuing |
Data Input | Prompt the user to provide typed inputs (e.g. date, dropdowns, notes) |
Task Completion | Wait for confirmation that a real-world task has been completed |
These steps can be used inline with any workflow and are especially useful when automation needs to be combined with manual decision points.
Method | Use Case Example |
|---|---|
Ask for Confirmation | Hold workflow until user approves a high-impact action |
Receive an Email | Notify stakeholders of a completed negotiation |
Messaging Integration | Alert support in Slack when refund is requested |
Approval Step | Require approval before continuing |
Data Input Step | Request structured input from a user (e.g. date, reason) |
Task Completion Step | Wait for manual real-world action (e.g. call, proofread) |