Automation library · Documents and files

OCR image

Started by an event in a connected app. It calls services over plain HTTP rather than through connectors. 8 steps, 1 loop or waits: small enough to read in one sitting and change without fear.

Small

8 stepsSmall: readable in one sitting
0Branches: places the flow splits
1Loop or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 1Logic 2Service 5

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

  1. 1When clicking ‘Test workflow’Manual triggerStarts it
  2. 2Read/Write Files from DiskRead Write FileService
  3. 3Loop Over ItemsSplit In BatchesLogic
  4. 4Extract from FileExtract From FileService
  5. 5HTTP RequestHttp RequestService
  6. 6Convert to FileConvert To FileService
  7. 7Write Files from DiskRead Write FileService
  8. 8Replace MeNo OpLogic

How it's built

Starts on
An event in a connected app
Steps
8, 1 loop or waits
Size
Small: readable in one sitting
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 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?

Not long. At 8 steps it can be read in one sitting and changed without fear.

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