Step-by-step setup guides for every Reeve connector — where to find API keys, how to authenticate, and what data you get.

Connectors

Connectors link external platforms to Reeve. Once connected, data flows into your Dashboard, agents can interact with the platform via tools, and analytics populate automatically.

Navigate to: /cockpit/connectors

The connectors page shows all available integrations organized by category. Each card shows its connection status. Click Connect to begin setup, or Disconnect to remove.

How Connection Works

Reeve uses two authentication methods depending on the platform:

Method	How It Works	Platforms
OAuth	Click Connect → redirected to platform → authorize → redirected back	Meta, Google Ads, TikTok, Shopify, Stripe, Slack, GitHub
API Key	Click Connect → modal opens → paste your key → validated → saved	PostHog, Klaviyo, Vercel, Railway, Figma, Gorgias, Zendesk

All credentials are encrypted with the TokenVault before storage. OAuth state tokens have a 10-minute TTL for CSRF protection. API keys are validated against the real API before being saved — if the key is invalid, you'll see an error immediately.

In multi-brand mode, credentials are scoped per product so each brand can have its own connections.

Advertising

Meta Ads 📘

Connect your Facebook & Instagram ad accounts to pull campaign data, spend, ROAS, and audience insights.

Auth type: OAuth (browser redirect)

What you get: Campaign performance, ad spend, ROAS, audience demographics, creative performance

Go to Connectors

Navigate to /cockpit/connectors and find Meta Ads under the Advertising category. Click Connect.

Authorize on Facebook

You'll be redirected to Facebook's authorization page. Log in with the Facebook account that has access to your ad accounts. Approve the requested permissions:

ads_management — Read your ad campaigns and performance
pages_read_engagement — Read page data linked to ads

Select Ad Accounts

After authorization, Reeve exchanges the short-lived token for a long-lived token (60 days) and fetches all accessible ad accounts. You're redirected back to the Cockpit with Meta showing as Connected.

After connecting: Ad data appears in the Dashboard's advertising panel. Your agents can use the reeve_ads tool to pull performance data, generate creatives, and analyze campaigns.

Meta long-lived tokens last ~60 days. Reeve handles refresh automatically. If you see a disconnected state, click Connect again to re-authorize.

Google Ads 🔍

Connect your Google Ads account for search and display campaign data.

Auth type: OAuth (browser redirect)

Status: Coming soon in the Cockpit UI (backend ready)

What you get: Campaign performance, keywords, ad groups, quality scores, conversion data

Go to Connectors

Navigate to /cockpit/connectors and find Google Ads. Click Connect.

Authorize on Google

You'll be redirected to Google's OAuth consent screen. Sign in with the Google account linked to your Google Ads account. Approve access.

Account Discovery

Reeve exchanges the authorization code for access + refresh tokens, then discovers all accessible customer accounts (Manager/MCC accounts and individual accounts). You're redirected back with Google Ads showing as Connected.

If you don't receive a refresh token, you may need to revoke Reeve's access in your Google Account settings and reconnect. Google only issues refresh tokens on the first authorization.

TikTok Ads 🎵

Connect your TikTok for Business account for short-form video campaign data.

Auth type: OAuth (browser redirect)

Status: Coming soon in the Cockpit UI (backend ready)

What you get: Campaign data, creative performance, advertiser account details

Go to Connectors

Navigate to /cockpit/connectors and find TikTok Ads. Click Connect.

Authorize on TikTok

You'll be redirected to TikTok's authorization page. Sign in with your TikTok for Business account and approve access.

Note: TikTok sends an auth_code parameter (not code) in the callback.

Advertiser Discovery

Reeve fetches your advertiser account IDs and details. You're redirected back with TikTok Ads showing as Connected.

Commerce

Shopify 🛍️

Connect your Shopify store for products, orders, customers, and analytics.

Auth type: OAuth with store domain input

What you get: Products, orders, customer data, sales analytics, inventory

Shopify has a unique flow — before the OAuth redirect, you need to enter your store domain.

Go to Connectors

Navigate to /cockpit/connectors and find Shopify. Click Connect.

Enter Your Store Domain

A modal opens asking for your Shopify store domain:

┌─────────────────────────────────────┐
│ Connect Shopify Store               │
│                                     │
│ Shop domain                         │
│ ┌─────────────────────────────┐     │
│ │ mystore.myshopify.com       │     │
│ └─────────────────────────────┘     │
│                                     │
│ Enter your *.myshopify.com domain   │
│                                     │
│         [Cancel]  [Connect →]       │
└─────────────────────────────────────┘

