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 it opens the Connectors page in the sidebar — the same page you get by clicking that sidebar entry.
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, Granola |
| Sales and support | Stripe, Salesforce, HubSpot, Calendly, Airtable, ClickUp, Supabase, Apollo |
| Social and publishing | X, LinkedIn, Reddit, Instagram, Facebook, WhatsApp, Discord, Twitch, Pinterest |
| Web data and tooling | Firecrawl, Exa, Tavily, PostHog, 1Password |
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.
What the social connectors cover
The social connectors do less than the apps they talk to, because of what each provider lets an app do. AdaL knows these limits before it calls anything: ask for something outside them and it says so and offers to use the browser instead, signed in as you. It asks before any post, message or follow.
| Service | It can | It cannot |
|---|---|---|
| Post as you (text, image, video, article, reshare, draft), comment, delete your own posts, read your own profile | Company pages, reading posts, reactions or the feed, search, messages, connections, editing a post | |
| X | Post, reply, quote, poll, media, delete, like, repost, bookmark, follow, mute, DMs, lists, timeline, mentions, search | Editing or scheduling posts, post analytics, blocking |
| Browse and search subreddits, posts and comments; post, comment, edit, delete, vote; rules and flair; your mod queue | Inbox and private messages, a user's comment history, wikis, joining subreddits, saved posts | |
| Business and Creator accounts only: publish photos, videos, Reels and carousels; comments, mentions, tags, current stories, insights; DMs within 24 hours of the person's last message | Personal accounts, other people's posts, hashtag search, likes, follows, the feed, scheduling | |
| Pages you manage only: post, schedule, edit and delete text, photos and video; comments, reactions, Page insights, Messenger as the Page | Your personal profile, Groups, friends, ads | |
| WhatsApp Business only: send text, media, locations, contacts and buttons; free-form within 24 hours of the customer's last message, templates after that | Personal WhatsApp, reading incoming messages | |
| Discord | Your profile, your server list, your membership in a server, linked accounts | Reading or sending channel messages and DMs, managing servers |
| YouTube | Search, video and channel details, comments, playlists, subscriptions, upload, captions of your own videos, your channel's analytics, live broadcasts | Community posts, captions of other people's videos |
| Boards and pins, analytics, trends, search your own pins | Creating a pin is untested and may be refused |
Reads on X cost API credits, so AdaL keeps them few. For "what are people saying about X", it uses social listening rather than a connector.
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 |
| Your WhatsApp Business Account ID |
Services that use your own API key
Firecrawl, Exa, Tavily, Apollo, PostHog and 1Password have no sign-in flow. The page that opens asks you to paste a key instead of granting consent:
| Service | What you paste |
|---|---|
| Firecrawl, Exa, Tavily, Apollo | Your API key for that service |
| PostHog | A personal API key (phx_…) and your region |
| 1Password | A service account token |
The key goes to that page, not to AdaL. Everything after that is the same: the account appears in the list when the key is accepted, and you disconnect it the same way.
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, username, login name or workspace name, or Account 1: Oct 8 when the provider gives none of those.
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 on each service card: Connect on a service with no account, Add account on one that already has one, Reconnect on an account that needs authorizing again, and Disconnect per account. Tooltips name the account you are acting on.
The cards are split into two views. Yours lists the services you have an account on, with the number of accounts next to the name; Discover lists the services you have not connected. Yours opens first when you have at least one account, otherwise Discover does. The search box searches both views at once, and choosing a view clears the search. On Desktop the panel also closes on Esc or a click outside it.
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.
Slack messages carry a footer
Every Slack message the agent sends, schedules or edits for you ends with a small line: Sent using AdaL. Link previews are turned off on those messages. Ask the agent to leave the footer out, or to keep link previews on, and it will.
Nothing rewrites your message after the fact. AdaL hands the agent that instruction while it reads the Slack actions, and the agent builds the footer itself. This works the same in the CLI, Desktop, the SDK and cloud agents.
Related: MCP Servers · Slash Commands · Built-in Tools