Demand-led roadmap
Give customers the integrations they need—without maintaining every API.
Four connectors run today: Google Workspace Shared Contacts, HubSpot Contacts, Pipedrive Persons and Microsoft 365 organizational contacts. Need another provider or business system? Customer requirements shape what we build next.
Running today
Different provider worldviews. One canonical model.
Every provider models a contact differently—one unlabelled email here, many labelled addresses there, a directory that is read-only by design. Each connector declares what it can actually represent, so a write is never allowed to flatten the richer side. The API is versioned, so the contract your product builds against stays put while the platform grows behind it.
Google Workspace Shared Contacts
Domain-wide external contacts for Google Workspace organizations—not personal Google Contacts.
Build with this integration →Available · two-wayHubSpot Contacts
CRM contacts with identity, lifecycle, ownership and provider-specific property semantics. One unlabelled email per contact—so a write patches the primary address instead of replacing the list.
Build with this integration →In validation
Built, and being proven against live accounts.
These connectors are implemented and covered by tests. We validate each one against a real provider account—confirming field by field what survives a round trip—before it carries customer data. Ask us where a given one stands.
Pipedrive Persons
Many emails and phones per person, each keeping its own label and primary flag through a full round trip.
Build with this integration →In validation · readMicrosoft 365 Organizational Contacts
Tenant-wide contacts an administrator maintains—not personal Outlook contacts. Read-only, because the directory is the source of truth.
Build with this integration →Customer-led
Your requirement can be next.
We prioritize new work by technical feasibility, repeatability and commercial fit, then agree scope directly with the teams behind the requirement.
Salesforce Contacts
Scoped and built against a named customer, because most of the work is the configuration particular to your customers’ orgs.
Request this integration →Customer-ledCRM, calendar, directory or business system
Bring the object flow and provider your customers need. The same infrastructure is designed to extend beyond contact sync.
Tell us what should sync →