HubSpot, Pipedrive, Zoho CRM and Salesforce
Send every new lead to your CRM with its score and source, and read status changes back. Your leads never wait for the CRM.
Connect
In Stores and CRMs → CRM, choose your CRM.
| CRM | How to connect | What DICE writes |
|---|---|---|
| HubSpot | Sign in, or a private app token with the contacts read and write scopes | Contacts |
| Pipedrive | Sign in, or your personal API token | Persons |
| Zoho CRM | Sign in (any data centre) | Leads |
| Salesforce | Sign in | Leads |
Field mapping
Each DICE field (name, email, phone, city, postal code, service, status, quality, score, source, notes) maps to one CRM field. Pick a direction per field:
- DICE → CRM: DICE sends it; changes in the CRM are ignored.
- CRM → DICE or Both ways: available for contact fields, service, status and notes. Score, quality and source only flow to the CRM.
When a field changed on both sides since the last sync, the conflict rule decides: newest change wins (default), DICE wins or CRM wins.
How sync works
- New and changed leads are queued and sent in the background, usually within a minute. An existing CRM record with the same email is linked instead of duplicated.
- With Read changes back on, DICE checks the CRM for changes every 15 minutes.
- If the CRM fails, DICE retries with growing pauses. The lead stays complete in DICE the whole time. After repeated failures the business owners get an email and the connection shows the error.
- Sync now sends waiting changes at once; the backfill option also sends leads from the last days you choose.
- The sync log lists what was sent or read and which fields changed. It never stores the values.
- Sandbox leads never leave DICE.