Connect your apps
Connectors let AdaL work with accounts you already have: read and send mail in Gmail, edit a Google Sheet, post in Slack, open a Linear issue, look up a Stripe customer. You authorize each account once in the browser, and the connection stays attached to your AdaL login.
Connectors are new. Every action that changes something — sending mail, uploading a file, creating an issue — asks for your approval first.
Open the Connectors panel
/connector
/connector works in the CLI and in AdaL Desktop. On Desktop you can also click Connectors in the sidebar.
You need to be signed in to AdaL. The connection list is per AdaL account, so the same accounts show up on every surface you sign in from.
Which services are available
The list is served by AdaL's backend, not built into the app, so new connectors appear without an update. The services shipped so far:
| Group | Services |
|---|---|
| Gmail, Google Drive, Calendar, Sheets, Docs, Slides, Tasks, Meet, Photos, Analytics, Search Console, BigQuery, Classroom, Maps, YouTube, Google Ads, NotebookLM Enterprise | |
| Work and chat | Slack, Notion, GitHub, Linear, Asana, Outlook, Dropbox, Jira, Confluence |
| Sales and support | Stripe, Salesforce, HubSpot, Calendly, Airtable, ClickUp, Supabase |
Google (All Services) is one sign-in that covers Gmail, Drive, Docs, Sheets, Slides, Calendar, Tasks, Photos, Analytics and Google Ads at once. It asks for all of their permissions in one consent screen.
A service shown as Not configured on this server is not enabled on the backend you are signed in to. Rollout is per server, so a connector in the table above may not be live for you yet.
Connect an account
- Select the service and press
Enter(on web and Desktop, click the add button next to the service). - Your browser opens the provider's authorization page. Grant the permissions it asks for.
- AdaL checks the result on its own and shows the account when authorization finishes. Nothing to paste back.
Each connector requests every permission its service offers, so you do not have to reconnect later for a different task.
A few services ask for one value on the authorization page before the provider's sign-in:
| Service | What it asks for |
|---|---|
| Google Ads | Your Google Ads customer ID |
| Jira, Confluence | Your site name — the part before .atlassian.net |
| Salesforce | Login settings; most people keep the defaults shown |
| Supabase | The API address; keep the default unless you self-host |
| NotebookLM Enterprise | Your Google Cloud project ID |
Authorization stops waiting after five minutes. Start again with Connect if it times out. An attempt you never finish — a closed tab, a declined consent screen — is deleted ten minutes later, and the agent never sees it.
You can connect several accounts to the same service. Each row shows a label AdaL can read: the account's email or workspace name, or Account 1: Oct 8 when the provider gives neither.
Account status
| Status | Meaning |
|---|---|
| Connected | Ready to use |
| Waiting for authorization | The browser step is not finished yet |
| Reconnect required | The authorization expired |
| Authorization failed | The provider rejected the attempt |
| Disconnected | The connection was removed |
AdaL does not compare the permissions you granted against the ones it asked for — no provider reports that reliably. A permission you declined shows up as an error on the action that needs it, and the agent will tell you to reconnect.
Keys in the CLI panel
| Key | Action |
|---|---|
↑ / ↓ | Move between services and accounts |
Enter on a service | Start a new connection |
Enter on an account that needs reauthorization | Reconnect it |
d | Disconnect the selected account |
r | Refresh the list |
n while waiting | Stop waiting for authorization |
Esc | Close the panel |
Enter on an account that is already connected does nothing, so you cannot create a duplicate connection by accident. d disconnects straight away — the row leaving the list is the confirmation.
On web and Desktop the same actions are buttons: an add button per service, a refresh button, and a red ✕ per account. The footer and tooltips name the account you are acting on.
Disconnect an account
Disconnecting removes that one connection from AdaL. It does not revoke the provider's authorization, because that grant is shared — revoking it would break your other connections to the same provider. To withdraw access on Google's side, remove AdaL from your Google account permissions; other providers have the equivalent page in their own account settings.
What the agent can do
Two tools are always available to the agent once an account is connected:
connector_discover— lists your connected accounts, the actions each service offers, and the input schema of one action. Read-only, no approval.connector_execute— runs one action on one account you chose. Always asks for approval first.
The action list comes from the provider, not from a fixed list inside AdaL, so everything the service exposes for your account is reachable. Ask in plain language:
Summarize the unread mail in my work inbox from this week
Find the Q3 planning doc in my Drive and list its headings
Post the release notes in #launches and open a Linear issue for anything still open
Treat anything the agent reads from mail, files or messages as data, not as instructions.
Related: MCP Servers · Slash Commands · Built-in Tools