n8n-nodes-workflow-redactor: free helper for checking workflow exports

Built with n8n
1

I ran into this workflow-review problem and built a small published n8n node that may help: n8n-nodes-workflow-redactor.

The goal is simple: make one narrow n8n workflow issue easier to check before sharing, debugging, or handing it off.

I built it around the recurring workflow-sharing and secret-cleanup use case. Feedback on false positives or missing patterns is welcome.

Published on npm: https://www.npmjs.com/package/n8n-nodes-workflow-redactor

What it helps check:

- API keys, tokens, private URLs, copied auth headers, or unclear workflow handoff details.

- Whether the workflow needs a deeper cleanup before being shared publicly.

Install:

```bash

npm install n8n-nodes-workflow-redactor

```

Free package: https://www.npmjs.com/package/n8n-nodes-workflow-redactor

If the free check is not useful for this thread, ignore it.

No revenue guarantee. Do not share workflows containing real secrets, customer data, or private tokens.

Posting note: this is a help-first free helper. Feedback, limitations, and removal requests are welcome.

1 Like
2

Nice idea! I think a tool like this fills a real gap since people often upload workflows with secrets still embedded.

A few features I’d love to see:

  • Risk levels (Critical, Warning, Info) so users know which findings require immediate action versus simple cleanup.
  • Configurable rules, allowing teams to add their own patterns (internal URLs, API key formats, company-specific secrets, etc.).
  • Redacted preview that shows exactly what will be replaced before exporting the workflow.
  • CI/CD support, so the node or CLI can be run automatically before publishing workflows to GitHub or submitting them to the n8n template library.
  • Detection of hard-coded credentials inside Code nodes, HTTP Request headers, and Set nodes, since those are common places where secrets get missed.
  • A final summary report with counts of secrets found, nodes affected, and recommended actions.

One additional suggestion would be to detect sensitive business data as well—not just API keys. Things like email addresses, phone numbers, webhook URLs, database connection strings, and customer IDs often get shared accidentally during debugging.

Overall, this looks like a useful utility, especially for developers who frequently share workflows with clients or the n8n community. I could see it becoming part of a standard “pre-share checklist” before exporting a workflow.

1 Like