n8n - 💡(How to fix) Fix Notion node v2.2: API-created workflow with malformed `filters` shape silently redirects to new draft instead of rendering [1 comments, 2 participants]

Describe the problem/error/question

When a Notion node ([email protected]) is created via the public API or n8n-mcp with a filters parameter using the Notion REST API shape ({"and": [...]}) instead of the n8n-internal shape (filters.conditions[] with key|type keys), the workflow editor refuses to render the workflow. Instead of a validation error, the editor silently redirects to a fresh ?new=true draft. Each URL paste creates another empty draft, polluting the workflow list. The workflow exists server-side and is fully retrievable via GET /api/v1/workflows/:id — only the UI fails. Expected: editor loads the workflow and shows a clear validation error on the offending node, OR the create/update API rejects with a structured error. Actual: silent UI redirect with a brief unreadable error flash; orphan empty drafts created server-side.

What is the error message (if any)?

Visible only as a flash before the redirect — too short to read. No console-level error retained after navigation. Network tab shows a successful GET /workflow/<id> followed by an immediate client-side replace to /workflow/<newId>?new=true.

• error: all

TL;DR

The Notion node's filters parameter should be updated to use the n8n-internal shape (filters.conditions[] with key|type keys) instead of the Notion REST API shape ({"and": [...]}) to fix the workflow editor rendering issue.

Guidance

• Verify that the filters parameter in the Notion node is using the correct shape by checking the node's configuration in the workflow editor or the workflow JSON.
• Update the filters parameter to use the n8n-internal shape, as shown in the provided workaround example.
• Test the updated workflow by saving and reloading it in the editor to ensure it renders correctly.
• If issues persist, try checking the browser console for any error messages that may indicate the cause of the problem.

Example

"filters": {
  "conditions": [
    { "key": "Date|date",    "condition": "equals", "date": "={{ $today.toISODate() }}" },
    { "key": "Status|select", "condition": "equals", "selectValue": "planned" }
  ]
}

Notes

The provided workaround example demonstrates the correct shape for the filters parameter, but it is unclear if this is the only possible solution. Further testing and debugging may be necessary to fully resolve the issue.

Recommendation

Apply the workaround by updating the filters parameter to use the n8n-internal shape, as this has been shown to resolve the issue in the provided example.