Home / Integrations Built connectors are tested against recorded provider responses. Going live still needs your own provider account, credentials and approvals. Inside the app, each brand sees one of five statuses: Not connected, Connected, Needs attention, Unsupported or Test mode.
search
DataForSEO SERP API Built: needs your account to activate What it does Google organic SERP collection (async task_post/task_get) Location, language, device, depth SERP feature types Pixel rectangles when returned Provider cost per task Limits Google only in this release; Bing/Maps are P2 Pixel/above-fold metrics only when rectangles are returned You’ll need Paid DataForSEO account with SERP API enabled Adequate balance DATAFORSEO_LOGIN / DATAFORSEO_PASSWORD Provider docs: docs.dataforseo.com
DataForSEO Labs (keyword research) Built: needs your account to activate What it does Seed keyword ideas Domain ranked keywords Domain intersection Limits Coverage and freshness depend on the provider database Country list limited to mapped location codes You’ll need DataForSEO Labs product access Provider docs: docs.dataforseo.com
analytics
Google Search Console Built: needs your account to activate What it does OAuth (PKCE) read-only Property chooser Search analytics by date/query/page with pagination Revocation detection Limits Aggregate data only — never joined to individual leads GSC dates are Pacific-time days Recent days may be incomplete You’ll need Google Cloud OAuth client (verified consent screen for external users) User with property access Provider docs: developers.google.com
Google Analytics 4 Data API Built: needs your account to activate What it does Sessions and key events by date/source/medium/landing page Thresholding flag Property timezone Limits Thresholded/sampled data is labelled Separate connection from GSC You’ll need OAuth client with analytics.readonly scope GA4 property access Provider docs: developers.google.com
messaging
WhatsApp Business Platform (Cloud API) Built: needs your account to activate What it does Inbound messages and media references Free-form replies inside the service window Approved templates Delivery/read statuses Signed webhooks (X-Hub-Signature-256) Click-to-WhatsApp referral source Limits No personal WhatsApp/WhatsApp Web sync No historical chat import Template approval and pricing set by Meta You’ll need Meta business verification WhatsApp Business Account + phone number System user token App secret + webhook verify token Approved templates Provider docs: developers.facebook.com
calling
Exotel cloud telephony Built: needs your account to activate What it does Click-to-call (agent leg then customer leg) Status callbacks reconciled via Call Details API Customer-leg talk time Recording URL when enabled Limits Not browser WebRTC Callbacks are unsigned → always reconciled Recording subject to account settings and law You’ll need Commercial Exotel account ExoPhone / caller ID provisioning API key + token Public callback URL Provider docs: developer.exotel.com , developer.exotel.com
payments
Razorpay payment links (customer payments) Built: needs your account to activate What it does Payment links per deal Signed webhooks Authenticated fetch reconciliation Refund events Limits Uses the tenant’s own merchant account Separate from VisiRelay subscription billing You’ll need Tenant Razorpay merchant account Key id/secret Webhook secret Provider docs: razorpay.com
billing
Razorpay subscriptions (VisiRelay billing) Built: needs your account to activate What it does Plan subscriptions Webhook + fetch reconciliation Cancellation at cycle end Invoices Limits Taxes/GST invoicing need accountant review You’ll need Our merchant account with Subscriptions enabled Plans created in Razorpay Provider docs: razorpay.com
email
Transactional email (SMTP / Amazon SES) Built: needs your account to activate What it does Verification, reset, invites, report delivery Limits Production requires verified domain and SES production access You’ll need Verified sender domain (SPF/DKIM) SES production access Provider docs: docs.aws.amazon.com
ai
Anthropic API (AI response experiments) Built: needs your account to activate What it does Prompt sampling Optional web-search grounding with returned citations Limits API experiments are not measurements of consumer AI products You’ll need ANTHROPIC_API_KEY with budget Provider docs: docs.anthropic.com
leads
Website forms + tracking script Built: needs your account to activate What it does Embeddable form Consent-aware page tracking Signed anonymous visitor token Limits No free-text/PII collection by the tracking script You’ll need Install snippet on a verified domain
Signed inbound lead API Built: needs your account to activate What it does Scoped API keys Idempotency keys Generic field mapping for any source You’ll need
Meta Lead Ads Unsupported for now Limits Planned (P2): requires app review and advertiser permissions You’ll need Meta app review (leads_retrieval) Page/form mapping Provider docs: developers.facebook.com
Google Sheets Unsupported for now Limits You’ll need
IndiaMART Generic inbound API mapping only What it does Use the signed inbound API with field mapping Limits No native connector until an authorized API contract and credentials exist You’ll need Authorized API access from the portal
Justdial Generic inbound API mapping only What it does Use the signed inbound API with field mapping Limits No native connector until an authorized API contract and credentials exist You’ll need Authorized API access from the portal
Property portals (99acres, MagicBricks, Housing) Generic inbound API mapping only What it does Use the signed inbound API with field mapping Limits No native connector until authorized API contracts exist You’ll need commerce
Shopify / WooCommerce Unsupported for now Limits Planned (P2) via documented webhooks You’ll need Store app/webhook credentials