CRM integrations

Connect a CRM once, and its contact records keep themselves current from what your customers consented to share — auto-mapped, live, with documents and signed flows appearing as activity on the record. No code. Most CRMs need nothing beyond the OAuth connection — a couple ask for one extra guided step first, covered on that CRM's own setup page.

How it works

Every CRM integration is the same shape, whichever CRM you pick:

1. Connect once. Sign in to allus, open Configuration → Integrations, and click Connect — the portal provisions everything on your behalf (no credentials to create or paste), then hands you to the CRM's own consent screen, the same OAuth flow it already uses for any other app. The sync runs on a live service — its data client and its webhook — so it needs your company on the Basic level or above.
2. Fields map themselves. A standard set of contact fields (name, email, phone, address) maps onto your CRM's native contact properties automatically; anything else your service asks for lands as a labelled custom property. Most CRMs need nothing configured by hand for this. Two exceptions: Microsoft Dynamics 365 asks for your environment address and a publisher prefix before it can even build the sign-in link, and the administrator who connects needs the customization privileges; and Freshsales walks you through a short field wizard for the properties its API cannot create on its own — a mapping sits flagged until that wizard finishes. Both are covered step by step on that CRM's own setup page.
3. Customers connect on their terms. A customer connects their allme profile to your service and chooses which fields answer each request, exactly like every other allme connection — see how it works.
4. Records stay current, live. When a connected customer edits a synced field, the CRM contact updates within seconds. Withdrawing a field clears the property and leaves a note explaining why — with one exception: a field the CRM itself will not hold a contact without (a last name, in Salesforce and Zoho) stays on the record, and the note says so, so the record still tells you the customer stopped sharing it. That CRM's own setup page names its exception.
5. Documents and signed flows show up as activity. Where a CRM's activity/timeline model supports it, a signed document or a completed contract flow appears as a dated note on the contact — automatically, not exported by hand.

What we never do

• Sync is one-way. allme → your CRM, never the reverse. Editing the contact in your CRM does not change the person's allme profile, and it does not create a two-way merge.
• No CRM-side edit detection. The next synced update simply overwrites what the CRM held — there is no conflict to resolve because there is no other write path.
• No document bytes land in a CRM. Photo, document and legal-document fields never sync to a CRM property; only the fact that a document exists (name, kind, date) shows up as an activity note.
• No business-customer sync. Every CRM contact created by these integrations is a person — the connecting counterparty in a company-to-person connection, exactly like every other allus connection. Company-to-company data never flows through this surface.

Supported CRMs

Rows appear here only once that CRM's integration has actually shipped — this table is never aspirational.

Next

How the underlying connection model works · Webshop plugins · SDKs