The flow
Starts it 1Logic 8Service 8
The steps in the order they run, from what starts it.
- 1Run every day at 11:50pmSchedule triggerStarts it
- 2Set variablesSetLogic
- 3Index existing?Http RequestService
- 4Yes / NoIfLogic
- 5Search for today dataElasticsearchService
- 6Create the index: zammad_history_ticket_countElasticsearchService
- 7Are there datasets?IfLogic
- 8Read all states out of ZammadHttp RequestService
- 9Read all groups out of ZammadZammadService
- 10Delete all documents of todayElasticsearchService
- 11Reduce the fieldsSetLogic
- 12Merge dataMergeLogic
- 13Reduce to oneNo OpLogic
- 14Read all the counts out of ZammadHttp RequestService
- 15Merge againMergeLogic
- 16Reduce fields for elasticsearchSetLogic
- 17Create document in elasticsearchElasticsearchService
How it's built
- Starts on
- A clock
- Steps
- 17, with 2 branches
- 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 a clock.
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. 17 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 17 steps before you point it at anything that matters.