The flow
Starts it 1Logic 10Service 6
The steps in the order they run, from what starts it.
- 1When clicking ‘Execute workflow’Manual triggerStarts it
- 2configSetLogic
- 3list_repo_filesGithubService
- 4get_only_workflowsFilterLogic
- 5github_repo_errorStop And ErrorLogic
- 6get_restored_workflowsData TableService
- 7get_not_restoredCodeLogic
- 8error_geting_restored_worflowsStop And ErrorLogic
- 9loop_over_itemsSplit In BatchesLogic
- 10truncate_control_tableData TableService
- 11get_workflow_fileHttp RequestService
- 12workflows_restoredNo OpLogic
- 13error_truncating_control_tableStop And ErrorLogic
- 14get_workflow_contentCodeLogic
- 15restore_workflowN8nService
- 16save_restored_workflow_dataData TableService
- 17error_saving_restored_workflowStop And ErrorLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 17, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- GitHub, n8n data table
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own GitHub account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
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. 17 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 17 steps before you point it at anything that matters.