Built systems

ErrorLens: Make broken automations visible and actionable.

ErrorLens gives teams a clear place to investigate workflow failures. Execution details, severity, suggested next steps and incident ownership sit together, while logging and Slack alert paths bring the failure context into the team’s daily operating rhythm.

ErrorLens

Filtered incident queue — About this view
Product interface
Local filters and incident records.

Owned incident detail — About this view
Product interface
Local ownership and resolved-state controls do not prove destination repair.

Original ErrorLens monitoring workflow in n8n — About this view
Local import only
Published creator JSON imported into the local editor. Inactive; no credentials or executions.

Monitoring classification and logging branch — About this view
Local import only
Native local source detail. Log to Sheet uses the Google Sheets HTTP API.

Error classification, Sheets logging and Slack alert — About this view
Local import only
Deterministic native-source crop. Local import, inactive and never executed.

What it does

Incident review interface with filters, failure detail and assigned ownership.
Failure-context views covering classification, severity and suggested next steps.
Recovery review controls with incident status and a local resolved state.

Why it matters

Makes failure investigation and responsibility easier to coordinate, with the context needed to decide the next recovery action.

reported lost after automation failures before this build: 3 clients / 2 monthsOwner-reported pre-build problem context, not a measured retention or savings result.
only if the same reported loss rate repeated: 18 clients / yearLinear exposure scenario: 3 clients × six two-month periods. Not clients retained or revenue saved after this build.

Explore the interface

Walkthrough

Under the hood

Error monitoring - original creator workflow

12 nodes · 8 non-note nodes

Open read-only HTML explorer →Download explicitly sanitized review JSON

Technology stack

n8n
JavaScript
Slack
React

Build note

3 clients lost. A better way to catch the next broken workflow.

Source & context

Historical engagement documentation.

Native n8n imports are local and inactive, not production execution. Historical recording capture dates are unknown; a displayed report period is not its capture date. Local source review: October 27, 2026. Public release and client-material clearance remain separate.

The failure had a business cost

Ahmad reports that the commissioning company lost approximately three clients in two months when automations broke. That is the reason for the system, not proof that the same amount was subsequently saved. The recovered source shows how failures are collected, classified and put in front of the team.

Collect the failure before asking someone to fix it

The original creator workflow uses a schedule or webhook, fetches failed n8n executions, filters recent failures and excludes its own runs. The local capture shows that actual source topology, imported without credentials and never executed.

Classify, log and alert

The source classifies failures into seven categories with severity and a suggested next step. Log to Sheet is an HTTP Request to the Google Sheets API, followed by the Slack alert path. A native Google Sheets node is not required for that logging step.

Make recovery a human-owned decision

The broader ErrorLens interface adds the review surface: filters, incident detail, an owner and a local resolved state. An alert or a local resolved flag does not prove the affected business record was repaired. The responsible person still checks the destination.

Inside the system

Cross-platform visibility Documented failure review across n8n, Make and Zapier.
Incident owner Connects available failure context to a responsible person.
Recovery decision Separates investigation from permission to change a workflow.
Destination check Verifies the affected business result after an authorized action.

The handoff

Failure-signal map
Shared review requirements
Incident ownership
Recovery acceptance checks

Technology stack

Workflow source

n8n
JavaScript
Slack

Recovered workflow includes Code, HTTP, schedule, webhook, Slack and Sheets logging structure.

This local walkthrough

React

Reconstructed interface with incident records.

Not established

Production hosting and execution are not established.

Source reading

Original published creator workflow JSON

Source & context

View	Provenance and limitation	Evidence class
Fig. 1	ErrorLens incident overview Local interface with incidents; not current client failures.	Product interface
Fig. 2	Filtered incident queue Local filters and incident records.	Product interface
Fig. 3	Owned incident detail Local ownership and resolved-state controls do not prove destination repair.	Product interface
Fig. 4	Original ErrorLens monitoring workflow in n8n Published creator JSON imported into the local editor. Inactive; no credentials or executions.	Local import only
Fig. 5	Monitoring classification and logging branch Native local source detail. Log to Sheet uses the Google Sheets HTTP API.	Local import only
Fig. 6	Error classification, Sheets logging and Slack alert Deterministic native-source crop. Local import, inactive and never executed.	Local import only

Historical engagement documentation.

Reviewed: 2026-10-27

Map one workflow handoff

Bring one workflow and the output the next person needs. Define its inputs, review decision and completion check before agreeing implementation scope.

Discuss a workflow →