The flow
Starts it 1Logic 3Service 5
The steps in the order they run, from what starts it.
- 1Time Tracked Update TriggerClick Up triggerStarts it
- 2ClickUp: Get Task DetailsClick UpService
- 3ClickUp: Get Time Entry DetailsClick UpService
- 4Merge: Task & Time DataMergeLogic
- 5Code: Extract Sprint & Task DataCodeLogic
- 6OnProjectFolderHttp RequestService
- 7Route by Sprint TypeIfLogic
- 8HubSpot: Update Project Hours (actual_additional_requests_hours)Http RequestService
- 9HubSpot: Update Project Hours Sprint 1-4Http RequestService
How it's built
- Starts on
- An event in a connected app
- Steps
- 9, with 1 branch
- 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. 9 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 9 steps before you point it at anything that matters.