Fix an existing workflow so it keeps working on n8n 3.0: replace removed nodes, rebuild removed AI Agent modes, rewrite removed expression helpers and review behavior changes flagged by the migration report. Load it when the user asks to migrate or update a workflow for n8n 3.0 or v3.
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
The user wants an existing workflow to keep working on n8n 3.0. The instance still runs 2.x, so the old nodes still load and run. The migration report lists one finding per workflow and rule, and re-checks a workflow each time it is saved, so a correct fix closes the finding by itself.
workflow-builder.workflow-builder for the edit mechanics, and in the same turn read
the workflow with get_workflow_as_code and the replacement node with
get_node_types.
Find each affected node from the finding by its name.ask_user before you edit.A replacement node keeps the old node's name, because downstream expressions reference nodes by name. It also takes over the old node's connections, credentials and settings such as "Always Output Data", "Retry On Fail" and "On Error".
Most Function code runs unchanged in the Code node. Change only what Code does not provide, and keep the code's logic as it is: do not refactor or reformat it.
functionCode parameter. items and $item() still work in Code.item is the whole item { json, binary }; in Function Item it was only the
JSON. Replace each use of item with item.json, and return
{ json: <result>, binary: item.binary }, because Function Item kept the
input item's binary data.getBinaryData() / setBinaryData() and their async variants do not exist
in Code. Read the item's binary property instead, and use
await this.helpers.getBinaryDataBuffer(itemIndex, propertyName) when the
code needs the file content.getWorkflowStaticData(type) becomes $getWorkflowStaticData(type).The old tool node used {placeholder} markers that the agent filled in, with
the placeholder definitions in a separate list. The replacement is the HTTP
Request node connected to the agent as a tool. Each placeholder becomes a
$fromAI('<name>', '<description>', '<type>') expression in the field that
used it. Keep the tool description, method, URL, authentication, headers and
query parameters, and use the old placeholder descriptions as the $fromAI
descriptions.
n8n-nodes-base.openAi) to the new OpenAI node.
Moderation maps to "Classify Text for Violations". Text edit and completion
have no direct target: use a chat message with instructions, and ask the
user when the intent is unclear.input; Chat Trigger passes
chatInput and sessionId. Update downstream references such as
$json.input.LangChain Code, Motorhead, Zep, Orbit and the GitHub Document Loader have no direct replacement. Do not guess. Explain what the node did in this workflow and ask the user to choose between the options that fit:
Replace the node with an AI Agent on the latest version. Reconnect its chat model, memory, tools and output parser, and carry over the system message and prompt. For the SQL Agent mode, connect a database tool with the same credential and move the old SQL prompt into the system message.
Rewrite each $getPairedItem(...) call as $('<node name>').item for the
paired item of the current item, as $('<node name>').itemMatching(index)
inside a Code node, or as $('<node name>').pairedItem(index) where the call
passed an index.
These findings do not break the workflow, but its output changes. Explain the change for this workflow and let the user decide. Do not change the workflow only to clear the finding.
in:sent.n8n-io/n8n
15aba30
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.