Connect accounts

An integration connects an outside account or service to Mobius. Connect a Gmail mailbox to search and send mail, Slack to post messages, or a model provider to use your own account.

For a provider that acts through an account, connecting is only the first step. You also decide who manages the account, which assistants may use it, and who may use and retain the returned tool results inside Mobius. These choices stay separate so sharing an assistant never exposes an account by accident.

Alice and Bob both use Northwind's Scout assistant. Alice can grant Scout her own Gmail account for her Mobius conversations and routines. Bob can still use Scout, but he cannot use Alice's mailbox or see the returned tool results in Mobius. If Northwind connects a team-managed operations inbox instead, an administrator can grant Scout that exact account for work whose Mobius audience includes both Alice and Bob.

Connect an account

1. Open Build > Integrations and select Browse services.
2. Choose the provider that holds the account or data you need.
3. If a choice appears, pick who the account belongs to. For a mailbox, calendar, or drive, choose My account or Shared account. For other credentials, choose You or Your team. Some business credentials can only be managed by the team.
4. Complete the provider's sign-in, API key, app installation, or account selection flow.
5. Return to Mobius and open the account you just connected. Check the identity and Managed by value before granting access.
6. If Assistant access appears, choose Give agents access. Select the assistants and review the Mobius result audience, then save.

To connect a second account from the same provider, return to Browse services, open that provider, and start its connect flow again. The new account appears beside the first; it does not replace it. Use Reconnect on an existing account only when you mean to refresh that exact connection.

The account page now lists each assistant that can use this exact connection. Its tools have not changed, so open the assistant's Configure tab when you also need to add an action such as gmail.message.send.

You can start from an assistant instead. On its Configure tab, find Accounts, select Add account, and review an existing account or connect a new one. After a new sign-in, Mobius returns you to that assistant's access review. When you give one assistant access in that review, Mobius also gives it the provider's tools if it has none, so it can use the account from your next message.

Connect from a conversation

You can also ask the assistant in a conversation to connect a service. Its reply carries a card for the service. Select Connect and the card opens in place:

• Choose an account you already manage, or
• Connect another. API keys go straight into the card. A service that signs you in, such as Google or Microsoft, opens its sign-in in a small window that closes itself when you finish.

Either way, the assistant gets the account in the same step, with no separate review. If it has none of the provider's actions yet, it gets all of them too. That includes the actions that change things, such as sending mail, and any the provider adds later. The card then shows the service as connected, and the assistant can use it from your next message.

The card doesn't ask who manages a new account, because the assistant already says whose it is:

• On your private assistant, the account is yours.
• On a shared assistant, a company key such as SendGrid is your team's, so everyone's conversations with the assistant can use it.
• Your own mailbox or calendar stays yours even on a shared assistant, so only your conversations with it can use the account.
• A workspace such as Slack is always your team's.

If you aren't an organization admin, a new account is always yours. To connect it any other way, start from Build > Integrations.

The card stays in the conversation and lists the accounts the assistant can use. Select + beside them to add another. You can also ask for the card later, for example "show me my Gmail accounts", and the assistant draws it even when the service is already connected.

To give the assistant fewer of the provider's actions, select the action count on the card, such as 32 actions. The actions are grouped into Read and Write, so you can keep only the read actions in one click, or clear individual ones. You stay in the conversation.

Which actions an assistant has is part of the assistant, its tools. You can change them on your own private assistant. On a shared assistant, only an organization admin can. If a shared assistant doesn't have the provider's actions, the card says so instead of offering to connect, because the assistant couldn't use the account yet.

If your browser blocks the sign-in window, the card asks you to continue, and the next click opens it.

Account settings inside a conversation

Open Account settings beside the message box to inspect connected accounts or choose Connect account. A connected account card also opens settings in place. Select the provider and account you mean to edit; this does not change which account the assistant normally uses.

Account managers can change the watched Outlook mail folder or OneDrive folder path and see the saved result. These settings control notifications. Microsoft still decides which mail and files the account can access. OneDrive also reaches SharePoint libraries permitted by Microsoft, using the same account.

