Triage and escalate Twenty CRM support cases with owner tasks
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 10 nodes and runs on Twenty events. Along the way it connects Twentycrm (community).
How it runs
Trigger: On Twenty events.
- Get support case (Twenty): get (record)
- Case already triaged? (If): checks a condition and branches into true / false
- Build triage policy (Code): runs custom JavaScript code
- Find existing triage task (Twenty): work with task
- Triage task already exists? (If): checks a condition and branches into true / false
- Create owner triage task (Twenty): create (task)
- Mark support case as triaged (Twenty): update (record)
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 2 community packages, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @blackswampai/n8n-nodes-twentycrm is verified or supports 3.0 (used in Watch for new support cases).
- Check that @blackswampai/n8n-nodes-twentycrm is verified or supports 3.0 (used in Get support case, Find existing triage task, Create owner triage task).
Nodes used (5)
- Twenty Trigger
@blackswampai/n8n-nodes-twentycrm.twentyTrigger - Twenty
@blackswampai/n8n-nodes-twentycrm.twenty - If
n8n-nodes-base.if - No Operation, do nothing
n8n-nodes-base.noOp - Code
n8n-nodes-base.code
From the author
Quick Overview This workflow triggers on new Twenty CRM custom supportCase records, applies an urgent or standard SLA based on priority, creates or reuses a deterministic owner task, and updates the support case with triage metadata for replay-safe…