integrations

Connect an account

Complete an OAuth connection for a provider, confirm the authorised account and services, and reconnect safely when authorisation expires.

Last verified 13 October 2026 · OpenbirdAI documentation

Connecting an account is a provider-side authorisation. OpenbirdAI never sees your password: it sends you to the provider, you approve a request, and the provider returns a token that OpenbirdAI stores encrypted on the server.

The connection flow

Open the integrations area and choose the provider.
Select connect. OpenbirdAI redirects you to the provider.
Sign in to the provider if required and review the requested permissions.
Approve. You are returned to OpenbirdAI.
Confirm the connected account label — usually an email or workspace name — is correct.

Confirming it actually works

A connected badge only proves an authorisation exists. To prove data flows, run a narrow question:

"List the five most recently modified files in Drive."
"What are my next three calendar events?"
"Show my three most recent orders."

If the status shows connected but a question returns nothing, the authorisation exists but the requested service or scope is missing. Reconnect and approve all scopes.

Reconnecting

Provider authorisations expire or get revoked. Reconnecting uses the same flow; OpenbirdAI replaces the stored authorisation atomically so there is no window where a partially valid token is used.

Connection shows expired or invalid → reconnect from the integrations area.
Connection shows connected but requests fail with permission errors → reconnect and approve the missing scopes.
You revoked access from the provider settings → reconnect, and re-approve from the provider side too.

Disconnecting

Disconnect removes the stored authorisation from OpenbirdAI immediately. OpenFeather can no longer read that source. To fully revoke, also remove OpenbirdAI from the provider's own account settings — OpenbirdAI cannot revoke access it does not hold.

Disconnecting does not delete the data already stored in your conversations. Delete the relevant conversations if that is your intent.

Managing several connections

When you connect more than one account of the same provider, answers become ambiguous unless you say which one you mean. Check the connected account label on each card and name it in the question.

Keep one connection per provider per workspace wherever possible.
Use separate workspaces when you genuinely need two accounts of the same provider.
Disconnect the one you are not using instead of leaving both active.

A connection that is not the one you meant is the most common cause of "the data looks wrong" rather than "there is no data".

Common questions

Why does the provider ask for permissions I do not use?

Providers request a fixed scope set per app. Decline the whole request if it does not meet your policy, rather than approving partially and being surprised later.

Can I connect two accounts for the same provider?

Connections are per workspace and per provider account. Switch or disconnect before connecting a different account so answers are unambiguous.