Automation library · Customer support

Triage and escalate Twenty CRM support cases

Started by an event in a connected app. It calls services over plain HTTP rather than through connectors. 10 steps, 2 branches: a working afternoon to understand properly.

Medium

Download free
10 stepsMedium: a working afternoon
2Branches: places the flow splits
0Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 1Logic 5Service 4

The steps in the order they run, from what starts it.

  1. 1Watch for new support casesTwenty triggerStarts it
  2. 2Get support caseTwentyService
  3. 3Case already triaged?IfLogic
  4. 4Skip previously triaged caseNo OpLogic
  5. 5Build triage policyCodeLogic
  6. 6Find existing triage taskTwentyService
  7. 7Triage task already exists?IfLogic
  8. 8Use existing or created taskNo OpLogic
  9. 9Create owner triage taskTwentyService
  10. 10Mark support case as triagedTwentyService

How it's built

Starts on
An event in a connected app
Steps
10, with 2 branches
Size
Medium: a working afternoon
Connects to
Nothing by connector; it calls services over plain HTTP
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 10 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 10 steps before you point it at anything that matters.