Enter your .myshopify.com domain (e.g., mystore.myshopify.com).

Authorize on Shopify

You're redirected to Shopify's authorization page for your store. Review the permissions and click Install app.

The callback includes HMAC signature verification — Shopify signs the callback URL and Reeve verifies the signature to prevent tampering.

Connected

After authorization, you're redirected back with Shopify showing as Connected. Your store data starts syncing immediately.

After connecting: Use the reeve_shopify tool for store analytics, or view data in the Dashboard's commerce panel.

Payments

Stripe 💳

Connect Stripe for revenue analytics, subscription metrics, MRR, LTV, and churn data.

Auth type: OAuth (Stripe Connect)

What you get: Revenue, MRR, LTV, churn rate, subscription metrics, customer count, payment history

Go to Connectors

Navigate to /cockpit/connectors and find Stripe. Click Connect.

Authorize on Stripe

You'll be redirected to Stripe's authorization page (Stripe Connect flow). Sign in with your Stripe account and authorize Reeve to read your account data.

Connected

Reeve receives your access token, Stripe user ID, and live/test mode indicator. You're redirected back with Stripe showing as Connected.

After connecting: Revenue data appears in the Dashboard. Your agents can use the reeve_revenue tool to pull MRR, LTV, subscription metrics, and more.

On disconnect, Reeve calls Stripe's deauthorize endpoint to revoke access. Your Stripe data is not stored — it's fetched live when requested.

Analytics

PostHog 🦔

Connect PostHog for product analytics, funnels, feature flags, and user behavior data.

Auth type: API Key (modal)

What you get: Page views, sessions, funnels, top pages, user behavior, feature flag data

Get Your PostHog API Key

Log in to PostHog
Click the gear icon (Project Settings) in the left sidebar
Scroll to Project API Key
Copy the key — it starts with phx_

You also need your Project ID:

In Project Settings, look at the URL: https://app.posthog.com/project/{PROJECT_ID}/settings
Or find it listed as "Project ID" on the settings page

Enter Credentials in Reeve

Click Connect on the PostHog card. A modal opens with three fields:

Field	Value	Example
API Key	Your project API key	`phx_1a2b3c4d5e6f...`
Project ID	Numeric project ID	`12345`
Host	PostHog instance URL (optional)	`https://app.posthog.com`

The Host field defaults to https://app.posthog.com. Only change it if you self-host PostHog.

Validate & Save

Click Test to validate your credentials against the PostHog API. If valid, click Connect to save. The key is encrypted and stored.

After connecting: Use the reeve_analytics tool for web analytics, or view data in the Dashboard's analytics panel.

Google Analytics 📊

Connect GA4 for website traffic data, top pages, and conversion metrics.

Auth type: Service Account JSON + Property ID

Status: Coming soon in the Cockpit UI (backend ready)

What you get: Sessions, page views, bounce rate, top pages, traffic sources, conversions

Create a Service Account

Go to the Google Cloud Console
Select your project (or create one)
Navigate to IAM & Admin → Service Accounts
Click Create Service Account
Name it (e.g., "Reeve Analytics Reader")
Grant the role Viewer (or Analytics Viewer if available)
Click Done

Generate a JSON Key

Click on the service account you just created
Go to the Keys tab
Click Add Key → Create new key
Select JSON format
Download the JSON file

Add the Service Account to GA4

Go to Google Analytics
Navigate to Admin → Property → Property Access Management
Click the + button to add a user
Enter the service account email (e.g., reeve@your-project.iam.gserviceaccount.com)
Set role to Viewer
Click Add

Get Your GA4 Property ID

In Google Analytics, go to Admin → Property Settings
Copy the Property ID (a number like 123456789)

Enter in Reeve

Provide the service account JSON and property ID when connecting.

Marketing

Klaviyo 📧

Connect Klaviyo for email and SMS marketing automation data.

Auth type: API Key (modal)

What you get: Email campaigns, flows, segments, open/click rates, SMS campaigns, revenue from email

Get Your Klaviyo Private API Key

Log in to Klaviyo
Click your organization name in the bottom-left
Go to Settings → API Keys
Click Create Private API Key
Name it (e.g., "Reeve Integration")
Set permissions: Read-only access is sufficient for analytics
Copy the key — it starts with pk_

Enter the Key in Reeve

Click Connect on the Klaviyo card. A modal opens with one field:

