Integration Node

The Integration node is a unified connector: you pick a provider and one of its operations, and the node delegates to that provider's executor. It replaces the per-provider node types with a single entry point.

When to Use

Use Integration to interact with a connected platform without hand-rolling HTTP calls — for example, sending a Slack message, reading or writing files in Google Drive, or calling another provider's supported operation.

Configuration

The available operations and their parameters are defined per provider in the integration definitions; the configuration panel surfaces the fields each operation needs. Providers with a dedicated executor (such as google-drive) handle validation and execution themselves; all others run through the generic integration executor.

Example

Run a provider operation (Slack shown):

provider: slack
operation: post_message

(Operation-specific fields — such as the target channel and message — are configured alongside provider and operation.)

Notes

• The provider must be connected and authorized under Settings → Integrations before it can be selected.
• Integration calls run on the governed external rail and are classified as action:integration scope, so guardrails are evaluated before the operation runs.
• If no provider is selected, or the provider is unknown, the node fails validation with a clear message.
• For arbitrary REST endpoints with no dedicated provider, use the HTTP node instead.