The flow
Starts it 1Service 20
The steps in the order they run, from what starts it.
- 1Create a clientHalo PSAToolService
- 2Delete a clientHalo PSAToolService
- 3Get a clientHalo PSAToolService
- 4Get many clientsHalo PSAToolService
- 5Update a clientHalo PSAToolService
- 6Create a siteHalo PSAToolService
- 7Delete a siteHalo PSAToolService
- 8Get a siteHalo PSAToolService
- 9Get many sitesHalo PSAToolService
- 10Update a siteHalo PSAToolService
- 11Create a ticketHalo PSAToolService
- 12Delete a ticketHalo PSAToolService
- 13Get a ticketHalo PSAToolService
- 14Get many ticketsHalo PSAToolService
- 15Update a ticketHalo PSAToolService
- 16Create a userHalo PSAToolService
- 17Delete a userHalo PSAToolService
- 18Get a userHalo PSAToolService
- 19Get many usersHalo PSAToolService
- 20Update a userHalo PSAToolService
- 21HaloPSA Tool MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 21
- 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 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?
Take your time. At 21 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.
Before you run itNothing 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 21 steps before you point it at anything that matters.