Community Node Rollout

Describe the problem/error/question

What are the steps involved to rolling out a community node. Once a community node has been successfully created. What are the next steps. How does it get enabled within the N8N hosted offering. Is their a validation step. How does it get tested for security. How are upgrades handled. How are scalability concerns addressed - not becoming an noisy neighbor.

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

hello @TechAllstar

You are building the node, publishing it on the npm portal, and that’s all. Once it’s published to the npm, you can enable it in the settings >> community nodes.
Install and manage community nodes | n8n Docs

n8n guys have nothing in common with the node, so it’s completely depends on the node’s author how to update it, publish patches and other stuff

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.