Automation library · Alerts and monitoring

Daily workflow backups to GitHub with Slack

Started by a clock, and works across GitHub and Slack. 16 steps, 2 branches, 1 loop or waits: a working afternoon to understand properly.

Medium

Download free
16 stepsMedium: a working afternoon
2Branches: places the flow splits
1Loop or waits
2Services it connects to

The flow

Starts it 1Logic 8Service 7

The steps in the order they run, from what starts it.

  1. 1Schedule TriggerSchedule triggerStarts it
  2. 2Starting MessageSlackService
  3. 3ConfigSetLogic
  4. 4Get WorkflowsN8nService
  5. 5FilterFilterLogic
  6. 6Loop Over ItemsSplit In BatchesLogic
  7. 7Completed NotificationSlackService
  8. 8Get a fileGithubService
  9. 9Merge ItemsMergeLogic
  10. 10Is File too large?IfLogic
  11. 11isDiffOrNewCodeLogic
  12. 12Get FileHttp RequestService
  13. 13SwitchSwitchLogic
  14. 14Edit existing fileGithubService
  15. 15Create new fileGithubService
  16. 16ReturnSetLogic

How it's built

Starts on
A clock
Steps
16, with 2 branches, 1 loop or waits
Size
Medium: a working afternoon
Connects to
GitHub, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own GitHub and Slack 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?

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 it

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 16 steps before you point it at anything that matters.