n8n 3.0 removes the Function node, and published workflows stop activating

Описание и применение

После обновления до n8n 3.0 опубликованные рабочие процессы, использующие удалённые узлы, автоматически деактивируются, что приводит к остановке триггеров. Миграция включает замену узлов Function и Function Item на Code‑узлы, проверку работоспособности и публикацию, после чего можно безопасно обновиться до версии 3.0.

Задача

Published n8n workflows that use removed nodes become inactive after upgrading to 3.0, causing triggers to stop firing without any error notification.

Результат

After following the migration steps, workflows that previously used removed nodes are re‑activated in n8n 3.0, restoring trigger functionality and preventing silent failures.

Рабочий процесс

• 1. Open Settings → Migration Report to list affected workflows and nodes.
• 2. If on a version older than 2.39, upgrade to 2.39 first to generate the report.
• 3. Export workflows via /api/v1/workflows or CLI and search for legacy node identifiers.
• 4. Create a migration plan listing workflow name, node, and purpose.
• 5. Replace Function nodes with Code nodes (Run Once for All Items) and Function Item nodes with Code nodes (Run Once for Each Item).
• 6. Test each migrated workflow manually on 2.x, verify output shape, then publish.
• 7. Upgrade to n8n 3.0 with a backup, noting that rollback is not possible.
• 8. After upgrade, review the workflow list and check the active toggle for every workflow to ensure none are inactive.

Доказательства

Workflows that use a removed node fail when they run. If such a workflow is published, it doesn't activate when n8n 3.0 starts, so its triggers stop firing.

Источник

The Function to Code conversion is the only real work, because the execution model changes:…

Источник

Open the workflow list and look at the active toggle on every workflow, not only the ones you migrated.

Источник