HubSpot, Pipedrive and Salesforce can stay in sync with the LetsBot CRM in both directions. Two-way sync uses the same connection as your existing WhatsApp notifications and chat-sidebar lookups, which keep working as before. The integration is free; you need your own subscription to that CRM.
What syncs
| LetsBot | HubSpot | Pipedrive | Salesforce |
|---|---|---|---|
| Customers | Contacts ↔ | Persons ↔ | Contacts ↔, Leads → |
| Companies | Companies ↔ | Organizations ↔ | Accounts ↔ |
| Deals | Deals ↔ | Deals ↔ (won and lost) | Opportunities ↔ |
| Tasks | Tasks ↔ | Activities ↔ | Tasks ↔ |
| Timeline | Notes → | Notes, calls and meetings → | Notes → |
↔ = both ways · → = into LetsBot only. You can switch any module off or keep it one way.
Step by step
- Open CRM → CRM integrations and choose HubSpot, Pipedrive or Salesforce.
- If you connected before two-way sync existed, press Reconnect once so LetsBot may write changes back. Until then, some modules stay read-only and the page tells you which.
- Choose modules and directions, match deal stages, and check the field mapping.
- Press Start sync. Nothing is written before that.
New WhatsApp numbers
By default, new WhatsApp numbers are not added to your CRM — the integration already logs conversations. In Salesforce you can choose to create a Lead for each new number (Company is set to “[not provided]” until you fill it in).
Speed and limits
- HubSpot — changes arrive within minutes.
- Pipedrive — changes arrive as they happen, through Pipedrive webhooks.
- Salesforce — LetsBot checks for changes on a schedule and pauses at 80% of your org’s daily API limit. Your Salesforce edition must include API access.
Records are matched by phone number in international format, then e-mail, then the CRM’s own ID, so the first sync does not create duplicates. By default the most recent change wins, field by field.