# Integrations overview

> Choose, connect, verify, and operate the provider integrations available to your Spacebrain workspace.

Canonical: https://help.spacebrain.ai/integrations/

Integrations authorize Spacebrain to read from or perform supported work in external systems. They can power Inbox channels, email, messaging, webinar sessions, payments, automation webhooks, calendars, and other workspace features.

The catalog and connection screens visible in your signed-in workspace are the source of truth. Provider availability can depend on plan, workspace type, role, geography, provider approval, environment configuration, and staged rollout.

<Callout type="info" title="A provider can be supported without being available everywhere">
  A guide describes the setup paths implemented by Spacebrain, but it does not guarantee that every provider is enabled for every workspace. A disabled button, **Coming Soon** label, **Not configured** status, missing catalog entry, or read-only screen means that the flow is not currently available to that user or environment.
</Callout>

## Provider setup guides

<Cards>
  <Card title="Gmail, SMTP, and inbound email" href="/integrations/email-gmail-smtp-and-imap" description="Connect Google with OAuth or use custom SMTP, then choose webhook, IMAP, or send-only operation." />

  <Card title="WhatsApp, Meta, and phone channels" href="/integrations/messaging-whatsapp-meta-and-phone" description="Keep WhatsApp Business, Facebook and Instagram, and Spacebrain phone numbers correctly separated." />

  <Card title="Zoom and Google Meet" href="/integrations/zoom-and-google-meet" description="Authorize webinar video providers and validate both session creation and live event delivery." />

  <Card title="Stripe and Commas" href="/integrations/stripe-and-commas" description="Prepare a payment account for paid Webinar checkouts without confusing it with workspace billing." />

  <Card title="Webhooks, Zapier, Make, and authentication" href="/integrations/webhooks-zapier-make-and-authentication" description="Understand the dynamic catalog, authentication types, webhook URL handling, and end-to-end tests." />
</Cards>

## Do not treat all connections as interchangeable

* **Email accounts** are managed in **Email → Accounts** and may use Google OAuth or custom server credentials.
* **WhatsApp Business** has its own Meta authorization and WhatsApp Business Account resources.
* **Meta Lead Ads & Messaging** connects Facebook Pages, Messenger, and linked Instagram accounts. It is separate from WhatsApp.
* **Phone Numbers** are Spacebrain-managed number resources purchased with workspace credits. They are not an OAuth connection and are not automatically WhatsApp-enabled.
* **Webinar video providers** and **Webinar payment accounts** live under Webinar settings and have readiness checks beyond authorization.
* **Zapier and Make** use a dedicated webhook setup drawer. Their URLs and event types are workspace-specific.
* Other entries in **Integrations** come from the active server-side catalog. Beta and inactive states in that catalog control what can be connected.

## Before connecting

Confirm:

* The active Spacebrain workspace or sub-account.
* The exact provider organization, tenant, page, mailbox, profile, property, or location.
* Which provider user will authorize and whether they have administrator approval.
* What data and actions the requested scope permits.
* Who owns reconnection and offboarding.
* Which live workflows will depend on the connection.
* Whether a sandbox or provider test environment is required before production.
* Whether the provider connection is distinct from an agency-owned or platform-billing account with a similar name.

## Connect a provider

1. Open **Integrations** and select the provider.
2. Read prerequisites and choose **Connect**.
3. Sign in to the intended provider account.
4. Review requested permissions rather than approving reflexively.
5. Complete all provider prompts and return to Spacebrain.
6. Select the intended resources if the provider exposes more than one.
7. Verify the displayed status and run an end-to-end test in the module that consumes the connection.

<Callout type="info" title="Connected is not the same as ready">
  Authorization can succeed before DNS, sender authentication, messaging registration, verified locations, payment onboarding, webhooks, installation, quotas, or provider review are complete.
</Callout>

## Shared connection responsibility

Use organization-controlled provider identities when possible. Record the owner and backup. Avoid connecting the same resource through multiple personal users unless the integration explicitly supports that design.

Use the provider guide for the initial setup, then follow the [connection lifecycle](/integrations/connection-lifecycle) for testing, reconnection, migration, disconnection, and incident handling.