How the plane actually takes your stack.
Named scenarios, not a logo wall. Native today is mail, calendar, prospecting and CSV. Your ERP of record is ingested, not replaced.
Inbox as the work timeline
Microsoft 365 and Google Workspace, two-way mail and calendar — threads attach to the account that owns the work.
Migrate the book
CSV load of companies, contacts and history when you leave a spreadsheet or a legacy export.
ERP of record stays
SAP, Dynamics or Odoo keep the ledger. We map an ingest scenario — API or event path — we do not ship a native rip-and-replace connector.
Agents on the same objects
AI agents write deals and activities through the governed API. Approval queue + exportable audit. They resolve against the ontology, not a shadow table.
Events out
Webhooks push domain events into your automations. The event map grows with you — tell us what to subscribe.
Native connectors
Microsoft 365 & Google Workspace for two-way email and calendar sync, Apollo for prospecting and enrichment, Stripe for billing — connected in a click.
REST API
A first-class /api/v1 for companies, contacts, deals, activities, leads, agent runs and Heisen chat. Bearer mk_live_ keys, scoped, rate-limited, org-isolated.
Webhooks & events
Push meaningful domain events into your automations as they fire. The event map grows with you — tell us what you need to subscribe to.
AI-agent access
AI agents write straight into MaxorConnect through the same governed API, with approval tiers and a full audit trail. Built for the agentic era.
The tools operators already live in.
First-class connectors for the systems that carry email, calendar, prospecting and billing. Missing one? Tell us — we map the ingest.
Microsoft 365
Two-way email and calendar sync so conversations and meetings stay attached to the account that owns the work.
Google Workspace
Gmail and Google Calendar connected the same way — one operational timeline, not three inboxes.
Apollo
Prospecting and enrichment when you turn it on — company and contact data pulled into your book under your policies.
Stripe
Subscription billing and payment processing for MaxorConnect itself — cards never land in our databases in full.
CSV import
Bulk load companies, contacts and historical books when you're migrating off a spreadsheet or legacy export.
Google Ads & LinkedIn
Optional marketing-module OAuth: campaign and spend intelligence for your org only — Limited Use, never for third-party model training.
Connect → sync → act → verify.
Integrations are not a dump truck. They feed the same detect → recommend → verify loop as the rest of the platform.
Connect
OAuth or API key — you authorize the scope; you can revoke it anytime.
Sync
Records land in your org boundary only. No cross-tenant bleed, no silent sharing.
Act
Humans and agents work the same objects — deals, tickets, time — with ABAC and approval tiers.
Verify
Audit trail + intelligence loop close the loop: what changed, who did it, what to do next.
The same governed API your team's UI uses.
Your systems and your AI agents read and write MaxorConnect directly — through one bearer-authenticated, scoped, rate-limited REST API. Every call is policy-checked and lands in the audit trail.
POST /api/v1/deals
Authorization: Bearer mk_live_••••••••
Content-Type: application/json
{
"title": "Q3 platform rollout",
"value": 48000,
"stage": "proposal",
"external_id": "erp-88421"
}201 Created
{
"data": {
"id": "…",
"title": "Q3 platform rollout",
"value": 48000,
"stage": "proposal",
"external_id": "erp-88421"
}
}The integration you need isn't here? We build it.
Tell us the tool your team runs on. If it isn't a native connector yet, we'll wire it — over the REST API, a webhook, or a first-class native integration. Scoped with you, shipped fast.
What teams ask before connecting.
No. SAP, Dynamics or Odoo keep the ledger. The ingest map is keep vs take vs lands-on: we take a masked read or event path onto companies and deals. We do not ship a native SAP, Dynamics or Odoo connector.
Yes. Native connectors and the REST API are production surfaces. We prioritize the connectors your walkthrough needs.
Yes. /api/v1 is one governed surface for UI automations and AI agents — Bearer keys, scopes, org isolation and audit.
Tell us. We wire missing tools over the API, a webhook/event path, or a first-class native connector — held to the same standard, not a mock.
The developers page documents base URL, auth, endpoint catalog, Heisen chat and errors: /developers.
The control plane of the business.
Book a walkthrough.
CRM, small ERP and agents under approval — on one governed plane. Your ERP of record stays yours. In production today. Talk to us to start.