Beta integrations

Some integrations connect through an app that the provider — like Google — is still verifying. While that review is in progress, the service is marked Beta in Console. You can use it now — here’s what that means in general.

Outcome

Connect and use a Beta integration with confidence — knowing why it’s in beta, that it’s safe to continue, and what changes once verification finishes.

Why something is in beta

Each integration runs behind its own app registered with the provider, and that app has its own verification status. When a provider is still reviewing one of our apps, we open the integration as a Beta rather than make you wait — so your agent can start using it today. Signing in to Arc Forge itself is never affected; only the individual integration is in beta.

The screen you may see

Because the app isn’t verified yet, the provider may show a caution or extra-consent screen during connect. It can look alarming, but the path through is simple.

The exact wording and steps differ by provider. Each integration’s own page has the precise screen and which parts are in beta — see Connect Google for Google services.

Beta is a limited group

Each beta integration opens to a limited group of accounts while we watch it closely and tune it. If a beta is full, choose Notify me on that row and we’ll reach out the moment a spot opens.

What changes when it’s verified

Full provider verification is the goal. Once the provider approves our app:

• The caution screen disappears.
• The Beta tag drops away.
• Connecting becomes a plain one-tap flow.

Nothing else changes for you — the access you already granted stays exactly the same.

Support packet

If a beta connection fails, open a support ticket with:

• The agent name and the specific integration (for example, “Google Drive”).
• The status shown on the row (Beta, Connected, or an error label).