The flow
Starts it 1Service 16
The steps in the order they run, from what starts it.
- 1Get a fired alerts reportSplunk ToolService
- 2Get metricsSplunk ToolService
- 3Create a search reportSplunk ToolService
- 4Delete a search reportSplunk ToolService
- 5Get a search reportSplunk ToolService
- 6Get many search reportsSplunk ToolService
- 7Create a search jobSplunk ToolService
- 8Delete a search jobSplunk ToolService
- 9Get a search jobSplunk ToolService
- 10Get many search jobsSplunk ToolService
- 11Get the result of a search jobSplunk ToolService
- 12Create a userSplunk ToolService
- 13Delete a userSplunk ToolService
- 14Get a userSplunk ToolService
- 15Get many usersSplunk ToolService
- 16Update a userSplunk ToolService
- 17Splunk Tool MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 17
- 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 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?
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.
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 17 steps before you point it at anything that matters.