Integrations

Sync contacts with Google/Outlook

Once your Google Workspace or Microsoft 365 account is connected, import your contacts from Google Contacts (People API) or Outlook (Microsoft Graph) as CRM contacts, without duplicating and without overwriting what you have already filled in.

Contact sync works over the same OAuth connection used for email and calendar (BYO model: the OAuth app belongs to your organization). It brings your contacts from the provider into the CRM as Contact records.

Prerequisite: grant contacts access

When you connect Google Workspace or Microsoft 365, the CRM now also requests contacts permission (Google: contacts; Microsoft: Contacts.ReadWrite), in addition to email and calendar. If you had already connected the account BEFORE this update, the connection does not include contacts: open Settings → Integrations, click "Reconnect" on the provider card and grant the contacts permission. The "Contact sync (two-way)" section then shows "Syncing".

💡 In your organization's OAuth app, make sure the contacts permission is enabled: on Google, enable the People API; on Azure, add the delegated permission Contacts.ReadWrite to Microsoft Graph.

Import contacts (Provider → CRM)

Open Settings → Integrations and find the connected provider card.
In the "Contact sync (two-way)" section, click "Import contacts".
The CRM reads your contacts (up to 200 at a time) and creates or updates a Contact for each one. It reports how many it read, created and updated.

How matching and deduplication work

The matching key is the contact's EMAIL: if a Contact with that email already exists, it is updated instead of duplicated; otherwise, a new one is created. The CRM also stores the provider's contact id (on the record itself) as an additional dedup safeguard. When updating an existing contact, the CRM only fills in fields that are EMPTY, and never overwrites the name, phone or job title you have already adjusted in the CRM.

💡 Contacts without an email are skipped on import, because email is required on the Contact and is the key used to avoid duplicates. Add an email to the provider contact to bring it in.

Send a CRM contact to the provider (CRM → Provider)

You can also create a CRM contact in your Google/Outlook (best-effort). When sent, the CRM keeps the link so it does not recreate the same contact on future sends. This direction is optional and only works with the contacts permission granted.

No connection? The feature stays inert

If you have not connected an account (or did not grant the contacts scope), nothing is imported or sent, and there are no errors in your workflow. The import button only appears when there is an active connection with the contacts permission.

How to test

In Settings → Integrations → connected provider card, "Contact sync (two-way)" section, click "Import contacts".
Check the summary shown: how many contacts were read, created and updated.
Open the CRM Contacts list and check that a known contact from your Google/Outlook appeared (or was updated) without duplicating.

Troubleshooting

The "Import contacts" button does not appear: there is no connection with the contacts scope. Click "Reconnect" on the card and grant the contacts permission (Google: contacts / People API; Microsoft: Contacts.ReadWrite).
Some contacts did not come in: contacts WITHOUT an email are skipped (email is required and is the dedup key). Add an email to the provider contact and import again.
A contact I had already adjusted was "overwritten": that should not happen. Import only fills EMPTY fields and never overwrites name/phone/job title you edited. If you notice an overwrite, report it to support with the contact.
403/insufficient permission: the contacts scope was not granted; reconnect and accept the permission on the consent screen. On Google, confirm the People API is enabled in the OAuth app.

Open this article inside the system →