The flow
Starts it 1Service 20
The steps in the order they run, from what starts it.
- 1Create TicketZammad ToolService
- 2Get TicketZammad ToolService
- 3Get Many TicketsZammad ToolService
- 4Delete TicketZammad ToolService
- 5Create UserZammad ToolService
- 6Get UserZammad ToolService
- 7Get Many UsersZammad ToolService
- 8Get Current UserZammad ToolService
- 9Update UserZammad ToolService
- 10Delete UserZammad ToolService
- 11Create OrganizationZammad ToolService
- 12Get OrganizationZammad ToolService
- 13Get Many OrganizationsZammad ToolService
- 14Update OrganizationZammad ToolService
- 15Delete OrganizationZammad ToolService
- 16Create GroupZammad ToolService
- 17Get GroupZammad ToolService
- 18Get Many GroupsZammad ToolService
- 19Update GroupZammad ToolService
- 20Delete GroupZammad ToolService
- 21MCP Server TriggerMcp 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.
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 21 steps before you point it at anything that matters.