Skip to main content
cesteralDocs
FAQContact

Connections

Connect ad platforms and external services via OAuth

Last updated 8 Oct 2026Configure · article 1 of 5

Connections link Cesteral Intelligence to your external platforms — ad networks, channels, and data sources. The AI assistant and automations use these connections to read campaign state and execute governed actions.

Open Integrations in the sidebar (under Workspace), or go to /workspace/integrations.

The Integrations Page

Connections are shown as cards, grouped under three tabs:

TabWhat it holds
AllEvery connection, across both kinds
ChannelsOAuth-authenticated channel integrations
PlatformsAd-platform MCP connections that expose governed tools

Each platform connection card shows:

  • Name and an optional slug subtitle
  • Status badge — active, inactive, error, or pending
  • Tool count — how many governed tools the connection exposes (flagged stale if the cached tool list is older than 24 hours)
  • A credential warning with a Fix credentials link when credentials are expired or invalid

The OAuth bridge that authenticates a connection works end-to-end, but the platform-execution stages built on top of it (tool sync, dry-run, execute) are connector-gated and not live by default. Until your operators point the platform at deployed connector URLs (via the MCP_SERVER_URL_OVERRIDES configuration), those stages won't run. A connection can be authenticated and healthy while platform execution is still unavailable.

Connecting a Platform

  1. Open the Platforms tab and choose a platform template (e.g., Google Ads, Meta)
  2. Complete the OAuth authorization flow
  3. The connection appears as a card with status active

Connections use OAuth — your credentials are never exposed in the app. The platform issues a token that Cesteral stores encrypted and uses to act on your behalf within the scopes you granted.

Connection and Credential Status

A connection has two related signals: an overall status and a credential status.

StatusWhat it meansWhat to do
activeConnected and workingNothing
pendingSetup is not yet completeFinish the connection flow
inactiveDisabled or not in useRe-enable if you need it
errorConnection failedTest the connection or fix credentials

When credentials are expired or invalid, the card surfaces a Fix credentials link that takes you to the connection's settings to re-authenticate.

Maintaining a Connection

Each platform connection card has an actions menu with:

  • View — open the connection detail and settings
  • Test — validate the connection against the upstream platform
  • Refresh — re-sync the connection's cached tool list
  • Fix credentials — re-authenticate when credentials are expired or invalid
  • Delete — remove the connection

Channel integrations (on the Channels tab) re-authenticate through an OAuth Reconnect flow rather than a credential edit.

Removing a Connection

  1. Open the connection card's actions menu
  2. Select Delete
  3. Confirm the removal

Removing a connection does not delete historical data — it only prevents future actions through that platform. Automations that depend on the connection will fail until it is reconnected or replaced.

Connection Health

Connection cards surface credential and error state inline. Connection health signals also appear in the platform's activity and monitoring surfaces, so an unhealthy integration is visible beyond the Integrations page itself.

Related articles

Still stuck? Browse the FAQ or contact us.