Creators portal: Node still in review. Why?

Wen submitted an update to our node and the status we see in the creators portal is “Update Changes Required”. But after 10 dayse there is no display what kind of changes are required - empty page!

Is this a bug in the creators portal? Did we miss something?

Please help, users urgently need the update!

The node concerned is “n8n-nodes-ckan” and the new version is 1.3.0.

Hi @ondics

Since you have been waiting for 10 days with an empty feedback page, you should reach out to the team to request the specific changes or ask them to clear the status. Use the following channels:

  • Email: Send a message to nodes@n8n.io or support@n8n.io.
  • Details to include: To speed up the process, clearly state:
    • Node Name: n8n-nodes-ckan
    • Version: 1.3.0
    • Issue: Portal shows “Update Changes Required” but the feedback page is empty.

For faster visibility, post in the #community-nodes channel on the official n8n Discord. Mention that your node is stuck in “Update Changes Required” with no visible feedback; the team members there can often ping the reviewers or provide a quick status update.

Adding to what kjooleng shared - as someone who’s been through the review process with several nodes, “Update Changes Required” with an empty feedback page usually means the reviewer left internal notes that aren’t surfaced to the portal UI yet, or the feedback email went to spam. Check your inbox for any message from nodes@n8n.io including spam/promotions folders. The most common reasons I’ve seen for that status on updates specifically: the new version wasn’t published to npm before submitting the portal update (the reviewer tests the actual npm package), or the package.json description or keywords fields don’t meet their content guidelines. Worth double-checking that npm info n8n-nodes-ckan shows version 1.3.0 publicly before following up.

Done. Email was sent to support@n8n.io.

The npm package is up to date and all fields like version, description, etc. in package.json are current.

What else can we do?

ok, now we can see the review notes in the creators portal.

the errors are fixed and the version is updated on npm.

the re-review can start.