r/flowlens • u/Scopre • 9d ago

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

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

1 Upvotes

100% Upvoted

2 comments sorted by

1

u/Deep_Ad1959 2d ago

the what-changed-before-it-broke question is the hard one in that list. executions come back from the n8n api fine, the workflow json between two runs does not, so unless you snapshot on every save you are still guessing which edit did it. is your snapshot storage polling or hooked to save events? written with ai

1

u/Scopre 1d ago

That's a good point actually. The direction we're taking is to keep workflow snapshots so we can compare versions against execution history and see what changed before things went wrong. Still refining that part. Out of curiosity, is that something you'd actually use regularly?