Connections and data

Manage which apps Otto can use

Keep connected apps limited to the accounts and workflows your agents actually need. From Settings > Integrations, you can review connected accounts, add a second account when the provider supports it, reconnect an app, or disconnect it entirely.

What connecting an app controls

Connecting an app gives Otto a credential it can use for that app. It does not mean an agent should perform every available action without supervision:

  • The connected account determines which mailbox, repository, calendar, or other external data the app can reach.
  • The app's available actions determine what an agent can do with that connection.
  • Approvals & safety determines when Otto asks you before an action with external consequences, such as sending, publishing, purchasing, deleting, or changing a record.

Use Approvals and safety controls to choose how closely to supervise actions. Disconnecting an app is the way to remove Otto's access; changing approval settings is not a replacement for removing a connection.

Review connected apps

  1. Open Settings.
  2. Select Integrations.
  3. Review the app cards under your connected apps. Each card identifies the provider and, when the provider supports it, the connected account.
  4. Open the app's details when you need to confirm what the connection is for before assigning work to an agent.

If an app is not listed, it is not connected on this Otto. Follow Connect an app before asking an agent to use it.

Add another account

Some providers support more than one connected account. If the app shows Add another account, select it and complete the provider's sign-in flow. The new account appears as a separate connection, so you can tell an agent which account to use.

If Add another account is not available, that provider supports one connection here. Connecting it again may reconnect or replace the existing credential rather than create a second account. Do not disconnect a working account unless you are ready to connect the account you want to use instead.

Reconnect an app

Reconnect when the provider reports an expired or invalid connection, or when you intentionally want to authorize a different account:

  1. Go to Settings > Integrations.
  2. Select the affected app.
  3. Choose Reconnect when it is shown.
  4. Finish the provider's sign-in or authorization steps.
  5. Return to the integration list and confirm that the app is connected before retrying the agent's task.

For some apps, Otto completes the connection immediately; others open a provider sign-in page or show a short code. Follow the instructions shown in Otto rather than sharing a password or authorization code in a chat.

Disconnect an app

  1. Open Settings > Integrations.
  2. Select the app and choose Disconnect.
  3. Confirm the removal.

After disconnecting, agents can no longer use that app through Otto. Existing conversation history, instructions, or files are not automatically removed; remove sensitive context separately if it is no longer appropriate. A running or scheduled task that still expects the app may fail or ask you to reconnect it.

Use the smallest useful boundary

  • Connect only the account needed for the job.
  • Keep a separate agent or workflow for work that needs a different account or sensitivity level.
  • Start new integrations with Ask to change or Always ask approvals.
  • For a recurring report, keep the connection and workflow read-oriented; add change-making actions only after you have reviewed the result.
  • Disconnect the app when a project ends, an account changes hands, or the agent no longer needs it.

An automation's access and limits are configured separately. See Set automation permissions and limits when a scheduled run needs an app.

If an app still cannot be used

  • The app is missing: connect it from Settings > Integrations.
  • The account is wrong: use Add another account if available, or disconnect and reconnect with the intended account.
  • The app says it needs authorization again: use Reconnect, then retry the task.
  • The agent asks for approval: review the requested action and your Approvals & safety setting; connection and approval are separate controls.
  • A scheduled run fails after you changed access: inspect the run and either reconnect the app or update the automation's permissions.

See Read and recover failed runs and Troubleshooting for broader recovery steps.

Related guides