Platform nodes pentrun8n

The verified @probo/n8n-nodes-probo The community package allows workflows to read and change platform records or start by signing platform events.

It provides two nodes:

Node	Use it to
the platform	Run a resource operation or a custom operationGraphQLfor each input item
the platform Trigger	Start a workflow when a platform-supported event occurs

Use the platform synchronize records, create reports, or enrich another system. the platform Trigger when the workflow should respond to a document, a user, an obligation, a rights claim, or a third party event.

Attention

The action node includes operations that update, publish, archive and delete records. Use a dedicated OAuth token with the smallest set of practical domains, limit platform user permissions, and test writing workflows against non-production data before activation.

Before we begin

You need:

• A instance8nCloud or auto-host with verified community nodes enabled.
• A owner or administrator8nwho can install the platform nodes.After installation, other court members can use them.
• A platform OAuth token, whose user can access the organizations and operations the workflow needs.
• A public HTTPS webhook URL when using the Trigger platform. your implementation.n8nshould announce the URL to which the platform can reach.

Install the package Add or update the inn8n community package

Configure credentials Connect the correct platform deployment with an OAuth token

Choose an automation pattern

Scheduled or input-driven work

Connect an upstream node to the platformThe action is executed once for each input, so that the expressions can map the values from $json into the operating fields.

Schedule Trigger → Probo: Task / Get Many → Filter → Slack

List operations commonly expose Return All and Limit. When Return All if enabled, the node automatically follows the connection pages of GraphQL. Use a dedicated operation when there is one, as it exposes the fields printed in the editorn8n.

Event-driven work

Start the workflow with the platform TriggerSelect an organization and one or more types of events, and then enable the workflow:

Probo Trigger: Document Version Published → Edit Fields → Slack

Activation creates a webhook subscription on the platform. Deactivation removes it. Signature verification and five-minute timestamp tolerance are enabled by default.

Data and errors

The output shape depends on the operation. List operations return one item per resource, while some creation, updating, and specialization operations retain part or all of the GraphQL response case. Inspect the node execution data before mapping a field downward. Custom operation GraphQL always returns the full response case.

By default, an operating error stops the node. Continue On Fail the setting when subsequent elements should still work; failed elements then contain a field error.

Explore the integration

Resource reference View all resources and operations generated by Action-Node

Execute resource Run a query or named mutation when there is no dedicated action

the platform Trigger Configure event subscriptions, payloads, and signature checks

Operational guidance

• Create an OAuth token on mediun8nastso that it can be rotated and revoked independently.
• Pin a package version for controlled production deployments and test upgrades before you run them.
• Keep destructive operations behind explicit conditions or approval steps.
• Stable use of platform IDs in workflow data; treat page IDs and cursors as opaque strings.
• The platform does not reset failed webhook deliveries, but it can still be reset manually or by managing workflow errors.