Adapters
Integrations
Every external service the platform talks to. Each runs in MOCK mode until its env vars are set — then it flips to LIVE with no code change. This is the shopping list for going live, by phase.
Total Adapters
16
Live
0
Mock (need keys)
16
Phase 1 — Live now
Claude API
All AI modules
Intent detection, RAG, generation
Required env vars
Stripe
Sales Closer
Required env vars
PayPal
Sales Closer
Required env vars
Helpdesk / Ticketing
Customer Support
Zendesk / Freshdesk
Required env vars
Shipping Tracker
Customer Support
TCS / Leopards
Required env vars
PostgreSQL
Central Data Layer
Swaps in-memory store → Postgres (schema.sql)
Required env vars
Auth (Clerk/Auth0)
Control Center
Admin/manager access
Required env vars
Phase 2 — Coming next
WhatsApp Business API
Outreach
Requires pre-approved templates
Required env vars
Email (SendGrid/SMTP)
Outreach
Required env vars
Instagram Graph API
Outreach
Required env vars
LinkedIn Messaging
Outreach
⚠ Automated DMs against LinkedIn ToS — needs a bridge or skip
Required env vars
Google Calendar
Appointment Setter
Required env vars
Calendly
Appointment Setter
Required env vars
Phase 3 — Future
Apollo.io
Lead Hunter
Required env vars
Clay.com
Lead Hunter
Required env vars
Google Places
Lead Hunter
Required env vars
How to go live
- Add the required keys to
.env.local. - Restart the dev server — the adapter detects the env var and switches to LIVE automatically.
- For the data layer, set
DATABASE_URLand runschema.sqlto swap the in-memory store for Postgres.