platforma Trigger pentrun8n

The the platform Trigger Node launches a workflow8when a subscribed platform event occurs. it replaces the survey with a managed webhook subscription as part of the workflow life cycle.

Requirements

• platform credentialsAPIwith access to the selected organization and permission to manage webhook subscriptions.
• A production webhook URL that the platform can reach via HTTPS.
• The correct configuration of the public webhook inn8n, especially whenn8rule behind a reverse proxy.

How it works

When you enable a workflow that includes the Trigger platform:

1. The node creates a platform webhook subscription for the selected organization and events.
2. the platform delivers the signed requests POST to the webhook URL of the node.
3. The node checks the HMAC-SHA256 signature and timestamp freshness by default.
4. The workflow runs with the webhook task as an input.
5. When you disable the workflow, the node deletes the subscription.

If the organization, selected events, or webhook URL changes, the node removes the static subscription and creates a corresponding subscription during activation.

Configuration

Field	Description
Organization ID	Organization that publishes events
Events	One or more types of events to subscribe to
Verify Signature	Refusing deliveries with a missing or invalid HMAC signature; enabled by default
Timestamp Tolerance (Seconds)	Reject deliveries outside this past or future window; by default 300. Set to 0 only to disable freshness checking.

Credentials use the same the platform API credentials Like a node of action.

Attention

Keep signature verification enabled. Disabling it allows any system that knows the webhook URL to initiate the workflow.

Supported events

The Trigger platform supports the same set of events as webhook subscriptions, including:

• Third party created / updated / deleted
• User created / updated / deleted
• Obligation created / updated / deleted
• Rights request created / updated / deleted
• Document created / updated / archived / unarchived / deleted
• Document version created / updated / published / rejected / deleted
• Document version signature requested / signed / cancelled
• Document version approval quorum requested / updated / approved / rejected / voided

See the full wire-format payloads in Webhook Event Types.

Output

Each trigger execution produces the entire JSON body of the webhook – the root cover plus the embedded resource fields:

Root field	Description
eventId	Unique delivery identifier (good idempotency key)
subscriptionId	Webhook subscription ID
organizationId	Organization ID
eventType	Event type (e.g. document:updated)
createdAt	Event timestamp
data	Current utility load of the entity (resource fields live here, not at the root)
updatedFrom	Present on *:updated events — instant image of the entity before modification

The platform also sends HTTP titles such as X-Probo-Webhook-Event, X-Probo-Webhook-Organization-Id, X-Probo-Webhook-Timestamp, X-Probo-Webhook-Signature, and X-Probo-Webhook-Host. Webhooks Overview for reference to the entire header/root field.

Example expressions:

{{ $json.eventType }}
{{ $json.organizationId }}
{{ $json.updatedFrom.membership.role }}
{{ $json.data.membership.role }}

Quickstart

1. Add the platform Trigger to a new workflow.
2. Select credentials şi a stabilit Organization ID.
3. Choose events, for example Document Version Signature Signed.
4. Add downstream nodes which uses $json.data (and $json.updatedFrom for updates).
5. Activate the workflowThe node automatically records the production webhook subscription.

Build reliable event workflows

• Filter on eventType before accessing the event-specific fields under data.
• Check if there are optional fields. updatedFrom is present only for update events.
• Use eventId as an idempotency key before creating an external side effect.
• Maintain the quick response of the workflow. the trigger recognizes the webhook before running downwards.
• Configure an error8 workflow for downstream failures. the platform does not trace failed webhook deliveries.

Troubleshooting

Symptom	Check
Activation cannot create the subscription	v1:webhook scope, user permissions, organization ID and production webhook URL configured den8n
the platform cannot deliver	Public DNS, HTTPS certificate, reverse proxy, firewall and subscription endpoint URL
Delivery returns 403	Signature verification status, server clocks and whether the subscription was recreated after a change
Workflow receives no selected event	The workflow is active and the event belongs to the selected organization and event set
Duplicate downstream action	Deduplicate with eventId and manually review or re-encrypt the workflow

Dock8ns moved to a new public URL, disable and reactivate the workflow so the node can replace the old subscription.

Related

Webhook overview Reviewing the envelope, titles and delivery behavior

Event types Check the task fields for each accepted event