Applications

Integrations

Connect the systems you already run — Vavan brings them into Vavan Core and keeps them current.

Integrations are part of Vavan's Connect layer. Their job is to bring external systems — your CRM, ERP, accounting, email, and prospecting tools — into Vavan Core, where their records are normalized into the same typed objects every app already understands. Once a system is connected, its data stops being a separate silo and becomes part of your one model of the business.

This is why integrations require no point-to-point wiring between apps: an imported record becomes a real Vavan Core object, so the CRM, Dispatch, Dock, and the rest see it natively. For how the layers fit together, see the platform architecture.

Credentials & security

Integration credentials — API keys, OAuth tokens, and connection secrets — are stored per-organization and encrypted in a dedicated credential store. They are never placed in shared application configuration or environment variables. Each organization connects its own external accounts with its own credentials, and those credentials are only ever used to sync that organization's data within that organization's isolation boundary.

Note. Because credentials are scoped to the organization, no integration can read or write across organization boundaries, and rotating or revoking a connection affects only the organization that owns it. See Security & isolation for the full isolation model.

Integration categories

Vavan integrates with the systems most physical-B2B operators already run. The table below lists the available categories, representative systems, and what each connection syncs.

Category	Examples	What syncs
CRM	Salesforce, HubSpot	Accounts, contacts, opportunities
ERP	Generic ERP connector	Products, orders, inventory
Accounting	QuickBooks Online	Invoices, customers, payments
Email	Outbound email delivery provider	Sends sequence steps and notifications; delivery and bounce status
Prospecting / enrichment	Apollo, OpenStreetMap	Net-new businesses and contact enrichment to discover new accounts

How synced data maps to Vavan Core objects

Connecting a system does not create a parallel copy of its schema. Each external record type is mapped onto a Vavan object type and its properties, so downstream apps work with native objects rather than vendor-specific payloads. For example:

A Salesforce Account (or HubSpot company) maps to a Vavan Account object; its contacts map to Contact objects linked to that account.
A CRM opportunity maps to the corresponding pipeline object so it appears in the CRM's stages alongside natively created deals.
An ERP order maps to an Order object with its Line Items, each line resolved to a Product in the catalog.
An accounting invoice and payment attach to the same Account and Order, so billing status is visible where the rest of the customer record lives.

Direction & the import pipeline

Most integrations run inbound: Vavan imports records from the external system and normalizes them into Vavan Core on a schedule or as changes occur. Where a connection supports it, Vavan also performs an outbound push — for example, writing updates back to a connected CRM, or sending email through the outbound delivery provider for Sequences and notifications.

Inbound records pass through a normalization pipeline before they become objects. The pipeline maps fields to the target object type, then performs deduplication and identity resolution so that the same real-world entity arriving from different sources — a company in both your CRM and your ERP, for instance — resolves to a single Vavan object instead of creating duplicates. The result is one clean, current record per real thing, which every application then reads and writes.