Integrations Overview

NearSync connects to a curated set of external services to deliver its platform capabilities. This section documents each integration: what it does, how it is configured, and what credentials are required.

Integration Catalog

Integration	Purpose	HQ Modules
Supabase	Database, authentication, file storage, edge functions, realtime	All modules
Twilio	Voice calling (WebRTC)	Comms HQ
Google Gemini	Primary AI provider, embeddings, RAG	Intelligence HQ, all AI-powered features
WhatsApp Business	Two-way messaging via Meta Business API	Comms HQ, Sales HQ
Sentry	Error tracking and monitoring	All apps (admin, portal, marketing)
Canva	Design asset management and export	Marketing HQ

Two kinds of integration, and why the difference matters

The services below fall into two groups, and the distinction decides who is responsible for the data that moves between them.

Services NearSync runs on your behalf. These are engaged by NearSync to deliver the product, on NearSync's own accounts, whatever you connect. They are sub-processors and are listed as such in the Data Processing Agreement, which is the authoritative list.

Services you connect yourself. You hold the account, you authorise the connection, and you can disconnect it at any time from the Integrations surface. When you connect one, you are instructing NearSync to exchange data with a provider you already have a relationship with, so that provider is not a NearSync sub-processor.

Services NearSync runs on your behalf

Platform

• Supabase -- database, authentication, storage, edge functions
• Vercel -- application and site hosting
• Sentry -- error monitoring

AI -- NearSync operates these on its own accounts:

• Google Gemini -- primary provider, embeddings and retrieval
• OpenAI -- secondary provider and fallback
• Anthropic Claude -- reasoning-heavy features
• xAI Grok -- where enabled
• Tavily -- web search performed on your behalf by AI features

Additional model providers -- Mistral, Groq, DeepSeek -- are selectable, but only where you supply your own credentials for them, which puts them in the second group. A model served locally through Ollama sends nothing to a third party at all.

Communications and meetings

• Resend -- transactional email
• Twilio -- voice and SMS
• LiveKit -- real-time audio and video sessions
• Meta (WhatsApp Business) -- two-way WhatsApp messaging
• Recall.ai -- meeting recording and transcription, where meeting intelligence is on
• Firebase Cloud Messaging -- mobile push delivery

Payments

• Stripe -- billing, and Stripe Connect for tenant billing
• Razorpay -- payment processing for INR

Reference data -- public tables NearSync pulls on a schedule. Nothing about you or your workspace is sent; NearSync's server fetches the table and stores it, so these are data sources rather than sub-processors:

• ExchangeRate-API (open.er-api.com) -- daily market exchange rates, refreshed at 02:30 UTC
• Central Bank of the UAE, read through the AllRatesToday republisher -- the published dirham rate table, each working day, used for UAE tax invoices in a foreign currency

Services you connect yourself

Each is connected through the unified OAuth flow on the Integrations surface, using an account you hold.

CRM and sales -- HubSpot, Salesforce, Pipedrive, Zoho, Freshsales

Projects and work management -- Asana, Monday, Notion, Trello, Jira, Linear

Accounting and commerce -- QuickBooks Online, Xero, Shopify, PEPPOL e-invoicing for supported jurisdictions

Calendar, meetings and productivity -- Google Workspace, Microsoft 365, Calendly, Cal.com, Zoom, Slack

Documents and design -- Canva, DocuSign, PandaDoc

Enrichment and data -- Lusha, Google Places, Google Ads, Airtable

Not every connector is available on every plan, and some require configuration by an administrator before they appear.

How Integrations Are Configured

Integrations fall into three configuration categories:

Platform-Level (Managed by NearSync)

These are configured once per deployment and apply across the entire platform instance. Examples include the Supabase connection, Sentry error tracking, and transactional email delivery. On Managed deployments, NearSync handles these. On BYOK deployments, the client provides their own credentials during the setup process.

Organization-Level (Admin Dashboard)

Some integrations are configured per-organization through the admin dashboard. The AI provider configuration, WhatsApp Business credentials, and lead enrichment settings are stored in the organization's settings and can be adjusted by admins in Intelligence HQ or System HQ.

User-Level (OAuth)

Integrations like Canva, HubSpot, and Salesforce use OAuth 2.0 flows where individual users authorize their own accounts. Token storage, refresh, and revocation are handled automatically by the platform.

What governs availability

An integration is available when the module it belongs to is switched on for that workspace. Supabase, Sentry, Resend and the AI providers are always available, because the modules behind them are always on. Everything else follows its module.

For what a plan costs, see the pricing page.

Integration-to-Module Mapping

• Comms module selected switches on Twilio (voice), WhatsApp Business, email integrations
• Marketing module selected switches on Canva, Meta, Mailchimp, LinkedIn, Google Ads
• CRM module selected switches on HubSpot, Salesforce, Zoho, Pipedrive, Lusha enrichment
• Finance module selected switches on Stripe, Razorpay, QuickBooks
• Operations module selected switches on Sentry monitoring dashboards, compliance tools
• Website module selected switches on Google Places (review sync), knowledge base tools

Core platform integrations (Supabase, Resend, Sentry, Gemini AI) are available on all tiers.

Managed vs. BYOK

Integration configuration differs based on your deployment type:

• Managed deployments: NearSync provisions and manages all platform-level credentials. You configure organization-level and user-level integrations through the admin dashboard.
• BYOK deployments: You provide your own Supabase project credentials and any third-party API keys during the setup process. The same integration capabilities are available; the difference is who owns and manages the infrastructure credentials.

For BYOK setup instructions, see the client portal's Setup tab after your deployment type is configured.