The flow
Starts it 2Logic 12Service 4
The steps in the order they run, from what starts it.
- 1Manual Capacity InspectionManual triggerStarts it
- 2Every 30-Minute CheckSchedule triggerStarts it
- 3Set Capacity Policy ParametersSetLogic
- 4Validate Policy ConfigurationsCodeLogic
- 5Retrieve Metrics History DataOpen ObserveService
- 6Analyze Pressure MetricsCodeLogic
- 7Draft Capacity RecommendationsCodeLogic
- 8Batch Process ResourcesSplit In BatchesLogic
- 9Summarize Capacity FindingsCodeLogic
- 10Evaluate Task Creation NeedsIfLogic
- 11Locate Review Task in CRMTwentyService
- 12Document Findings Without CRM LogCodeLogic
- 13Plan Task Creation or UpdateCodeLogic
- 14Check Task ExistenceIfLogic
- 15Update Existing Review TaskTwentyService
- 16Generate New Review TaskTwentyService
- 17Log Refreshed Task ChangesCodeLogic
- 18Log New Task CreationCodeLogic
How it's built
- Starts on
- A clock
- Steps
- 18, with 2 branches, 1 loop or waits
- 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 a clock.
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. 18 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 itNothing 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 18 steps before you point it at anything that matters.