Use Composio to give the Sazabi agent access to your other SaaS tools

Last verified on Nov 8, 2026.

An incident rarely stays inside your observability tools. You need to know which customers are affected, who owns the service, whether a related ticket is open, and where to post the update. That information sits in a CRM, a docs workspace, a chat tool and a tracker, and each has its own login.

Composio aggregates many of those apps behind one MCP endpoint. With it connected, the Sazabi agent, part of Sazabi's AI-native observability and security platform, can reach the apps you have linked in Composio from the same thread where it reads your logs.

What the Sazabi agent can do with Composio

Sazabi connects to Composio's hosted Connect server at https://connect.composio.dev/mcp. You paste a Composio API key, which Sazabi stores and sends as the x-consumer-api-key header. Composio says the server gives access to 1000+ apps, but Sazabi's docs add the important limit: it only exposes tools for apps you have already connected in your Composio account.

Composio Connect exposes seven meta-tools, and the agent uses them to find and run the real tools:

• COMPOSIO_SEARCH_TOOLS finds tools in the Composio catalog for a request and suggests an execution plan.
• COMPOSIO_GET_TOOL_SCHEMAS fetches the input schema for the tool slugs search returned.
• COMPOSIO_MULTI_EXECUTE_TOOL runs one or more discovered tools in parallel, up to 50 per call.
• COMPOSIO_MANAGE_CONNECTIONS creates, lists, renames or removes OAuth connections to upstream apps, and COMPOSIO_WAIT_FOR_CONNECTIONS waits while a person completes an OAuth flow.
• COMPOSIO_REMOTE_WORKBENCH and COMPOSIO_REMOTE_BASH_TOOL run Python or bash in a remote sandbox, for bulk operations or large tool responses.

Those two sandbox tools run on Composio's side, not in Sazabi's own sandbox, so anything the agent sends them leaves Sazabi. Write operations follow the per-connection read-only toggle and your organization's tool policy.

Questions it answers

• Which of the affected customers have an open deal or ticket in the CRM?
• Is there a page in our docs workspace that describes this service's on-call owner?
• Has anyone already mentioned this error in chat today?
• Which issues in the tracker reference this service?
• Who should be told, and where is the right channel?

A worked example: finding affected accounts in a CRM

A deploy of checkout-api caused failed payments for about twenty minutes. Your logs list the account IDs that hit the error. The sales team needs to know which of those accounts are mid-negotiation. HubSpot is linked in your Composio project, so you ask:

From the checkout-api errors between 16:02 and 16:24 UTC, take the account
domains acct-104.example.com and acct-221.example.com. Use Composio to look
them up in HubSpot and tell me which have an open deal, and who owns each.

The agent reads the log window first to confirm the accounts. It then calls COMPOSIO_SEARCH_TOOLS with the request, and Composio returns the matching HubSpot tools plus a plan. COMPOSIO_GET_TOOL_SCHEMAS supplies the exact inputs, and COMPOSIO_MULTI_EXECUTE_TOOL runs the lookups for both domains in one call. If HubSpot were not yet linked, COMPOSIO_MANAGE_CONNECTIONS would start the OAuth step and COMPOSIO_WAIT_FOR_CONNECTIONS would pause until a person finishes it.

The useful habit is to keep the first pass read-only. Ask for the lookup, review who owns each account, and only then ask for a follow-up such as a note or a message, which will go through the write path and your tool policy. If the answer lists tools the agent did not need, narrow what you linked in the Composio dashboard rather than telling the agent to avoid them.

How it fits with other integrations

Composio is a general bridge, so prefer a dedicated page when one exists. Slack, Linear and Notion each have their own, with the exact tools and permissions. Use Composio for apps that have no connector of their own, like the CRM in the example above. Related agent tooling sits in the coding agents category, your services send telemetry through OpenTelemetry, and the integrations index lists every method. Pricing covers Sazabi plans.