getting started

Connect a platform to OpenbirdAI

Connect an authorised account before asking OpenFeather about private data, and verify the connection works before you rely on it.

· OpenbirdAI documentation

OpenbirdAI cannot answer questions about private platform data until the relevant account is connected and the required permissions are granted. Connections are provider-specific: connecting one service never grants access to any other.

Before you start

Check the following so you do not have to restart the flow halfway through:

  • You can sign in to the provider yourself with the account that owns the data.
  • You are allowed to grant that access on behalf of your workspace or team.
  • You are in the workspace where you want the connection to live — connections are workspace-scoped.

Run the connection flow

  1. Open the integrations area from the dashboard navigation.
  2. Find the provider and choose connect.
  3. You are redirected to the provider to authorise OpenbirdAI. Approve only the permissions you need.
  4. The provider returns you to OpenbirdAI, which stores the authorisation server-side.
  5. Confirm the account appears as connected with the correct email or workspace name.

Verify with a narrow question

Do not test with a broad question. Ask something specific and small, for example "How many files did I change in Drive in the last 7 days?" A narrow question fails fast and tells you whether the connection actually reads data.

  • A specific answer with sources means the connection works.
  • An empty answer usually means the wrong account, an excluded date range, or a missing permission.
  • A permission error usually means the authorisation was granted but a required scope was declined.

Common mistakes

  • Connecting the account to the wrong workspace, then wondering why teammates cannot see the data.
  • Granting access to a personal account when the business data lives in a team account.
  • Assuming a connection covers every service in a suite — Google, for example, exposes a defined set of services, each with its own availability.
  • Revoking access from the provider settings and expecting the OpenbirdAI connection to update automatically.

Disconnecting safely

Disconnecting from OpenbirdAI removes the stored authorisation immediately. OpenFeather stops being able to read that source. For a full revocation, also remove OpenbirdAI from the provider's own account settings.

Never paste access tokens, client secrets or passwords into Ask, chat or support messages. Support never needs them.

Common questions

Does OpenbirdAI store my provider password?

No. Authorisation happens on the provider's site and OpenbirdAI stores the resulting token server-side, encrypted.

Why can my teammate not see data from my connection?

Connections are workspace-scoped. The person must be in the same workspace and the request must run in that workspace context.

Was this page helpful?