What are AI agent integrations?
AI agent integrations are the connections that let an AI agent, or an app it built, act in other software: post to a Slack channel, append a row to a sheet, update a CRM record. Each one needs an authenticated account and a set of actions the agent can call.
Most business data still sits in apps that don't talk to each other. The average organization runs 957 applications and has connected only 27% of them 2.
Why is connecting an agent to your tools hard?
Every service wants its own OAuth app, scopes, token refresh and rate limits. Google treats full Google Sheets access as a sensitive scope, and an unverified app is limited to 100 new users 4.
The shortcut is a long-lived API key in a config file, and it is common. About 88% of open-source MCP servers need credentials, 53% rely on static keys or tokens and only 8.5% use OAuth 1. GitGuardian found 24,008 secrets exposed in MCP configuration files on public GitHub 3.
| Task | Building it yourself | On Sidechat |
|---|---|---|
| Register an OAuth app per service | Required | Not needed for one-sign-in apps |
| Store and refresh tokens | Your code and database | Handled |
| Keep API keys out of code and prompts | Your secret store | Encrypted with Google Cloud KMS, added at call time |
| Limit where a key can be used | Your code | Approved domains only |
| Revoke access | Per service | Disconnect in Integrations |
How does Sidechat handle sign-in and keys?
Sidechat holds the credentials, so your AI assistant and the apps it builds work with references, not the secrets.
- One sign-in per app
- You approve on a Sidechat page that names the app and what it is asking for, then sign in on the app's own screen. Tokens are refreshed automatically.
- Keys encrypted, held server-side
- Keys you add through Sidechat's secure prompt are encrypted with Google Cloud KMS and attached to requests on Sidechat's servers. Your assistant and your app's code only hold a reference.
- Locked to approved domains
- Each key works only for the domains you approve. A call to any other host, or a redirect to one, is refused.
- Disconnect any time
- Remove an app from Integrations and the connection is deleted.
How do you connect a tool?
Wiring an AI workflow to Slack or a spreadsheet usually means registering an OAuth app, storing and refreshing tokens, and keeping API keys out of your code, once for every service. On Sidechat that plumbing already exists. Your assistant asks for a tool by name, and you approve one sign-in.
- 1
Connect your AI assistant
Once your workspace has access, add Sidechat's MCP server to Claude Code, Codex, Cursor, VS Code Copilot or claude.ai, and sign in.
- 2
Describe the job
For example: every hour, post new rows from the Orders sheet to #orders in Slack. Your assistant finds the Google Sheets and Slack tools in the catalog.
- 3
Approve the sign-in
A Sidechat page names the app and what it is asking for, then opens the app's own sign-in screen. Sidechat never sees your password, and tokens are refreshed automatically.
- 4
Bring a key for everything else
No connector for a service? Store its API key with Sidechat and approve the domains it may call. Calls to any other host are refused.
- 5
Let it run
The app or scheduled Function runs on Sidechat, and each action is paid from your prepaid credits.
What can you connect today?
- Slack
One sign-in on the app's own screen
Post messages and read channels. Adding Sidechat to Slack as a bot needs your own Slack app.
- Gmail
One sign-in on the app's own screen
Read, draft and send email
- Google Sheets
One sign-in on the app's own screen
Read and append rows
- Google Calendar
One sign-in on the app's own screen
Check availability and create events
- HubSpot
One sign-in on the app's own screen
Create and update contacts and deals
- Notion
One sign-in on the app's own screen
Read and update pages and databases
- Mailchimp
One sign-in on the app's own screen
Send campaigns to an existing audience
- Any HTTP API
Your API key, stored by Sidechat
Your key, encrypted and limited to the domains you approve
What do connectors cost?
- Connected accounts$3.003 accounts / month × $1.00Sidechat rate card, as of
- Actions through connected apps$30.001,500 actions / month × $0.02Sidechat rate card, as of
- Monthly total$33.00
Assumes Slack, Google Sheets and Mailchimp connected, and about 50 actions a day for 30 days. Paid from prepaid credits; free workspaces are not charged. Model tokens, hosting and email are priced separately.
Connector questions
Which apps can I connect with one sign-in?
Slack, Gmail, Google Sheets, Google Calendar, HubSpot, Notion, Mailchimp and more than 100 others connect with a single sign-in when your AI assistant asks for them. Anything with an HTTP API works with your own key.
Can I connect a tool that isn't listed?
Yes, if it has an HTTP API. Store its API key with Sidechat and approve the domains it may call. The key is encrypted, and calls to any other host, including redirects, are refused.
Can my AI assistant or my app see my passwords and keys?
Not when you add them through Sidechat. You sign in on the app's own screen, so Sidechat never sees the password, and keys you add through Sidechat's secure prompt are encrypted with Google Cloud KMS and attached to requests on Sidechat's servers. Your assistant and your app's code only hold a reference.
What do connectors cost?
2¢ per action and $1 per connected account per month, paid from prepaid credits. Free workspaces aren't charged. Model tokens, hosting and email are priced separately.
Can I limit what I spend?
Credits are prepaid, so work stops when they run out, and you can set a monthly limit on automatic top-ups in Billing.
Can I add Sidechat to Slack as a bot?
Yes, with your own Slack app: a bot token, signing secret and app ID from Slack's app console. Using Slack as a tool, to post messages or read channels, takes one sign-in.
Keep reading
Sources
- Of more than 5,200 open-source MCP servers, about 88% require credentials, 53% rely on long-lived static API keys or tokens, and only 8.5% use OAuth. Astrix Security, State of MCP Server Security 2025, .
- The average organization runs 957 applications and has connected only 27% of them. MuleSoft 2026 Connectivity Benchmark, via CIO Dive, .
- GitGuardian found 24,008 unique secrets exposed in MCP-related configuration files on public GitHub. GitGuardian, State of Secrets Sprawl 2026, .
- Google requires verification for apps that request sensitive scopes such as full Google Sheets access; until then, an unverified app is limited to 100 new users. Google Cloud Help, Unverified apps, .
Changes to this page
- : First published.
- : Rewrote the page: how sign-in and keys work, the connector list, sources and questions.