Automation library · Documents and files

Push and update files in GitHub

Started by an event in a connected app, and works across GitHub. 10 steps: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 2Service 7

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

  1. 1When clicking "Execute Workflow"Manual triggerStarts it
  2. 2PullGitService
  3. 3GitHub get fileGithubService
  4. 4configSetLogic
  5. 5Update README and add new fileExecute CommandService
  6. 6Decode fileCodeLogic
  7. 7Add filesGitService
  8. 8GitHub push edited fileGithubService
  9. 9CommitGitService
  10. 10PushGitService

How it's built

Starts on
An event in a connected app
Steps
10
Size
Medium: a working afternoon
Connects to
GitHub
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. 10 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 10 steps before you point it at anything that matters.