The flow
Starts it 2Logic 10Service 10
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Schedule Trigger1Schedule triggerStarts it
- 3Setup FlowSetLogic
- 4Insert Data By Status SendingNoco DbService
- 5Get all flow templates from NocoDBNoco DbService
- 6IF Type EmailIfLogic
- 7Filter TemplateFilterLogic
- 8If email is not emptyIfLogic
- 9IF Template Parameters OKIfLogic
- 10Disposal CheckIfLogic
- 11Status-no-emailNoco DbService
- 12Get user_id from dcpNoco DbService
- 13Brevo Send EmailSend In BlueService
- 14Status-disposal-emailNoco DbService
- 15IF user_id is not emptyIfLogic
- 16Update DataNoco DbService
- 17Map DataSetLogic
- 18Add records By Status ProcessingNoco DbService
- 19WaitWaitLogic
- 20Insert Data By Status ProcessingNoco DbService
- 21Remove DuplicatesRemove DuplicatesLogic
- 22Change Status to SendingNoco DbService
How it's built
- Starts on
- A clock
- Steps
- 22, with 5 branches, 1 loop or waits
- Size
- Large: read it before trusting it with anything live
- Connects to
- NocoDB
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own NocoDB 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?
Take your time. At 22 steps it is large: read it before trusting it with anything live.
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 22 steps before you point it at anything that matters.