Field	Value	Example
Private API Key	Your Klaviyo private key	`pk_abc123def456...`

Save

The key is validated and stored encrypted. Klaviyo shows as Connected.

After connecting: Use the reeve_email tool for campaign management, or view email metrics in the Dashboard.

Communication

Slack 💬

Connect Slack to receive agent notifications and interact via Slack channels.

Auth type: OAuth (Slack App)

What you get: Bot access to channels, ability to send/receive messages, workspace mapping

Go to Connectors

Navigate to /cockpit/connectors and find Slack. Click Connect.

Authorize in Slack

You'll be redirected to Slack's OAuth page. Select your workspace and authorize the Reeve bot. Permissions include:

Posting messages
Reading channel messages (where the bot is invited)
Reacting to messages

Connected

Reeve saves the bot token and workspace mapping (team ID → user ID). Slack shows as Connected with your workspace name.

After connecting: Add the Reeve bot to channels where you want agents to respond. See the Slack channel docs for configuration.

Reeve uses Slack's HTTP Events API (not Socket Mode) for App Directory compatibility. Events are verified using HMAC-SHA256 request signing.

Customer Support

Gorgias 🎧

Connect Gorgias for e-commerce customer support ticket data.

Auth type: API Key (modal with 3 fields)

What you get: Support tickets, response times, customer satisfaction, AI triage data

Get Your Gorgias API Credentials

Log in to your Gorgias helpdesk
Go to Settings → REST API (under Integrations)
Find the HTTP Basic Auth section
Note your:
- Domain: Your Gorgias URL (e.g., mystore.gorgias.com)
- Email: The admin email address
- API Key: The API key shown on this page

Enter Credentials in Reeve

Click Connect on the Gorgias card. A modal opens with three fields:

Field	Value	Example
Domain	Your Gorgias domain	`mystore.gorgias.com`
Email	Admin email	`admin@mystore.com`
API Key	Your Gorgias API key	`abc123def456...`

Test & Save

Click Test to validate your credentials — Reeve creates a temporary connection and tests it against the Gorgias API. If the test passes, the credentials are saved. If it fails, the temporary connection is cleaned up automatically.

After connecting: Support data appears in the Dashboard. Use the reeve_support tool for ticket management.

Zendesk 🎫

Connect Zendesk for enterprise support ticket and agent performance data.

Auth type: API Key (modal with 3 fields)

What you get: Tickets, agent performance, response times, CSAT scores

Get Your Zendesk API Token

Log in to Zendesk as an admin
Go to Admin Center (gear icon in the sidebar)
Navigate to Apps and integrations → APIs → Zendesk API
Make sure Token Access is enabled
Click Add API Token
Give it a description (e.g., "Reeve Integration")
Copy the token immediately — it won't be shown again
Note your:
- Subdomain: The part before .zendesk.com in your URL (e.g., mycompany)
- Email: Your admin email address

Enter Credentials in Reeve

Click Connect on the Zendesk card. A modal opens with three fields:

Field	Value	Example
Subdomain	Your Zendesk subdomain	`mycompany`
Email	Admin email	`admin@mycompany.com`
API Token	The token you just created	`abc123def456...`

Test & Save

Click Test to validate your credentials against the Zendesk API. If valid, click Connect to save.

Zendesk uses email/token authentication (not OAuth). The API token acts as the password with the format {email}/token:{api_token} for Basic Auth.

Development & Deployment

GitHub 🐙

Connect GitHub for repository access, deployments, and CI/CD integration.

Auth type: OAuth or GitHub App installation

What you get: Repository access, deployment status, CI/CD triggers, code context for agents

GitHub supports two connection methods — choose based on your needs:

OAuth gives your personal account access to repos. Good for individual developers.

Click Connect

Navigate to /cockpit/connectors and click Connect on the GitHub card.

Authorize on GitHub

You'll be redirected to GitHub's OAuth page. Review the requested permissions:

repo — Full control of private repositories (read/write)
read:user — Read your user profile

Click Authorize to approve.

Connected

Reeve stores the access token (encrypted) along with your GitHub username and user ID. You're redirected back with GitHub showing as Connected.

The OAuth token is stored with format validation — GitHub tokens must be 40+ characters and start with ghp_, gho_, ghu_, ghs_, or ghr_.

The GitHub App provides granular, per-repository permissions and works with organizations. Recommended for teams.

Install the GitHub App

Navigate to /cockpit/connectors, click Connect on GitHub, and choose Install GitHub App. You'll be redirected to:

