The flow
Starts it 1Model 4Logic 8Service 3
The steps in the order they run, from what starts it.
- 1When Form SubmittedForm triggerStarts it
- 2If File Size ≤ 50MBIfLogic
- 3Fetch Upload URLMcp ClientModel
- 4Notify File Too LargeFormService
- 5Append File to Upload RequestCodeLogic
- 6Upload File to URLHttp RequestService
- 7Initiate File TransformationMcp ClientModel
- 8Check Transformation StatusMcp ClientModel
- 9Route by Job StatusSwitchLogic
- 10Fetch Transformation ResultsMcp ClientModel
- 11Wait for 5 SecondsWaitLogic
- 12Halt with ErrorStop And ErrorLogic
- 13If Download URL AvailableIfLogic
- 14Download Transformation ResultsHttp RequestService
- 15Set No Content StatusSetLogic
- 16Set Final Output FormatSetLogic
How it's built
- Starts on
- Someone submitting a form
- Steps
- 16, with 3 branches, 1 loop 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 someone submitting a form.
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.
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.