The flow
Starts it 2Logic 6Service 3
The steps in the order they run, from what starts it.
- 1Manual Execution TriggerManual triggerStarts it
- 2Daily Trigger at 6amSchedule triggerStarts it
- 3Set Actor Task IDSetLogic
- 4Execute TED Monitoring TaskApifyService
- 5Check Dataset AvailabilityIfLogic
- 6Fetch Dataset RecordsApifyService
- 7Report No Dataset FoundCodeLogic
- 8Process Dataset RecordsCodeLogic
- 9Check for Record PresenceIfLogic
- 10Upsert TED RecordsData TableService
- 11Report After IngestionCodeLogic
How it's built
- Starts on
- A clock
- Steps
- 11, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- Apify, n8n data table
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Apify 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. 11 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 11 steps before you point it at anything that matters.