Human Intervention
Human Intervention lets a Workflow pause at a specific step and wait for a person to provide input, make a decision, or approve a request. Once the required response is received, the Workflow can continue based on that response.
Use Human Intervention when an automated process needs human judgment before proceeding.
Why Use Human Intervention?
Some tasks can be automated but still require human approval or a decision before the next step runs.
Example: Expense Approval
An expense-processing Workflow collects expense details automatically, then requests a manager's approval before proceeding with payment. The Workflow waits for the manager's response and can follow different paths depending on whether the expense is approved or rejected.
How to Set Up Human Intervention
1. Create a Workflow
Log in to viaSocket and create a new Workflow.
Select a Trigger, connect the required account, configure the Trigger, and test it.
2. Add Human Intervention
Click + Add Step.
Select Built-in Tools → Human Intervention.
3. Choose an Interaction Service
Select the service through which the person will receive the request and respond:
Slack
Email
WhatsApp Business Cloud (Meta)
M91
Telegram
Configure the selected service as required.
4. Configure the Interaction
Set up the message or request that the recipient will receive.
Create response buttons: Add buttons that let the recipient choose an available response, such as Approve or Reject.
Map Workflow variables: Insert dynamic values from the Workflow to personalise the message or include relevant information.
Use response values: Store or map the response so later steps can use it in conditions to determine what happens next.
5. Receive the Response
The request is sent through the selected service. The recipient can review the information and respond using the available interaction options.
6. Configure the Next Steps
Add the Actions that should run after the response is received. Use conditions to define different paths for different responses.
For example:
Approved: Continue to the payment-processing step.
Rejected: Notify the requester and stop the approval path.
7. Test and Publish
Test the Workflow to verify that the request reaches the recipient, the response is captured correctly, and the appropriate next steps run. Publish the Workflow when everything works as expected.
Best Practices
Include enough context in the request so the recipient can make an informed decision.
Use clear response buttons, such as Approve and Reject.
Map response values into conditions to control what happens next.
Test both approval and rejection paths before publishing.
Need Help?
If Human Intervention isn't working as expected, contact viaSocket Support at [email protected]. Include your Workflow name and a screenshot of the History/Log to help the team investigate.