WeCom for Pipedrive & Salesforce — integration for EU sales teams
Many EU companies run Pipedrive (lean SMB CRM) or Salesforce (enterprise) instead of HubSpot — yet WeCom inquiries still arrive from China. This post explains how WeCom CRM integration works for both stacks and what compliance teams should watch.
Why not “export & import”?
- Volume: Above ~5–10 leads per week, manual copy-paste fails.
- Language: Mandarin in spreadsheets is not searchable for EU managers.
- Pipeline: Without automatic person/deal links, forecasting breaks.
Pipedrive: typical mapping
| WeCom field | Pipedrive |
|---|---|
| Contact / company | Person + Organization |
| First message | Note on person |
| Intent / score | Custom field or label |
| Next step | Activity / task |
Use the REST API: create person, attach note, optional deal in a defined stage. Store the token as a workspace secret in the bridge.
Salesforce: typical mapping
| WeCom field | Salesforce |
|---|---|
| Contact | Contact (+ Account) |
| Conversation | Task or Note |
| Source | Lead Source = WeCom |
| Translation | Rich text note (EN) |
Enterprise teams often validate in sandbox first, with a dedicated WeChat_ID__c (or similar) field.
Shared GDPR checklist
- Document legal basis (often legitimate interest for B2B first contact).
- DPA with CRM vendor and bridge hoster.
- Retention policy (e.g. 24 months) you can enforce technically.
- Avoid US middleware without a transfer mechanism for personal content.
More depth: WeChat & GDPR 2026.
One bridge, multiple CRMs
The Pragma supports HubSpot, Pipedrive, and Salesforce from the same WeCom webhook — switch target CRM per workspace, not your China setup.
- Configure WeCom webhook once
- Paste the chosen CRM token
- Test lead → verify person/contact + note
Summary
WeCom Pipedrive integration and WeCom Salesforce integration mirror HubSpot: webhook → EU processing → structured CRM record. The difference is your fields and pipeline rules — not the China channel.