Install the platformin8n nodes

The platform is distributed as @probo/n8n-nodes-probo n8ndistributes it directly through the pen8nCloud node selector and self-hosted instances. the platform action node and the platform Trigger.

Requirements

• A instance8nCloud or auto-host with verified community nodes enabled.
• n8n 1.0 or later.
• The role of owner or administrator inn8n.

All court members can use the nodes after a owner or administrator installs them. If the platform does not appear in the nodes selector, ask the court owner to activate verified community nodes.

Install directly from node picker

1. Open a workflow canvas.
2. Deschideţi node picker prin selectarea +.
3. Search for the platform.
4. Select the platform from More from the community.
5. Check the actions accepted and select Install.
6. Add the platform or the platform Trigger In terms of workflow.

This is the recommended installation method for both pentrun8nCloud and pentrun8nauto-host. verified community node guide at the level of control.

Self-hosted installation options

Self-hosted administrators can also install the npm package by Settings → Community Nodes, manually or via community package environmental variables8n.These options are useful for attached container images, queue-mode implementations and infrastructure-managed versions.

To use Settings → Community Nodes, select Install and enter @probo/n8n-nodes-probo.

For a manual installation:

Latest

mkdir -p ~/.n8n/nodes
cd ~/.n8n/nodes
npm install @probo/n8n-nodes-probo

Pinned version

mkdir -p ~/.n8n/nodes
cd ~/.n8n/nodes
npm install @probo/n8n-nodes-probo@<version>

Reopen each processn8nwhich loads nodes after installation.In queue mode, the main process and all workers must use the same version of the package.

___ZBT_I18N_RUNTIME_BLOCK_175__

Installing a package inside a container in operation is usually temporary.Add the package to the image or mount a persistent data directory8to survive a redistribution.

Pin and update versions

For production, attach the package version to your image or deployment configuration.

1. Check the current version of the package installed inn8n.
2. Test important workflows in a non-production n8n instance.
3. Updating each major process and workers together.
4. Reactivate a trigger workflow if your deployment does not automatically restore its webhook record.

Use the community node management UI8 for app updates.

cd ~/.n8n/nodes
npm install @probo/n8n-nodes-probo@<version>

Remove the package

Deactivate workflows that use the platform Trigger before removal, so thatn8we can delete their subscriptions to the webhook platform. Settings → Community Nodes, or run:

cd ~/.n8n/nodes
npm uninstall @probo/n8n-nodes-probo

Reopen and revoke any OAuth platform token that is no longer in use.

Next step

Configure a the platform API credentialThen test a read-only operation before enabling a workflow that changes the data.