Automation library · Documents and files

Backup n8n workflows to Bitbucket

Started by a clock. It calls services over plain HTTP rather than through connectors. 9 steps, 1 branch, 2 loops or waits: a working afternoon to understand properly.

Medium

9 stepsMedium: a working afternoon
1Branch: places the flow splits
2Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 1Logic 5Service 3

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

  1. 1Run Daily at 2 AMSchedule triggerStarts it
  2. 2Set Bitbucket Workspace & RepositorySetLogic
  3. 3Get All WorkflowsN8nService
  4. 4Loop WorkflowsSplit In BatchesLogic
  5. 5Get Existing Worfklow from BitbucketHttp RequestService
  6. 6New or Changed?IfLogic
  7. 7Upload Workflow to BitbucketHttp RequestService
  8. 8Wait to Avoid Rate LimitingWaitLogic
  9. 9Calculate Wait TimeCodeLogic

How it's built

Starts on
A clock
Steps
9, with 1 branch, 2 loops or waits
Size
Medium: a working afternoon
Connects to
Nothing by connector; it calls services over plain HTTP
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account. 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. 9 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 9 steps before you point it at anything that matters.