Integrations

Zimmer integrates with external services to sync knowledge, push data, deploy to channels, and trigger automation. Access integrations from Connections in the left nav.

Knowledge sources

Sync external content into your Knowledge Bases automatically.

Data sources

Bring structured product and catalog data into your agents.

Marketing & ads

Connect paid media platforms to sync campaign structure and performance data.

Channels

Deploy your agent to additional messaging platforms.

Calendar & booking

Analytics & events

Connecting an integration

1. Go to Connections in the left nav
2. Find the integration and click Connect
3. For OAuth integrations: complete the authorization flow
4. For API key integrations: enter your credentials
5. Once connected, the integration appears in the Connected section

Syncing knowledge sources

Knowledge integrations (Google Drive, Instagram, Facebook, Notion) sync content into your Knowledge Bases:

• Initial sync runs automatically on connect
• Daily sync keeps content up to date
• Manual sync available via the "Sync Now" button
• Synced content is chunked and embedded for semantic search (RAG)

CRM

Push conversation data and leads into your CRM.

HubSpot setup

1. Go to Connections and click Connect on HubSpot
2. Complete the OAuth flow — grant access to contacts, companies, deals, and notes
3. Once connected, Zimmer can push leads captured during conversations as HubSpot contacts
4. Notes from conversations are attached to the contact record
5. Deals can be created or updated based on conversation outcomes
6. Pipeline selection is available when configuring lead push rules

Meta Ads — deep dive

Meta Ads is a full bidirectional integration: Zimmer reads campaign structure and performance data, and Action agents can write changes back (pause, resume, adjust budgets).

Connecting

1. Go to Connections and click Connect on Meta Ads
2. Complete the Meta OAuth flow — grant access to your ad accounts
3. Select which ad accounts to sync (you can connect multiple accounts)

What syncs

Zimmer pulls the full campaign hierarchy and stores it in Data Tables:

• Ad accounts — account name, currency, timezone, status, credit limit
• Campaigns — name, objective, status, daily/lifetime budget, bid strategy
• Ad sets — targeting, placement, schedule, budget, optimization goal
• Ads — creative, status, preview URL
• Performance metrics — impressions, clicks, spend, conversions, CPA, ROAS, CTR, CPM (broken down by date)

Synced data is available to both Knowledge agents (for answering questions about campaigns) and Action agents (for optimization decisions).

Using with Action agents

Action agents with a Meta Ads connection can read campaign data and propose/execute changes. See Action Agents for details on optimizer profiles, budget control, and approval modes.

Google Ads — deep dive

Google Ads connects through OAuth and uses GAQL (Google Ads Query Language) internally to pull data.

Connecting

1. Go to Connections and click Connect on Google Ads
2. Complete the Google OAuth flow
3. If you use a Manager (MCC) account, Zimmer detects the account hierarchy and lets you select child accounts to sync

Requirements

• A Google Ads developer token is required (GOOGLE_ADS_DEVELOPER_TOKEN environment variable)
• For MCC setups, optionally set GOOGLE_ADS_LOGIN_CUSTOMER_ID to specify the manager account

What syncs

• Account hierarchy — MCC parent/child relationships
• Campaigns — name, type (Search, Display, PMax, Video, Demand Gen), status, budget, bidding strategy
• Ad groups — name, status, targeting settings
• Ads — responsive search ads, display ads, video ads with asset details
• Keywords — keyword text, match type, bid, quality score
• Performance metrics — impressions, clicks, conversions, cost, CPA, ROAS, CTR (by date)

Using with Action agents

Action agents with a Google Ads connection support family-specific optimization. See Action Agents for details on Google Ads optimizer families, bidding controls, and recommendation policies.

Ad platform setup

• Meta Ads requires META_APP_ID and META_APP_SECRET environment variables.
• Google Ads requires GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, and GOOGLE_ADS_DEVELOPER_TOKEN. For MCC accounts, optionally set GOOGLE_ADS_LOGIN_CUSTOMER_ID.
• TikTok Ads requires TIKTOK_APP_ID and TIKTOK_APP_SECRET.
• Display & Video 360 reuses GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET. Enable both the Display & Video 360 API and the Bid Manager API in your Google Cloud project.
• DV360 reporting is asynchronous. The first sync may show a pending status while the report builds. The next sync picks it up automatically.

End-to-end flow

The typical setup flow for any integration:

1. Connect — Go to Connections, click Connect, complete auth
2. Select accounts — For multi-account platforms (Meta, Google, TikTok), choose which accounts to sync
3. Sync — Initial sync runs automatically; data appears in Data Tables
4. Use — Link the integration to agents, or create Action agents that operate on the synced data

Scheduled syncs

• Integration syncs run on schedule via POST /api/cron/sync-integrations.
• Protect that endpoint with CRON_SECRET and send Authorization: Bearer $CRON_SECRET.
• When apps/ws-server is running, DV360 pending reports are picked up automatically by the background worker.
• Manual sync is always available via the Sync Now button on any connected integration.

Linking integrations to agents

Some integrations can be enabled per-agent:

1. Open the agent detail page
2. Go to the Integrations section (Knowledge agents) or Configure tab (Action agents)
3. Toggle integrations on/off for that specific agent

Action agents created from starter kits automatically bind to the integration selected during setup.