Integrations

Composio

How PIILOT uses Composio for managed integrations and tool execution.

PIILOT uses Composio as the managed integration layer for supported external applications. Composio provides toolkit discovery, managed authorization configuration, connected-account links, connected-account status refresh, and tool execution for configured workflow actions.

PIILOT stores the connection identifiers and metadata required to reference a Composio connection. The underlying OAuth authorization flow is handled by Composio and the connected application.

What PIILOT sends to Composio

Toolkit search queries and toolkit slugs when discovering integrations.
Auth configuration creation or lookup requests for managed auth flows.
User identifiers for connected-account links.
Callback URLs so authorization returns to PIILOT.
Connected-account identifiers when refreshing status or executing a tool.
Tool slug, user id, connected account id, and tool arguments when executing an action.

Composio execution path

flowchart TD
  A[Workflow connector node]
  A --> B[Setup compiler]
  B --> C[Resolve Composio tool]
  C --> D[Attach connected account]
  D --> E[Prepare tool arguments]
  E --> F[Execute through Composio]
  F --> G[Connected application]
  G --> H[Return tool result]
  H --> I[Update workflow context]

No blind scopes

Users should review requested scopes and connected-account permissions before authorizing an integration. PIILOT can map and validate workflow setup, but connected-app access remains a user and workspace responsibility.