Automation library · Alerts and monitoring

Log errors and audit events

Started by a clock, and works across n8n data table. 12 steps: a working afternoon to understand properly.

Medium

12 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 3Logic 4Service 5

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

  1. 1Error Trigger - GlobalError triggerStarts it
  2. 2Execute Workflow Trigger - Audit APIExecute Workflow triggerStarts it
  3. 3Schedule Trigger - Daily PurgeSchedule triggerStarts it
  4. 4Normalize Error EventCodeLogic
  5. 5Normalize Audit EventCodeLogic
  6. 6Build Purge ConfigCodeLogic
  7. 7Insert ErrorLogData TableService
  8. 8Insert AuditLogData TableService
  9. 9Delete old ErrorLog rowsData TableService
  10. 10Delete old AuditLog rowsData TableService
  11. 11Build Purge Audit EventCodeLogic
  12. 12Insert Purge AuditLogData TableService

How it's built

Starts on
A clock
Steps
12
Size
Medium: a working afternoon
Connects to
n8n data table
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. 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.

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