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": "CxC - Zendesk Trigger nativo (plantilla)",
"nodes": [
{
"parameters": {
"content": "## PLANTILLA DE PARTIDA - esqueleto del camino facil\n\nEl nodo **Zendesk Trigger** hace por ti lo que en el otro flujo se arma a mano:\n- Al ACTIVAR el workflow, crea automaticamente el webhook + trigger en Zendesk (y los borra al desactivar).\n- Valida la firma HMAC de cada entrega EL SOLO: no necesitas Crypto ni comparar headers.\n\nTras importar:\n1. Crea la credencial **Zendesk API** (subdominio, email, API token) y asignala al nodo.\n2. Revisa las condiciones en la UI: status / is / solved. Recuerda que en la API de Zendesk el trigger real usa {\"field\":\"status\",\"operator\":\"value\",\"value\":\"solved\"} y que `changed_to` NO existe para status; ademas `closed` es inmutable (no acepta comentarios ni tags), por eso se dispara en SOLVED.\n3. El trigger creado por n8n envia el payload estandar de Zendesk, NO el JSON custom canonico del MVP (ticket_id, customer_email, order_id, status, subject). Para extraer el custom field order_id tendras que mapearlo aguas abajo.\n4. Sustituye el nodo placeholder por la logica real (consultar orden, email, tag) o copia los nodos del otro flujo.\n\nLimite honesto: ganas velocidad de armado, pierdes control fino del payload y del trigger (anti-bucle con tag confirmacion_enviada hay que anadirlo en Zendesk a mano o aguas abajo).",
"height": 560,
"width": 520
},
"id": "sticky-trigger",
"name": "Sticky Note",
"type": "n8n-nodes-base.stickyNote",
"typeVersion": 1,
"position": [
-820,
-160
]
},
{
"parameters": {
"service": "support",
"conditions": {
"all": [
{
"field": "status",
"operation": "is",
"value": "solved"
}
]
},
"options": {}
},
"id": "zendesk-trigger",
"name": "Zendesk Trigger (status solved)",
"type": "n8n-nodes-base.zendeskTrigger",
"typeVersion": 1,
"position": [
-220,
60
]
},
{
"parameters": {},
"id": "noop-procesar",
"name": "Placeholder: procesar ticket solved",
"type": "n8n-nodes-base.noOp",
"typeVersion": 1,
"position": [
40,
60
]
}
],
"connections": {
"Zendesk Trigger (status solved)": {
"main": [
[
{
"node": "Placeholder: procesar ticket solved",
"type": "main",
"index": 0
}
]
]
}
},
"active": false,
"settings": {
"executionOrder": "v1"
}
}
For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
About this workflow
CxC - Zendesk Trigger nativo (plantilla). Uses zendeskTrigger. Event-driven trigger; 3 nodes.
Source: https://github.com/alinedmooner/cxc-technical-interview/blob/d1bea77adecd4e629557b017aa4fa35fd5b825ed/mvp/n8n/workflows/zendesk-trigger-flow.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.
Protect Pdf With The Password Using Convertapi. Uses manualTrigger, readWriteFile, stickyNote, httpRequest. Event-driven trigger; 7 nodes.
Kb Tool Confluence Knowledge Base. Uses executeWorkflowTrigger, httpRequest, stickyNote. Event-driven trigger; 7 nodes.
N8N Español - Ejemplos. Uses manualTrigger, executeCommand. Event-driven trigger; 7 nodes.
Manual Stickynote. Uses graphql, manualTrigger, stickyNote. Event-driven trigger; 7 nodes.
[E2E] Availability Exceptions - Create and Delete. Uses CUSTOM. Event-driven trigger; 7 nodes.