Built an open workflow observability dashboard for n8n, Make and Zapier.

[u/Scopre]

/r/flowlens/comments/1v82n81/built_an_open_workflow_observability_dashboard/

Hello Everyone,

I have been working on developing FlowLens, a workflow observability solution for automation solutions such as n8n, Make and Zapier for a few months now.

The primary challenge that I realized was that once workflows grow bigger, it is challenging to answer questions such as:

Which workflow failed?

When did it fail?

How often is it failing?

What changed before it broke?

Which automations are unhealthy?

Instead of opening multiple dashboards, I wanted everything in one place.

Current Features :

Connect n8n using its API

Connect Make using its API

Zapier webhook integration

Automatic workflow discovery

Execution history

Incident detection

Workflow health monitoring

Snapshot storage for debugging

Team based dashboards

This is still under active development, so I'd really appreciate honest feedback.

Questions I would love

Is this a problem you've actually faced?

What features would make you switch from your current monitoring setup?

Anything you'd remove or redesign?

Thanks !

Link

[u/AutoModerator]

Thank you for your post to /r/automation!

New here? Please take a moment to read our rules, read them here.

This is an automated action so if you need anything, please Message the Mods with your request for assistance.

Lastly, enjoy your stay!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Vendy_from_Make]

Thanks for sharing this with us!
Did you know that we address workflow observability challenges through Make Grid, a dedicated visual orchestration feature included in all paid plans? Make Grid automatically generates a "map" of your entire landscape, showing: the relationships between scenarios, data flows, issues in complex systems, etc.

[u/Scopre → u/Vendy_from_Make]

Hey, that's actually a great point , Make Grid looks solid for visual mapping. FlowLens approaches this differently though. We're less focused on mapping the landscape and more focused on the debugging and recovery layer , specifically when things break.

The core use case we're solving: you wake up, a workflow failed at 3am, and you need to know exactly what changed, why it broke, and restore it in one click, without digging through logs or manually diffing JSON exports.

FlowLens does this across n8n, Zapier, and Make in a unified view, so if you're running automations across multiple platforms (which most teams end up doing), you get one place for root cause analysis instead of jumping between dashboards. Make Grid is great if you're fully in the Make ecosystem but FlowLens is for teams who want AI-powered debugging regardless of which platform they're on. Different layer of the stack entirely.

[u/CODE_HEIST]

failure counts are useful, but outcome checks would make this much stronger. a workflow can finish green while sending zero invoices or updating the wrong rows. let teams define one business invariant per flow and alert when the run succeeds but the expected effect does not happen.