https://github.com/apps/reeve-code/installations/new

Select Repositories

Choose which repositories the Reeve GitHub App can access:

All repositories — Access to every repo in your account/org
Only select repositories — Pick specific repos

Click Install.

Connected

GitHub redirects back with the installation_id. Reeve stores the installation ID and uses it to generate short-lived installation tokens for API access. These tokens auto-expire and are more secure than long-lived OAuth tokens.

After connecting: The gateway injects GH_TOKEN into agent environments. Agents can clone repos, create PRs, and interact with GitHub. The reeve agents doctor command checks GitHub connectivity.

Vercel ▲

Connect Vercel for frontend deployment status, domains, and build logs.

Auth type: API Key (modal)

What you get: Deployment status, domains, build logs, project list

Get Your Vercel Access Token

Go to vercel.com/account/tokens
Click Create Token
Give it a name (e.g., "Reeve Integration")
Set scope to your personal account or team
Set expiration (or "No Expiration" for convenience)
Click Create Token
Copy the token immediately — it won't be shown again

Enter the Token in Reeve

Click Connect on the Vercel card. A modal opens:

Field	Value	Example
Access Token	Your Vercel token	`Bearer token from vercel.com/account/tokens`

Validate & Save

Reeve validates the token by calling GET /v9/projects on the Vercel API. If the token is valid and has the right permissions, it's encrypted and stored.

Railway 🚂

Connect Railway for backend infrastructure and deployment management.

Auth type: API Key (modal)

What you get: Service status, deployment history, project info

Get Your Railway API Token

Go to railway.com/account/tokens
Click Create Token
Name it (e.g., "Reeve Integration")
Copy the generated token

Enter the Token in Reeve

Click Connect on the Railway card:

Field	Value	Example
API Token	Your Railway token	`Token from railway.com/account/tokens`

Validate & Save

Reeve validates the token by running a GraphQL me query against the Railway API. If valid, the token is encrypted and stored.

Figma 🎨

Connect Figma for design file access, components, and design tokens.

Auth type: API Key (modal)

What you get: Design files, components, comments, design tokens

Get Your Figma Personal Access Token

Go to figma.com and log in
Click your avatar in the top-right → Settings
Scroll down to Personal access tokens
Click Generate new token
Give it a description (e.g., "Reeve Integration")
Copy the token — it starts with figd_

Enter the Token in Reeve

Click Connect on the Figma card:

Field	Value	Example
Personal Access Token	Your Figma token	`figd_abc123...`

Validate & Save

Reeve validates the token prefix (figd_) and length, then tests it against the Figma API. If valid, the token is encrypted and stored.

Managing Connections

Checking Status

The connectors page shows real-time status for all integrations:

✅ Meta Ads        Connected    Acme Ads Account
✅ Stripe          Connected    Last sync: 5m ago
✅ PostHog         Connected    Project: 12345
⚪ Google Ads      Not connected
⚪ TikTok Ads      Coming soon

Status is fetched from two API endpoints:

/connectors/ — Data source connectors (Klaviyo, Shopify)
/integrations/ — OAuth integrations (Meta, Stripe, Slack)

Disconnecting

Click the Disconnect button (visible on hover) for any connected platform. This:

Revokes tokens where possible (Stripe calls deauthorize, Google revokes refresh token)
Deletes stored credentials from the encrypted store
Stops data syncing immediately

Re-connecting

If a connection expires or breaks, click Connect again to go through the auth flow. Existing data isn't lost — only the credentials are refreshed.

How Agents Use Connectors

Once connected, your agents access platform data through specialized tools — no API keys needed:

// Revenue from Stripe
reeve_revenue({ action: "get_summary" })

// Analytics from PostHog / GA4
reeve_analytics({ action: "get_top_pages", period: "30d" })

// Shopify store data
reeve_shopify({ action: "get_products" })

// Email campaigns from Klaviyo
reeve_email({ action: "list_campaigns" })

// Ad performance from Meta
reeve_ads({ action: "get_performance", platform: "meta" })

// Social metrics
reeve_social({ action: "get_metrics" })

// Support tickets
reeve_support({ action: "list_tickets" })

The gateway resolves connector tokens through the Services API using service-to-service auth (X-Reeve-Services-Token). Agents never see raw API keys.

Connector data is fetched live when agents or the dashboard request it — Reeve doesn't store copies of your platform data. This means data is always current, but requires the external platform to be accessible.

Connectors

On this page