HubSpot’s Zendesk connection often lands tickets on the contact timeline and stops there. Sales needs tickets on the deal; marketing needs workflow triggers; support needs CRM context back in Zendesk. That is a bidirectional design problem, not a checkbox.
What native usually misses
- Ticket visibility on deal records.
- Reliable name/org sync beyond email match.
- HubSpot workflows firing on ticket priority/status.
- Pushing plan tier / CSM owner into Zendesk user fields.
Target architecture
- Zendesk trigger/webhook on ticket create/update → middleware.
- Match HubSpot contact by email; attach note + custom properties (
open_ticket_count,last_ticket_priority). - If a deal is open, mirror a note or association sales can see.
- Reverse: HubSpot company properties → Zendesk organization/user fields on a schedule or webhook.
Matching strategy
Email is necessary, not sufficient. Prefer external ids stored both sides after first sync. Handle shared inboxes and plus-addressing deliberately.
Privacy
- Sync ticket subjects carefully—they often contain personal data.
- Define retention when a contact is deleted in HubSpot (GDPR).
- Document Zendesk and HubSpot as subprocessors for customers.
Acceptance tests
- Enterprise-tagged ticket updates deal properties within a minute.
- Closing the last open ticket clears
has_open_ticket. - Replay webhook does not duplicate notes.
Need this built? HostHob ships production integrations and Marketplace-ready apps from Rotterdam. See our services or Design HubSpot–Zendesk sync.