The flow
Starts it 1Logic 16Service 3
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Set RetriesSetLogic
- 3GET Epic Games Free Games pagePuppeteerService
- 4Extract offersHtmlLogic
- 5If has ResultsIfLogic
- 6Split OutSplit OutLogic
- 7Wait between requestsWaitLogic
- 8Extract title and imageHtmlLogic
- 9Extract labelSetLogic
- 10Update RetriesSetLogic
- 11Prepare dataMergeLogic
- 12If Has RetriesIfLogic
- 13Check if changedCodeLogic
- 14Wait for conditionsMergeLogic
- 15Notify on errorDiscordService
- 16Only when changedFilterLogic
- 17Prepare notificationCodeLogic
- 18SuccessMergeLogic
- 19Notify DiscordHttp RequestService
- 20Save Static DataCodeLogic
How it's built
- Starts on
- A clock
- Steps
- 20, with 2 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Discord
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Discord 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. 20 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 20 steps before you point it at anything that matters.