The flow
Starts it 2Logic 9Service 4
The steps in the order they run, from what starts it.
- 1Run every hourSchedule triggerStarts it
- 2When clicking ‘Execute workflow’Manual triggerStarts it
- 3Get Chorus Engagement per last dayHttp RequestService
- 4Merge paginated engagementsCodeLogic
- 5Filter items with empty meeting_summaryFilterLogic
- 6Loop Over EngagementsSplit In BatchesLogic
- 7Search Company In HubSpot By NameHttp RequestService
- 8If company existsIfLogic
- 9Search notesHttp RequestService
- 10Skip, if company not foundNo OpLogic
- 11If note not existIfLogic
- 12Create Note PayloadCodeLogic
- 13Skip, if note already existsNo OpLogic
- 14Create NoteHttp RequestService
- 15ContinueNo OpLogic
How it's built
- Starts on
- A clock
- Steps
- 15, 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. 15 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 15 steps before you point it at anything that matters.