GitHub shows permitted repository scope and a link to manage the installed app. When repository scope is unavailable, account management does not grant access to private repository names. Slack shows workspace and app setup facts; channel access is managed in Slack. Teams shows the tenant link and how to refresh it. Changing watched Outlook calendars is not supported here.

Add Google Drive or Google Sheets files to a message

Select + under the message box, then Add from Google Drive or Add from Google Sheets. The item appears when the assistant has an account for that service. Search the files Mobius can use in the account, tick the ones you want, and select Add. Mobius checks each file through that exact account. Files that pass appear as chips beside your attachments. Your written request stays intact. Select Send when you are ready.

Google lets Mobius see only files chosen in Google or created by Mobius. If you manage the account and don't see a file, select Choose from Google to pick it in Google's own window. If someone else manages the account, ask them to make more files available. If a file fails the check, the chooser keeps it ticked with the reason so you can remove it or choose it again.

Each message can use files from one Drive account and one Sheets account. To use another account from the same service, remove the current files first. Mobius checks the assistant's exact account access and read action when you add files and again when you send. While a message is sending, its files can't change. If access changes, the draft and its files stay in place so you can repair access or remove a file. People allowed to change the assistant can use Customize actions to add its missing read action.

Team files need an existing conversation. In a new chat, the chooser asks you to send your request first; opening it does not start a conversation or send a message. References identify Google files; they do not upload copies or prove that the assistant has read them. The assistant reads through the selected account. That account stays fixed for the current reply and any resume; choose files again for a later message.

Choose who manages the account

You means the connection follows your Mobius membership. This fits a personal mailbox, calendar, or drive. You manage its lifecycle, and only your Mobius conversations and routines may use it and retain its returned tool results, even when the assistant is shared with colleagues.

Your team means organization administrators manage the connection. Use it for a shared support inbox, a company API key, or another credential whose management should stay with the organization when its creator leaves. The upstream account must still remain active. A team-managed connection can make the Mobius result audience the whole team or named people, as chosen in each assistant grant.

For a mailbox, calendar, or drive, these choices read My account and Shared account. A team member's own account is always theirs. Mobius refuses to make it team-managed, at connection time and later, because that would open their mail or files to the whole team. A shared account is one the team shares, such as support@, whose address is no member's sign-in.

Creating or administering a team connection does not let an administrator read the provider content. Account management and content access are separate.

Google Workspace service accounts and Microsoft application connections are business credentials, so Mobius always makes them team-managed. Some delegated Google and Microsoft connections can also be made team-managed later from the account page. That change keeps the account identity, assistant access, result audiences, account preferences, and routine bindings in place.

Give an assistant account access

Connecting an account does not make it available to every assistant. Its manager grants one exact account to selected assistants, with a Mobius result audience for each grant.

• A person-managed account can be used only in that person's Mobius audience, which also retains the returned tool result.
• A team-managed account can be used for the team or named active people, as selected on the grant.
• Select all current agents creates a separate grant for each assistant that exists now. Assistants created later receive no access.

The grant covers both conversations and routines. There is no separate routine access switch. A routine still saves the exact accounts it will use, which prevents a later preference from changing where unattended work runs.

Three controls must agree before an assistant can act:

Giving an assistant a Gmail tool never grants a mailbox. Granting a mailbox to one assistant from its access review adds the Gmail tools if it has none; granting from the account page leaves tools as they are.

Choose among several accounts

Mobius shows an account by its connection name and verified external identity. Give connections names people can say naturally, such as Support inbox and Alice work mail.

For personal and workspace providers, such as Gmail or Slack, an assistant can choose a named account for one call when several are eligible. If the request does not name one, open the assistant's Accounts card and select Account preferences:

• Your chats saves the account that assistant should use in your conversations.
• Channel replies saves the account for team channel work. Only an organization administrator can change this preference.

A preference chooses among accounts the assistant is already allowed to use. It does not create access. Routines keep their saved accounts and do not use either preference.

If one eligible account remains, Mobius can use it without asking. With several personal or workspace accounts and no preference or exact routine account, the assistant must choose a named account for the call.

