DPDP connectors for CRM
Customer records and their consents: 7 systems whose consents and requests the platform keeps in step, with proof.
CRM systems
Salesforce
HubSpot
Zoho CRM
Microsoft Dynamics 365
LeadSquared
Pipedrive
Freshsales
Product names and logos are trademarks of their owners.
How a connector works
Withdrawals reach the system
When someone withdraws consent, the connector stops that purpose in the system that uses it, and records when it did.Erasure and access requests
A request to erase, correct or see data is carried to each system that holds it, and each system's answer comes back to the request.Proof for every step
Every action a connector takes is written to the tamper-evident trail, so the evidence pack shows it happened and when.
Build your own
Any system without a ready connector still joins, in one of three ways.
REST API
Read and write consents, requests and records from your own code, with the same rules the console follows.Webhooks
Get each withdrawal, request and deadline as an event the moment it happens, signed so you can trust it.Guided manual tasks
For a system with no API, the platform gives a named person a task with steps and asks for proof when it is done.
Don't see your system?
Tell us which. We set up connectors with you during onboarding, and anything else joins by API, webhooks or a guided task.