Automation library · Alerts and monitoring

Automated GitHub backup for n8n workflows with Slack

Started by a clock, and works across GitHub and Slack. 13 steps, 2 branches: a working afternoon to understand properly.

Medium

13 stepsMedium: a working afternoon
2Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Logic 5Service 7

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

  1. 1Every 5 MinutesSchedule triggerStarts it
  2. 2ConfigurationSetLogic
  3. 3GitHub: List filesGithubService
  4. 4GitHub: File namesAggregateLogic
  5. 5Get All WorkflowsN8nService
  6. 6Discard Archived WorkflowsFilterLogic
  7. 7If File ExistsIfLogic
  8. 8Get a fileGithubService
  9. 9Create a fileGithubService
  10. 10If Not EqualIfLogic
  11. 11Send Success MessageSlackService
  12. 12Send Failed MessageSlackService
  13. 13Edit a fileGithubService

How it's built

Starts on
A clock
Steps
13, with 2 branches
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. 13 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 13 steps before you point it at anything that matters.