Connections And Integrations
11 articles
How integrations work through Composio
HIIE integrations run on Composio. You authorize each app explicitly, and Camelia can then read from or write to it, with write actions gated behind your approval.
Browsing the integration catalog and connecting an app
The Browse tab is the Composio catalog. Pick an app, check its auth badge, and start a real per-user connection flow that runs server-side.
Authorizing an OAuth integration and how the flow completes
OAuth apps run a real per-user flow: HIIE opens a server-provided redirect, you authorize the provider, then HIIE polls until the connection is active.
Connecting API-key and custom-auth apps
API-key and custom-auth apps prompt you for credentials during connection, stored with the connection. The flow runs server-side and the Composio key never reaches your browser.
Read vs write integration actions and when approval is required
Read actions run immediately; write actions (post, send, create, delete, update) require your approval unless you enable auto-approve. A server-side token enforces the gate.
Viewing your connected accounts in the Connected tab
The Connected tab lists the integrations you've actually authorized and that reached an active state — the apps whose tools Camelia and your flows can use.
The Credentials vault: storing your BYO Composio and OpenRouter keys
The Credentials vault stores your own Composio and OpenRouter keys, encrypted at rest. A BYO OpenRouter key makes managed-inference runs free and unmetered on your account.
Composio key modes explained: BYO, dedicated project, and shared
Composio keys resolve in three tiers: your BYO key (most private), a per-account dedicated project key, or a shared managed key isolated per user. No key ever reaches the browser.
Checking the Environment tab's key mode and health badge
The Environment tab shows your resolved Composio key mode (byo, project, shared, or none) with a live health badge, and only ever displays a masked key hint.
Rotating a dedicated Composio project key
Accounts on a dedicated Composio project key can rotate it from the Environment tab. HIIE mints a replacement server-side, encrypted at rest and never shown to the browser.
Why integration keys are never sent to your browser
Integration keys stay server-side and are encrypted at rest; the browser only ever sees masked hints. This keeps keys off the client, though it is not end-to-end encryption.