Governance for automations built outside engineering
Count every flow. Measure what it touches.
FlowCensus finds every automation your company runs, shows what each one reaches, and proves when the risk is gone.
n8n today · read-only key · flow content and secrets never stored
- CriticalUnauthenticated webhook writes to production DBtouches Finance
- HighReal customer data frozen in pinnedDatatouches Customers
- HighAPI key hard-coded in an HTTP nodetouches CRM
- MediumError path silently drops orderstouches Sales
The blind spot
Your company already runs automations nobody inventoried.
Finance, sales and operations build their own flows in n8n and AI tools. Each one holds credentials, reaches systems and moves data. Security only finds out when something breaks.
What exists?
No inventory of instances, flows and the credentials they use. Shadow automation grows faster than any review process.
What does it reach?
A webhook is harmless or critical depending on what sits behind it. Rule-based scanners cannot tell the difference.
Who fixes it?
Findings without an owner become tickets nobody picks up. The person who built the flow is the one who can fix it.
How it works
Census, ruler, proof.
We read the file that describes each automation, rebuild what it reaches and who built it, and rank risk by what it touches in the business — not by the rule that fired.
Census
Connect each n8n instance with a read-only API key, or upload the exported workflows. FlowCensus counts every flow, active or not, and maps the systems, data and credentials it uses.
Ruler
Technical severity and business impact are separate axes. The same rule on two flows can carry very different risk, and the ranking shows which areas stop if a flow fails.
Proof
Each finding has an owner and a plain-language fix guide. Resolved means gone in the next scan, and FlowCensus measures how much your builders fix on their own.
Same rule. Different risk.
Severity tells you what fired. Impact tells you what matters.
Webhook without authentication
Posts the daily standup reminder to a Slack channel.
Technical severity: high
Business impact: low
Webhook without authentication
Creates invoices in the ERP and emails them to customers.
Technical severity: high
Business impact: critical
Trust by construction
A census of weaknesses is a target document. We built for that.
If FlowCensus is compromised, the attacker gets no credential that authenticates into your systems, no personal data of your customers, and not the content of your flows.
- The raw workflow JSON — it lives in memory during the scan and is never written
- Secret values, in any form: not the value, not part of it, not a hash
- The content of pinnedData — only that it exists
- Personal data of your customers
What we do keep — flow, node and credential names — is encrypted per customer, in a database of its own. Offboarding deletes that database and issues a dated deletion certificate.
How we protect your dataWho it is for
One view for the CISO. One fix for the builder.
For the CISO
A single inventory of every automation, ranked by business impact, with an owner for each finding and a number that shows the risk going down.
For the builder
Findings in plain language, a guide for each fix and no tickets thrown over the wall. The scan shows what you fixed, too.
Pricing
Public pricing. No procurement cycle.
Self-service plans from $59 a month, sized by the number of n8n instances you connect. Every plan starts with a free scan.
Questions
Before you connect anything.
Which platforms do you cover?
What access do you need?
Do you read execution data?
Where is the data hosted?
Find out how many automations your company really runs.
The free scan shows the size of your estate — totals and severities, no names — before you pay anything.