How integrations work through Composio
HIIE's integrations are powered by Composio. The Connections section is where you browse the catalog, connect your accounts, manage your bring-your-own keys, and see which Composio key your account runs under.
The model
When you connect an app, you authorize it explicitly through a real per-user flow. The Composio key that powers these connections is resolved server-side and is never sent to your browser. Once connected, those tools become available to Camelia and to flow steps that call an MCP tool.
How Camelia uses connected tools
Camelia can search your available integrations and execute their actions on your behalf. Actions are classified as read or write: read actions run immediately so Camelia can answer your question, while write actions (post, send, create, delete, update, and similar verbs) raise a human approval popup before they run. You stay in control of anything that changes data in an external system.
Where to manage everything
The Connections section is organized into four areas:
- Browse — the integration catalog.
- Connected — the accounts you have actually connected.
- Credentials — your encrypted bring-your-own key vault (Composio and OpenRouter).
- Environment — which Composio key mode your account runs under, with a live health badge.
Isolation
Every connection and credential is scoped to your account, and resolved keys are never returned to the browser or logged. This keeps your authorizations isolated from other tenants while letting Camelia take real actions across the tools you have approved.