Scan n8n Workflows for n8n 3.0 Breaking Nodes & OpenAI Shutdowns
Scan n8n Workflows for n8n 3.0 Breaking Nodes & OpenAI Shutdowns
Regular price
£58.99
Regular price
£58.99
Sale price
Unit price
/
per
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
Couldn't load pickup availability
🔥
128+ Sold
Popular with n8n builders
⚡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
Scan n8n Workflows for n8n 3.0 Breaking Nodes & OpenAI Shutdowns
Regular price
£58.99
Regular price
£58.99
Sale price
Unit price
/
per
Scan your n8n workflows for n8n 3.0 breaking changes and OpenAI model shutdowns—then email one clear report
This manually run n8n automation fetches all workflows from your n8n instance, scans them for node types removed in n8n 3.0 and for OpenAI model IDs with published shutdown dates, and emails you a single plain-text summary. Catch issues early—before deployments break.
What this workflow does
- Runs on manual trigger (execute when you choose) to start the scan.
- Sets the From and To email addresses used to deliver the report.
- Uses the n8n API to retrieve every workflow definition from your n8n instance.
- Scans each workflow’s nodes and parameters for known n8n 3.0 removals and specific patterns, including:
- AI Agent v1 (deprecated pattern)
- Deprecated “Execute Sub-workflow” sources
- Usage of the removed
$getPairedItemhelper
- Detects OpenAI model IDs referenced in node parameters and flags matches found in a built-in list of shutdown dates.
- Builds a single text summary and sends it via SMTP using the email step.
Use cases
- Before upgrading to n8n 3.0, quickly identify workflows that will fail due to removed nodes or helpers.
- When planning AI changes, locate any workflows still referencing OpenAI models scheduled for shutdown.
- For SaaS operators managing many automations, centralize risk visibility with one email report.
Technical details
- Manual trigger + n8n API workflow retrieval
- Nodes: set, code, email send, sticky note, manual trigger
- Requires an n8n API key in the credential used to read workflows
- Requires an SMTP email credential for the email-sending step
Run it manually, review the emailed plain-text findings, and fix breaking references—fast.
