Integrations and external tools
Connecting Slack, Gmail, Notion or your own MCP servers to an agent: the app bank, the permission settings, and what stays out of reach.
4 Min. LesezeitAktualisiert am 8. August 2026
Diese Seite ist noch nicht in Ihre Sprache übersetzt und wird auf Englisch angezeigt.
An agent is not locked inside Odoo. It can post to Slack, send an email, write a Notion page, open a Jira ticket, provided you let it.
Two sources of tools
| Source | What it is | Who it is for |
|---|---|---|
| The app bank | Over 1,000 services connectable in a few clicks | Everyone |
| Your MCP servers | Your internal tools, already exposed over MCP | Teams with their own tooling |
The bank runs on Composio, which handles authentication and keeps the connectors current. Your MCP servers stay with you: Aidoo only records their address and their access secret, encrypted per workspace.
Integrations are not part of the trial
They unlock from the Starter tier. During the free trial, an agent works on Odoo alone.
Connecting an application
Open the Integrations page
The Agents space of the dashboard, "Integrations" entry. Only owners and admins can connect an account there.
Search for the application
The search queries the catalogue live. Type the name of the service: Slack, Gmail, HubSpot, Stripe.
Grant access
The connection opens in a new tab, on the provider's side. Depending on the service, that is an OAuth screen or an API key to paste. Aidoo never sees your password.
Come back and refresh
Back on the Integrations page, click "Refresh". The account appears with its status dot, healthy or in error.
The connection belongs to the workspace, not to whoever created it. Every agent can use it, once you allow them one by one.
What the catalogue holds
Search for the service you have in mind, or browse by area:
108 applications
- Slack
- Gmail
- Microsoft Teams
- Outlook
- Discord
- Telegram
- Zoom
- Google Chat
- Twilio
- SendGrid
- Front
- HubSpot
- Salesforce
- Pipedrive
- Zoho CRM
- Attio
- Close
- Copper
- Freshsales
- Apollo
- Outreach
- Lemlist
- Jira
- Linear
- Asana
- Trello
- ClickUp
- Monday.com
- Notion
- Basecamp
- Wrike
- Shortcut
- Todoist
- Height
- Zendesk
- Freshdesk
- Intercom
- Help Scout
- Crisp
- Google Sheets
- Google Docs
- Google Drive
- Google Slides
- Microsoft Excel
- OneDrive
- SharePoint
- Dropbox
- Box
- Airtable
- Coda
- Confluence
- DocuSign
- PandaDoc
- Stripe
- QuickBooks
- Xero
- PayPal
- Square
- Chargebee
- Brex
- Ramp
- Plaid
- GitHub
- GitLab
- Bitbucket
- Sentry
- PagerDuty
- CircleCI
- Jenkins
- Vercel
- Netlify
- Figma
- Google Calendar
- Outlook Calendar
- Calendly
- Cal.com
- Mailchimp
- Klaviyo
- Brevo
- ActiveCampaign
- Customer.io
- Typeform
- SurveyMonkey
- Google Ads
- Google Analytics
- Mixpanel
- Amplitude
- PostHog
- Canva
- Shopify
- WooCommerce
- BigCommerce
- Amazon
- Etsy
- BambooHR
- Workday
- Greenhouse
- Lever
- Personio
- Gusto
- OpenAI
- Anthropic
- Perplexity
- Exa
- Tavily
- Firecrawl
An extract of the most requested services. The Composio catalogue holds over a thousand and keeps evolving: the search on the Integrations page is what counts.
Only services whose authentication Composio manages show up in the dashboard search.
Letting an agent use one
Connecting an application hands it to nobody. Each agent gets its own list, in its configuration.
Five applications per agent, at most. Beyond that the conversation gets too heavy and the model loses focus.
Writing is a separate switch. By default, an agent wired to Slack can read, not post. You open writing application by application.
Restrict the tool list. An application often exposes dozens of tools. Without a restriction, every one of them is loaded on each conversation turn, inflating the credit bill for nothing. Two or three are almost always enough.
How Aidoo decides a tool writes
When the connector does not declare it, Aidoo classifies the tool by its name: create_, update_, send_ or delete_ count as writes, list_, get_ or search_ as reads. When in doubt, the tool lands on the write side, so it stays blocked until you open the switch.
Your own MCP servers
If you already expose internal tools over MCP (Streamable HTTP), declare them on the same page. Two authentication modes: a static header, such as Authorization: Bearer …, or OAuth.
Secrets are encrypted and tied to the workspace. A declared server is then enabled agent by agent, exactly like an application from the bank, with the same write switch and the same tool restriction.
The chat inside Odoo too
The "Aidoo AI" assistant embedded in your Odoo can use the connected applications. Its authorisation does not go through an agent: it is set per Odoo user, application by application, from the "Chat" button of each connected account.
What holds true whatever happens
Content coming back from a third-party service is treated as untrusted, exactly like Odoo data: a Slack message carrying instructions does not steer the agent.
Every external tool call is logged like the rest and appears in the run report.
Troubleshooting
| Symptom | Likely cause |
|---|---|
| The app does not show up in the search | The service has no managed authentication in the catalogue |
| The account is in error | The authorisation expired or was revoked on the provider's side: reconnect the account |
| The agent does not see the tool | The app is not enabled in its configuration, or the tool is missing from the restricted list |
| The agent reads but does not write | The write switch is closed for that application |
| "Integrations are not included in your plan" | You are on the trial: move up to the Starter tier |
Next step
- Rules and permissions: bounding what the agent touches in Odoo
- Credits and consumption: what external tools cost
- Best practices and troubleshooting: when an agent misbehaves