The flow
Starts it 1Logic 8Service 7
The steps in the order they run, from what starts it.
- 1Schedule Daily at 3 AMSchedule triggerStarts it
- 2Get Industry SourcesFunctionLogic
- 3Fetch Source PageHttp RequestService
- 4Extract Page LinksFunctionLogic
- 5Fetch Article ContentHttp RequestService
- 6Parse Article ContentFunctionLogic
- 7Rate Limit DelayWaitLogic
- 8Is Relevant?IfLogic
- 9Check if TechnicalFunctionLogic
- 10Store in Knowledge BaseHttp RequestService
- 11Analyze Content OpportunitiesHttp RequestService
- 12Is Technical Content?IfLogic
- 13Has Marketing Opportunity?IfLogic
- 14Extract Technical CodesHttp RequestService
- 15Create Response CampaignHttp RequestService
- 16Store Technical CodesHttp RequestService
How it's built
- Starts on
- A clock
- Steps
- 16, with 3 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. 16 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 16 steps before you point it at anything that matters.