Automation library · Setup and learning

Monitor & debug n8n workflows with MCP

Started by another system calling it. It calls services over plain HTTP rather than through connectors. 11 steps, 1 branch: a working afternoon to understand properly.

Medium

Download free
11 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 2Logic 6Service 3

The steps in the order they run, from what starts it.

  1. 1WebhookWebhookStarts it
  2. 2Route by ActionSwitchLogic
  3. 3Get Active WorkflowsHttp RequestService
  4. 4Get Last ExecutionsHttp RequestService
  5. 5Get Executions Details (Status = Error)Http RequestService
  6. 6Split Active ExecutionsSplit OutLogic
  7. 7Extract All ExecutionsSplit OutLogic
  8. 8Details of ExecutionsSplit OutLogic
  9. 9Active WorkflowsSetLogic
  10. 10Processing AuditCodeLogic
  11. 11Respond to WebhookRespond To WebhookStarts it

How it's built

Starts on
Another system calling it
Steps
11, with 1 branch
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 another system calling it.

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. 11 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 it

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 11 steps before you point it at anything that matters.