The workflow JSON
Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →
{
"name": "HUMAN_HANDOFF",
"nodes": [
{
"parameters": {
"workflowInputs": {
"values": [
{
"name": "Customer"
},
{
"name": "Human"
},
{
"name": "Instance"
},
{
"name": "Reason"
}
]
}
},
"id": "c055762a-8fe7-4141-a639-df2372f30060",
"typeVersion": 1.1,
"name": "Tool Activated",
"type": "n8n-nodes-base.executeWorkflowTrigger",
"position": [
272,
352
],
"alwaysOutputData": false
},
{
"parameters": {
"operation": "set",
"key": "=customer:{{ $json.Customer }}:mode",
"value": "human"
},
"type": "n8n-nodes-base.redis",
"typeVersion": 1,
"position": [
480,
352
],
"id": "67c1345d-9168-44c6-be71-a546b8c66817",
"name": "Human Mode",
"credentials": {
"redis": {
"name": "<your credential>"
}
}
},
{
"parameters": {
"resource": "messages-api",
"instanceName": "={{ $json.Instance }}",
"remoteJid": "={{ $('Tool Activated').item.json.Human }}",
"messageText": "=O contato {{ $('Tool Activated').item.json.Customer }} foi transferido para o atendimento humano.\n\nMotivo: {{ $('Tool Activated').item.json.Reason }}",
"options_message": {}
},
"type": "n8n-nodes-evolution-api.evolutionApi",
"typeVersion": 1,
"position": [
688,
352
],
"id": "2c28b0dc-cce3-4370-a444-79e46428f062",
"name": "Alert Human",
"credentials": {
"evolutionApi": {
"name": "<your credential>"
}
}
}
],
"connections": {
"Tool Activated": {
"main": [
[
{
"node": "Human Mode",
"type": "main",
"index": 0
}
]
]
},
"Human Mode": {
"main": [
[
{
"node": "Alert Human",
"type": "main",
"index": 0
}
]
]
}
},
"active": false,
"settings": {
"executionOrder": "v1",
"binaryMode": "separate",
"availableInMCP": false
},
"versionId": "REPLACE_WITH_WORKFLOW_VERSION_ID",
"meta": {
"templateCredsSetupCompleted": false
},
"id": "REPLACE_WITH_WORKFLOW_ID",
"tags": []
}
Credentials you'll need
Each integration node will prompt for credentials when you import. We strip credential IDs before publishing — you'll add your own.
evolutionApiredis
For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
About this workflow
HUMAN_HANDOFF. Uses executeWorkflowTrigger, redis, n8n-nodes-evolution-api. Event-driven trigger; 3 nodes.
Source: https://github.com/Guazzihub/Chatbot-AI-Assistant/blob/main/Workflows/Tools/HUMAN_HANDOFF.json — original creator credit. Request a take-down →
Related workflows
Workflows that share integrations, category, or trigger type with this one. All free to copy and import.
Reagendamiento. Uses executeWorkflowTrigger, redis, n8n-nodes-evolution-api, dataTable. Event-driven trigger; 73 nodes.
Agendamiento. Uses n8n-nodes-evolution-api, redis, dataTable, executeWorkflowTrigger. Event-driven trigger; 60 nodes.
Prevent concurrent workflow runs using Redis. Uses executeWorkflowTrigger, manualTrigger, stickyNote, executeWorkflow. Event-driven trigger; 43 nodes.
This workflow sets a small "lock" value in Redis so that only one copy of a long job can run at the same time. If another trigger fires while the job is still busy, the workflow sees the lock, stops e
This implementation aggregates incoming data into a Redis list from potentially concurrent workflow executions. It buffers the data for a set period before a single execution retrieves and processes t