Integrations
Metaventus plays well with others
Connect your Google and Microsoft accounts, your video call tools, your payment methods — and migrate from your old CRMs in a few clicks.
No credit card required
Our position
Three reasons to integrate, and only one not to
What already belongs to you
Your corporate identity, your calendars, your payment account. These are your accounts, not ours: replacing them would mean asking you to move house for nothing.
Where you come from
Migration connectors exist so that leaving somewhere else is easy. They are used once, and that is just as it should be: a permanent integration with the tool you are leaving is not a migration, it is a dependency.
What involves hardware
An IP desk phone is an object sitting on a desk. It is provisioned, not hosted.
And what we do not integrate
Everything the suite already does. Connecting an emailing tool, an appointment booking calendar or a third-party phone system would mean recreating the seams we have spent two years removing.
Identity & messaging
Team login with a Google Workspace account.
Microsoft 365
Microsoft login and Outlook calendars visible in Metaventus.
SAML / OIDC SSO
Azure AD, Google Workspace, Okta, OneLogin, Auth0 — centralized enterprise login.
Video conferencing
Microsoft Teams
Meeting link generated automatically for your appointments.
Google Meet
Meetings created on your account with every booking.
Zoom
Your video appointments on your connected Zoom account.
CRM & marketing migration
Brevo
Contacts, companies, opportunities, tasks, lists and templates imported.
HubSpot
Guided CRM data migration with deduplication.
Efficy
Contacts and companies brought over via API connector.
Calendly
Schedules and event types imported into the Booking hub.
CSV import
Universal import with column mapping, for everything else.
Payment & telephony
Stripe
Payment links on your own Stripe account or via the managed account.
Yealink IP phones
Automatic provisioning of your desk phones by MAC address.
And for everything else: the API
What we do not integrate, you can connect yourself. 772 public endpoints, scoped keys, IP address restriction, rotation and expiry — and outgoing webhooks so you are notified rather than having to poll.
Explore the API documentationFAQ
Frequently asked questions
You don't have two thousand connectors?
No, and we do not want them. A catalogue of several hundred connectors is an admission: it acknowledges that the solution needs to be plugged in elsewhere to reach its best. That is not what we believe. We provide the essentials — identity, calendars, video conferencing, payment, migration — and for everything else, we are already equipped: the eight hubs cover the business functions, and the API covers the special cases.
So it is the Apple philosophy, in short?
That is the idea, yes: a coherent ecosystem rather than an assembly of parts. We prefer one feature that holds up all the way to ten that stop at the first special case — and a connector is often the ninth of those ten.
And what if my tool is not on the list?
Two honest answers. Either the suite already does what that tool does, and the real question is why you are keeping two. Or it does not, and the public API lets you connect it: 772 endpoints, scoped keys, outgoing webhooks.
Do you use Zapier or Make?
You can connect them to our API and webhooks, nothing prevents it. But the built-in automation already does what you would go there for — and it works on the same database, with no delay, no copying and no extra invoice.
What happens if you add a connector?
It appears on the Releases page, like everything else. We add them when they fall under the three reasons above — what already belongs to you, where you come from, what involves hardware. Not to make a list longer.
Another question? Write to us — a human will answer.
Ready to bring all your tools together?
Create your free account in two minutes: CRM, telephony, marketing, appointments and customer service — all in one place, with AI built in.
No credit card required