- Home
- Skills
- APIs & Backend
- n8n Workflow Safety Check
More screenshots
Works with the AI Agents you already use
n8n Workflow Safety Check
This skill finds those and nine other n8n mistakes in exported files, and tells you how to fix each one.
$5
n8n Workflow Safety Check
Example session with this skill installed
Check this project with n8n-workflow-safety-check.
- Read your context and instructions
- Compiled the n8n workflow safety
$ python3 scripts/check_n8n.py examples/risky
BLOCK backups/credentials.json:7 N03 DECRYPTED_CREDENTIALS_EXPORT
credential "Shop DB": postgres data in plain text (host, database, user, password, port, ssl)
Why: This is a credentials export made with n8n export:credentials --decrypted (or a copy of one): each credential's data (passwords, API keys, OAuth client secrets and tokens) is stored in plain text. Anyone with the file can use all of these accounts.
Safer: Remove the file from the repository and its history, change every credential in it, and move credentials between instances with the normal encrypted export plus the same N8N_ENCRYPTION_KEY.
BLOCK backups/credentials.json:23 N03 DECRYPTED_CREDENTIALS_EXPORT
BLOCK n8n-data/config:2 N04 ENCRYPTION_KEY_IN_FILE
BLOCK workflows/order-intake.json:54 N01 SECRET_IN_NODE_PARAMETERS
BLOCK workflows/order-intake.json:73 N02 COMMAND_FROM_INPUT
BLOCK workflows/order-intake.json:103 N05 SECRET_IN_PINNED_DATA
BLOCK workflows/support-chat.json:20 N01 SECRET_IN_NODE_PARAMETERS
REVIEW workflows/order-intake.json:12 N11 WEBHOOK_WITHOUT_AUTH
REVIEW workflows/order-intake.json:19 N12 RISKY_CODE_IN_CODE_NODE
REVIEW workflows/order-intake.json:30 N15 SQL_QUERY_WITH_EXPRESSION
REVIEW workflows/order-intake.json:48 N16 PLAIN_HTTP_REQUEST
REVIEW workflows/order-intake.json:62 N13 TLS_CHECK_OFF
REVIEW workflows/order-intake.json:84 N18 FILE_PATH_FROM_INPUT
REVIEW workflows/order-intake.json:96 N14 PERSONAL_DATA_IN_PINNED_DATA
REVIEW workflows/order-intake.json:183 N17 ANY_WORKFLOW_CAN_CALL
REVIEW workflows/support-chat.json:6 N11 WEBHOOK_WITHOUT_AUTH
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 4 files, 4 with n8n workflow content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
Paste an API token into an HTTP Request node's Authorization header instead of a credential and it is saved in plain text in the workflow: download the workflow to share it, post it as a template or commit it to git, and the token goes with it. A Webhook left on Authentication: None that feeds {{ $json.body.file }} into an Execute Command node lets anyone who finds the URL run commands on your n8n server, and a test call you pinned can keep your n8n-auth session cookie in the file. This skill finds those and nine other n8n mistakes in exported files, and tells you how to fix each one.
Your agent runs a scanner on your n8n workflow JSON files: single exports (Download or copied nodes), n8n export:workflow files with one or many workflows, and templates. It also reads credential exports and n8n's .n8n/config settings file. It parses each file to the exact line, knows each node by its type (Webhook, HTTP Request, Code, Execute Command, SSH, Postgres, MySQL, Chat and MCP triggers and more), treats values that start with = as n8n expressions, and tells expressions that read incoming data ($json, $input, $('Node'), $fromAI()) from safe ones ($now, $execution). Credentials referenced by id and name are fine, and Supabase anon keys are not reported. It never imports, activates or runs a workflow. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- N01: tokens, passwords and keys written into node parameters (Authorization and API-key headers, query keys, user:password URLs, Set fields, JSON bodies, Code nodes, Telegram bot tokens, Slack and Discord webhook URLs, provider keys)
- N02: Execute Command and SSH commands built from incoming data or AI tool input
- N03: credential exports made with --decrypted, with every secret in plain text
- N04: n8n's settings file with the instance encryption key
- N05: Authorization headers, session cookies and tokens saved in pinned data
REVIEW
- N11: Webhook and MCP Server triggers with no authentication, and public chats without login
- N12: Code and Function nodes using child_process, fs, eval or new Function (Python: subprocess, eval, exec)
- N13: allowUnauthorizedCerts (Ignore SSL Issues) turned on
- N14: real-looking emails, phone numbers, addresses and ID or card numbers in pinned data
- N15: SQL queries with expressions from incoming data instead of query parameters
- N16: HTTP requests to remote hosts over plain http://
- N17: workflows any workflow on the instance can call (callerPolicy any)
- N18: Read/Write Files from Disk paths built from incoming data
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason and safer approach for each rule
- A risky and a safe example project (two workflows, a credentials export and an n8n data folder), and the real report the scanner produces on the risky one
Limits It reads the exported files as written. Credentials stored inside n8n, instance settings and environment variables (such as NODE_FUNCTION_ALLOW_BUILTIN or N8N_RESTRICT_FILE_ACCESS_TO), community node internals and run-time data are not checked, and workflows kept only in the n8n database must be exported first. Form triggers are not reported. NOT FLAGGED is not a guarantee.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Static check of exported workflow, credential and settings files. Data that reaches a node through several other nodes is judged only by the expression in that node. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example files include clearly fake, inert tokens, an encryption key and customer details (NOTREAL, EXAMPLE, not-a-real-..., .example domains, a +44 7700 900xxx phone number from the range set aside for fiction) for the scanner to find. Nothing in them is run.