Connected apps

Your agents can work in the apps you already use: read and send mail, post to Slack, create Notion pages, file Linear issues, or manage HubSpot contacts. These are examples, not the full supported-app list.

Browse the full integration catalogue to find an app. For example, Sokko supports HubSpot. Each app page has its own link that you can share.

Connected apps are enabled by default for OpenClaw, Hermes, Eve, and Flue agents. Connecting accounts and running app actions require a paid plan. You must approve each account connection before an agent can use it.

Find a supported app

Ask your agent whether Sokko supports an app. It can check the live catalogue with sokko_available_apps and share the matching integration link immediately. Ask for the full list to return every connectable app. Catalogue lookup works even if the agent's connected-apps switch is off.

The catalogue lists Composio's full public toolkit catalogue, including apps that use API keys and apps without authentication. Each entry describes its connection method separately from its availability. An app missing from the examples on this page can still be supported. An app marked as unconnected to one agent can still be available for you to connect. Apps outside the catalogue may have another integration route, described below.

Managed OAuth apps use Composio's existing authorization setup. Apps such as Meta Ads can use a hosted token or API-key form instead. You enter the token on that page, and Sokko keeps it out of chat. Some apps require a custom OAuth client or other provider configuration first. Those apps remain visible with setup guidance. Apps without authentication remain visible too, but do not have an account connection flow. Your agent can research their documented usage options.

Connect from chat

Ask your own agent, “How do I connect Gmail?” or “Connect HubSpot.” The agent checks the catalogue and sends a clickable authorization link.

Open the link in your browser and approve the connection. For apps that use an API key, enter it on the hosted authorization page. You do not need to sign in to Sokko or open its dashboard. Never paste credentials into chat.

Return to the same chat and tell the agent you have finished. It checks the connection status before it uses the app. If authorization is still pending, finish the browser flow. If the link expired or authorization failed, ask for a fresh link. Links normally last about ten minutes.

Your agent can use the app as soon as it verifies the connection. No new chat, agent restart, or redeploy is needed. A support agent helping you connect a different agent will share the public integration page instead, since a chat authorization link always connects the account to the agent that created it.

Connect from the dashboard

When an app is missing from the catalogue

Ask your agent to find another way to connect it. The agent should check alternate app names, read Sokko documentation, and search official provider, Composio, and MCP documentation. A missing catalogue entry does not prove that an integration is impossible.

The agent should explain the best option it can verify, link to its sources, and identify the authentication requirements and next step. These may include:

• A custom MCP server. Ask your agent to add the provider's verified MCP configuration. It can register HTTP URLs or local stdio commands from chat using sokko_add_mcp_server. When credentials are needed, it sends a private setup link; enter secrets there and return to chat. No Sokko login is needed. See Custom MCP servers for examples and prerequisites. You can also use the dashboard: an owner or admin can open MCP servers, select Add server, and grant it to the intended agent. Sokko supports remote HTTP servers and local stdio commands. Use the provider's documented URL or command. Remote servers must use port 443 or 80. Enter tokens, custom headers, and secret environment values in the server's auth fields. Granting a server updates the agent's configuration and can redeploy it.
• A direct API or runtime integration. If the provider documents a suitable API or integration, the agent can help prepare that setup and check whether its runtime supports it. Add credentials through Secrets and API keys. That setup may require additional configuration and a redeploy.
• Additional platform support. A provider or Composio may support an app whose authentication Sokko does not yet handle. The agent should name that gap and explain what must be added. It cannot create a hosted connection link for an app outside the live catalogue.

Custom integrations are separate from Sokko's hosted app connections. Their provider may require its own account, permissions, or subscription. The agent must verify the proposed route before describing it as available in Sokko. If no route can be verified, it should explain what it checked and what remains unknown. It must not invent a URL or ask for credentials in chat.

Disabled connected apps, plan restrictions, and temporary service errors are different from an app missing from the catalogue. Follow the tool's next step for those conditions.

Connections belong to one agent

Each connected account belongs to the agent you selected. Connecting Gmail to one agent does not connect it to your other agents. Connect the account separately for each agent that needs access. Disconnecting one agent's account leaves the other agents' connections intact.

Changes take effect without a restart

Connecting or disconnecting an account, or changing the agent's switch, takes effect on the next gateway request. No redeploy is required. The credentials stay on the server and do not appear in the agent's environment or workspace.

Cost

App actions use your Sokko AI credits, the same balance your model usage uses. Generating a connection link and checking its status do not count as app actions. When credits run out, app actions stop until you add credits from Billing. See Plans and Model access.

Cursor agents

Cursor agents load their tools from the Cursor dashboard rather than from Sokko, so connected apps are not wired up for them yet. See Memory for the corresponding Cursor setup.