CRMs: HubSpot, Salesforce, Pipedrive, Zoho CRM

What syncs

Members become contacts (HubSpot, Salesforce, Zoho CRM) or persons (Pipedrive), matched by email and updated, never duplicated, with name, email, phone, membership level, status and renewal date. HubSpot and Pipedrive get three fields named Mybers Level, Mybers Status and Mybers Renewal Date, created on the first sync. Salesforce and Zoho CRM don't let Mybers create fields: add the three to Contact yourself and type their API names on the integration's Settings tab; until you do, name, email and phone sync and the rest is skipped. Pick the direction on the Settings tab: Mybers to CRM, CRM to Mybers, or both. New and changed members are pushed as they happen; a daily schedule catches the rest.

What each one needs

• HubSpot: a service key (HubSpot's new name for a private app token) with crm.objects.contacts and crm.schemas.contacts, both read and write. The schemas permission lets Mybers create its Level, Status and Renewal Date properties; without it names and emails still sync and the integration page shows the refusal. Settings → Integrations → Service keys, or Private Apps on older accounts.
• Pipedrive: your personal API token from Settings → Personal preferences → API.
• Zoho CRM: a Self Client in the Zoho API Console with scope ZohoCRM.modules.ALL. The code it generates lasts ten minutes, so swap it for the refresh token right away; the page walks you through it.
• Salesforce: an External Client App (or a Connected App on older orgs) with OAuth on, the api scope and the Client Credentials Flow enabled, plus a "Run As" user. Mybers signs in as that user, so there is no Allow screen. You need its Consumer Key and Secret and your My Domain address.

HubSpot, Pipedrive and Zoho CRM start on Starter; Salesforce is on Pro. See the plan badge on each card.