Connect your own tools, with your own accounts
Garuda customers connect their own third-party accounts through Composio, whose catalogue held 1,431 connectable products when this page was last checked. You authorise each provider yourself and the connection belongs to your workspace alone. Today that surface is connection management — agents do not yet call these tools during a conversation.
Checked against the running product on 30 August 2026. Everything here describes what Garuda does today.
What can Garuda connect to?
Garuda connects to third-party tools through Composio, an integration broker whose catalogue held 1,431 connectable products when this page was last checked on 30 August 2026. Google Calendar, Slack, HubSpot, Salesforce and Highlevel are all in it, alongside roughly 1,400 others.
These are examples, not the whole catalogue. The “actions” column is the number of operations Composio publishes for that product, counted from its live API on 30 August 2026.
| Product | Listed under | Actions in the catalogue |
|---|---|---|
| Google Calendar | Scheduling & Booking | 45 |
| Slack | Team Chat, Team Collaboration | 158 |
| HubSpot | CRM, Marketing Automation | 244 |
| Salesforce | CRM, Contact Management | 184 |
| Highlevel | Marketing Automation, CRM | 218 |
| Zendesk | CRM, Customer Support | 451 |
| Mailchimp | Email Newsletters, Marketing Automation | 272 |
| Shopify | eCommerce | 315 |
| Notion | Notes, Documents, Project Management | 53 |
| Calendly | Scheduling & Booking, Calendar | 52 |
Whose account does an integration use — mine or Garuda's?
Yours. Every customer connects their own third-party account: you authorise the provider yourself, and the connection is stored against your Garuda account id, so one customer's connection can never be reached through another's. Garuda does not operate a shared account on your behalf.
The tokens for a connected account are held and refreshed by Composio against your account id. No third-party refresh token is stored in Garuda’s own data. When a connection is removed, Garuda first re-reads the list of connections that belong to your account and refuses the request if the connection is not one of yours — a connection belonging to someone else is reported as simply not found.
How do I connect a tool?
Open Integrations in your Garuda workspace, search the catalogue, choose a product and select Connect. Garuda asks Composio for an authorisation link, you sign in with the provider and approve the access, and you come back to a workspace that lists the connection. Disconnecting is one action in the same place.
- Search or browse the catalogue, which is paged rather than loaded whole — it is far too large for one screen.
- Select Connect on the product you want. Garuda requests an authorisation link scoped to your account id.
- Authorise with the provider itself. Where a product supports OAuth you sign in on its own site, so you never hand Garuda a password.
- The connection appears in your workspace, and only in your workspace.
Connecting requires an active subscription: a workspace without one gets a “subscription required” response rather than an authorisation link. Integrations do not cost anything beyond the $17 monthly plan, though the third-party services you connect have their own pricing.
What kinds of tools are in the catalogue?
The catalogue is grouped into categories such as CRM, Scheduling & Booking, Team Chat, Marketing Automation, Email Newsletters, Customer Support, eCommerce and project management. Garuda reads those groupings straight from Composio, so the list grows as the catalogue does.
| Category | Examples in the catalogue |
|---|---|
| CRM | HubSpot, Salesforce, Zendesk, Highlevel |
| Scheduling & Booking | Google Calendar, Calendly |
| Team Chat & Collaboration | Slack |
| Marketing Automation | HubSpot, Mailchimp, Highlevel |
| Email Newsletters | Mailchimp |
| Customer Support | Zendesk |
| eCommerce | Shopify |
| Notes, Documents & Project Management | Notion |
Can my agent use a connected tool during a conversation?
Not yet, and it is worth being blunt about it. What exists today is connection management: browse the catalogue, connect your own account, see what is connected, disconnect it. Garuda's chat agents do not yet call those tools mid-conversation — no calendar is booked and no CRM record is written from inside a chat.
Stated as a table, so there is no room for misreading:
| Capability | Status today |
|---|---|
| Browse the catalogue of connectable products | Available |
| Connect your own account through the provider | Available |
| See and remove your workspace's connections | Available |
| An agent calling a connected tool during a chat | Not built yet |
| Per-agent connections | Not built yet — connections belong to the workspace |
What exactly does Composio do in this?
Composio is the integration broker. It publishes the catalogue, runs the authorisation flow with each provider, and stores and refreshes the resulting tokens against the account id Garuda supplies. Garuda registers nothing per integration and holds no provider credentials of its own.
The reason Garuda uses a broker rather than writing one adapter per product is simple arithmetic: a catalogue of 1,431 products is not something a small team converges on one integration at a time. The trade-off is equally plain — connected accounts live with Composio, which is a third party in your data path for anything you connect.
Still have a question?
Every answer on this site is written from the product as it works today. If something here does not match what you see, treat the product as the truth and tell us.