The flow
Starts it 1Service 11
The steps in the order they run, from what starts it.
- 1Bulk Search MD5 HashesHttp Request ToolService
- 2Bulk Search SHA1 HashesHttp Request ToolService
- 3List SHA1 ChildrenHttp Request ToolService
- 4Get Database InfoHttp Request ToolService
- 5Lookup MD5 HashHttp Request ToolService
- 6Lookup SHA1 HashHttp Request ToolService
- 7Lookup SHA256 HashHttp Request ToolService
- 8List SHA1 ParentsHttp Request ToolService
- 9Create Search SessionHttp Request ToolService
- 10Get Session ResultsHttp Request ToolService
- 11Get Top QueriesHttp Request ToolService
- 12hashlookup CIRCL MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 12
- 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. 12 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 12 steps before you point it at anything that matters.