The flow
Starts it 1Logic 11Service 6
The steps in the order they run, from what starts it.
- 1Start WorkflowManual triggerStarts it
- 2Prepare ClickUp TaskSetLogic
- 3Set Meeting InfoSetLogic
- 4Create ClickUp TaskClick UpService
- 5Send to Transcription APIHttp RequestService
- 6Prepare Teams MessageSetLogic
- 7Transcription Request OK?IfLogic
- 8Send Summary to TeamsMicrosoft TeamsService
- 9Wait for ProcessingWaitLogic
- 10Prepare Error MessageSetLogic
- 11Fetch TranscriptHttp RequestService
- 12Send Error to TeamsMicrosoft TeamsService
- 13Extract Transcript TextCodeLogic
- 14AI SummarizeHttp RequestService
- 15Extract Summary JSONCodeLogic
- 16Summary Exists?IfLogic
- 17Generate Action ItemsCodeLogic
- 18Merge Summary & ActionsMergeLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 18, with 2 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- ClickUp
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own ClickUp 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. 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.
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 18 steps before you point it at anything that matters.