HubSpot integration¶
Beta — Integration details
This integration's setup steps are based on standard HubSpot private app patterns. Specific API scopes, data objects, and credential handling will be verified against the live Dxtra application. If you encounter differences, please report an issue.
Connect your HubSpot workspace to Dxtra to automate privacy requests, manage consent, and maintain audit trails across contacts, deals, and communications.
What you can do¶
- Access requests — Export complete customer profiles including contacts, deals, tickets, and activity history.
- Erasure requests — Delete customer records and associated data from HubSpot.
- Consent management — Sync email preferences and communication consent across your workspace.
- Data discovery — Identify and catalog all customer data in HubSpot.
Prerequisites¶
- Active HubSpot account (Professional or Enterprise tier recommended)
- HubSpot admin or custom app developer access
- Dxtra workspace with admin permissions
Setup¶
Add HubSpot as a processor¶
- In Dxtra, go to Integrations → Processors.
- Click Select Processor and choose HubSpot from the dropdown.
- Follow the onboarding wizard: Data Processor Details → Enter API Key → Confirm.
- Dxtra displays your Data Controller DID for the connection.
- Click Onboard to complete setup.
Generate HubSpot private app token¶
- Log in to HubSpot and go to Settings → Integrations → Private apps.
- Click Create app and name it "Dxtra Privacy Compliance".
- On the Scopes tab, enable:
crm.objects.contacts.readandwritecrm.objects.companies.readandwritecrm.objects.deals.readandwritecrm.objects.tickets.readandwritecrm.objects.activities.read- Click Create app and copy your private app token.
- Paste the token in the Dxtra onboarding wizard.
Verify the connection¶
Once onboarded, the HubSpot processor appears in your Manage Processors table with an "Interconnected" badge. Test by creating a data subject request for a contact in HubSpot—Dxtra should retrieve their complete profile.
Data covered¶
| Object | Fields |
|---|---|
| Contacts | Name, email, phone, company, title, location, lifecycle stage, custom properties |
| Companies | Name, industry, employees, website, address, revenue, owner, custom properties |
| Deals | Name, amount, stage, close date, owner, associated contacts/companies, custom properties |
| Tickets | Number, subject, status, priority, origin, associated contact, comments, updates |
| Activities | Tasks, events, calls, emails, notes, timestamps, associated records |
| Forms | Form submissions, field values, submission dates |
How DSRR requests work¶
When you submit an access request in Dxtra:
- Dxtra queries HubSpot for the contact by email or ID.
- It gathers all associated data: company info, deal history, tickets, activities, and communications.
- Data is compiled and exported in your requested format.
- For erasure requests, you confirm scope and Dxtra deletes records with a full audit trail.
Troubleshooting¶
Connection fails
Verify your private app token is current and has the required scopes. Regenerate the token in HubSpot if needed. Check that your HubSpot account has admin permissions.
Missing data in exports
Confirm the contact exists in HubSpot and isn't archived. Verify the token's scopes include the objects you're querying. Check sync status on the Manage Processors page.
Deletion errors
Ensure the contact isn't a team member or locked by a workflow. Review any associated deals or active tickets that might prevent deletion. Contact HubSpot support if issues persist.
Best practices¶
- Test first — Run requests on test contacts before handling production data.
- Monitor sync status — Regularly check the Manage Processors dashboard for errors.
- Keep tokens secure — Regenerate your private app token if you suspect compromise.
- Document consent — Log all consent changes for audit purposes.
- Update privacy notices — Inform customers that you use Dxtra for privacy compliance.