Capability providers, such as Firecrawl and Google Places, follow a narrower rule: the assistant never chooses among keys. When several eligible keys remain, save an account preference or bind the exact key to the routine. Until then, Mobius withholds that provider's tools. It does not fall back to a team key or silently substitute another connection.

Reconnect, rename, or disconnect

Open Build > Integrations, select Connected accounts, then open the exact account.

• Change Label when people need a clearer name. The verified account identity and authority stay the same.
• Use Reconnect when consent expired, a token can no longer refresh, or the provider asks for a new sign-in.
• Use Disconnect when Mobius should stop using the account. Other accounts for the same provider stay connected.

Disconnecting removes assistant access and leaves routines that depended on the account needing repair. The confirmation names the exact account before anything is removed.

Disconnecting from Mobius does not always revoke consent at Google or Microsoft. Their family pages explain when to remove the upstream authorization too.

What a connection can add

Depending on the provider, a connection can add:

• Actions an assistant can call.
• Events that record a change and can start a routine.
• Pickers for channels, repositories, files, and other provider data.
• AI models billed through the connected account.
• Activity records for diagnosing failed calls or missing events.

Not every provider offers every capability. The provider page shows what is available and what still needs setup. Readiness is reported per connected account. It means Mobius has the configuration needed to attempt a call, not that the provider guarantees the next call will succeed.

Browse the catalog

The app catalog is the source of truth for the current organization. A deployment can enable or hide a provider, and some read-only or platform-funded providers need no customer account.

Google providers share OAuth and service-account rules. Start with Google integrations. Microsoft 365 providers share consent and disconnect behavior, with different support for personal and business accounts. Start with Microsoft integrations.

Inspect actions and events

Open a provider under Build > Integrations. Its Capabilities section lists actions and events. Expand an action when you need its parameters or behavior annotations.

Mobius's own actions, named mobius.*, appear under the built-in Mobius provider. Remote Model Context Protocol (MCP) servers live under Build > MCP servers because their tools are discovered live. Your HTTP and worker-backed actions live under Build > Custom actions.

Provider events become source events, such as:

github.pull_request.opened

Prefer an exact event name. Use a trailing wildcard such as github.* only when every matching event should start the same work.

Dispatch, review, and outbound recipients

Before a connected provider action runs, Mobius freezes the selected account and rechecks the live connection, assistant grant, and result audience. A denial stops that call and never falls through to another account.

Mobius does not automatically ask a person to confirm an external change. If a task needs judgment before it acts, instruct the assistant to open an interaction and wait. That is a deliberate, instruction-based review. The interaction does not enforce the later dispatch or prove that a particular tool call followed the decision.

A grant's result audience limits which Mobius conversation or routine audiences may use the connection and receive its returned tool result. It does not inspect or restrict an outbound email address, phone number, channel, or other destination supplied to the action. Per-delivery controller consent is not currently enforced. Use provider-side restrictions or a narrower custom action when an outbound destination needs a hard allowlist.

For MCP tools, an idempotent hint alone does not permit an automatic retry. Mobius retries only when the server positively marks the tool read-only and idempotent and does not mark it destructive.

Connect from software

Most providers use POST /v1/integrations/providers/{provider}/connect. Redirect providers return a redirect_url; inline providers return the connection. The provider page shows the request body when it has fields beyond the standard connect options, and the API reference owns the full schema.

The mobius command-line interface (CLI) can inspect action and event catalogs:

mobius catalog list-actions
mobius catalog get-action slack.message.post
mobius catalog list-events

The CLI does not connect provider accounts yet. Use the app or API.

Connect a provider outside the catalog

If a provider has an API but no Mobius integration, create a custom HTTP action. For a system that must stay inside your network, keep its credentials in your own secret manager and expose the operation through a worker. Mobius does not offer a general-purpose secrets store.

To start work from a system Mobius does not model, send an email to an assistant's address or invoke that assistant from your software. See assistant messaging.

Next

• Give an assistant a focused set of tools and skills.
• Learn what a tool call records in actions.
• Start work from an outside change with source events.
• Check exact request and response shapes in the API reference.