The flow
Starts it 1Logic 9Service 13
The steps in the order they run, from what starts it.
- 1Technical Support PortalForm triggerStarts it
- 2Configuration VariablesSetLogic
- 3Contact informationFormService
- 4Get session tokenHttp RequestService
- 51. Request or incidentSwitchLogic
- 6Request FormFormService
- 7Incident FormFormService
- 81. Check if File ExistsIfLogic
- 92. Check if File ExistsIfLogic
- 101. Upload FileHttp RequestService
- 11Request Category IDCodeLogic
- 122. Upload FileHttp RequestService
- 13Incident Category IDCodeLogic
- 14Create RequestHttp RequestService
- 15Create IncidentHttp RequestService
- 16If1IfLogic
- 17IfIfLogic
- 181. Link File to TicketHttp RequestService
- 19Finish RequestFormService
- 202. Link File to TicketHttp RequestService
- 21Finish IncidentFormService
- 22Sign Out GLPIHttp RequestService
- 23No Operation, do nothingNo OpLogic
How it's built
- Starts on
- Someone submitting a form
- Steps
- 23, with 5 branches
- Size
- Large: read it before trusting it with anything live
- 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?
Take your time. At 23 steps it is large: read it before trusting it with anything live.
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 23 steps before you point it at anything that matters.