The flow
Starts it 3Logic 13Service 5
The steps in the order they run, from what starts it.
- 1Execute Workflow TriggerExecute Workflow triggerStarts it
- 2Manual TriggerManual triggerStarts it
- 3Schedule TriggerSchedule triggerStarts it
- 4Merge ItemsMergeLogic
- 5tag?SwitchLogic
- 6Get All WP PostsWordpressService
- 7isDiffOrNewCodeLogic
- 8/SetLogic
- 9GlobalsSetLogic
- 10Format JSONCodeLogic
- 11Check StatusSwitchLogic
- 12Get file dataGithubService
- 13Execute WorkflowExecute WorkflowLogic
- 14Same file - Do nothingNo OpLogic
- 15File is differentNo OpLogic
- 16File is newNo OpLogic
- 17If file too largeIfLogic
- 18ReturnSetLogic
- 19Edit existing fileGithubService
- 20Create new fileGithubService
- 21Get FileHttp RequestService
How it's built
- Starts on
- A clock
- Steps
- 21, with 3 branches
- Size
- Large: read it before trusting it with anything live
- Connects to
- GitHub, WordPress
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own GitHub and WordPress accounts. 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 21 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.
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 21 steps before you point it at anything that matters.