Salesforce 
HubSpot 
NetSuite 
Zendesk 
Microsoft Dynamics 365 Sales 
Dynamics 365 F&O 
Attio 
Pipedrive 
Zoho CRM 
Campfire 
Rillet 
Front 
Shopify 
Amazon Seller Central 
SendGrid Keep supported HubSpot and Zendesk records aligned with two-way sync. Give each team access to current data while controlling which system can update each field.
Example workflow
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Starting eventA change involving HubSpot Tasks or Zendesk Tickets needs a defined result in the other system.
Start with HubSpot Tasks and Zendesk Tickets. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve requester, organization, team, and status references before ticket updates.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyEscalate the same ticket twice, close one of several tasks, and verify that private ticket content is not copied into a public work item.
Review records and field ownershipMapping essentials
Match records by stable IDs and assign an owner for each field. The record notes identify the coverage to check.
Download the mapping worksheetCSV · No email required
| HubSpot record | Zendesk record | Record matching | Field ownership |
|---|---|---|---|
| TasksDocumented record: SupportedBusiness process handoff | TicketsDocumented record: Supported | Retain separate ticket and task IDs with an explicit relationship; several tasks may resolve one ticket. | Choose which ticket conditions create a work item and which task outcomes may update the support case. |
| CompanyDocumented record: SupportedRecord matching | OrganizationsDocumented record: :clock1: On Request | Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. | Assign ownership separately for relationship details and finance-controlled billing details. |
| TicketDocumented record: SupportedRecord matching | TicketsDocumented record: Supported | Retain the ticket ID and distinguish parent tickets, follow-ups, and merged cases. | Agree which queue controls status and assignee; keep private comments distinct from public replies. |
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Why teams connect HubSpot and Zendesk
Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one HubSpot and Zendesk workflow to test, define what success looks like, and decide who handles failed updates.
Push product signup and usage events into HubSpot contact properties to drive lifecycle marketing segmentation.
Write warehouse-computed lead and account scores back to HubSpot properties on a schedule or in near real time.
Sync tickets, users, and organizations into Postgres so support analytics run on SQL instead of repeated API pulls.
Write CRM account tier, owner, and renewal data onto Zendesk organizations and ticket fields so agents see context in the ticket.
Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| ✅ Supported. Confirm field permissions and sync direction. |
| 🕘 Coming soon. Confirm field permissions and sync direction. |
| ❌ Not supported. Confirm field permissions and sync direction. |
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| ✅ Supported. Confirm field permissions and sync direction. |
| :clock1: On Request. Confirm field permissions and sync direction. |
Review how each system connects, detects changes, and permits access to your records.
View setup requirements and limits| Connection requirement | HubSpot | Zendesk |
|---|---|---|
| Integration interface | REST API (CRM v3) | REST API |
| Authentication | OAuth | OAuth app authorization |
| Change detection | Record updates and association changes need separate validation. | The saved Stacksync guide does not specify the change-detection mechanism. |
| Read access | Available for supported records | Available for supported records |
| Write access | Available for supported records | Available for supported records |
Enterprise controls
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Review setup, record relationships, testing, and recovery for your implementation.
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
Setup guides: Authorize HubSpot
Setup guides: Authorize Zendesk
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Use the HubSpot and Zendesk planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.
Download the mapping worksheet · CSV, no email required
Business process
Support-to-work-item handoff: Zendesk Tickets provides context for HubSpot Tasks. These are related records, not equivalent entities.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Fields to include
References: HubSpot: Tasks documentationZendesk: Tickets documentation
Record matching
Compare whether HubSpot Company and Zendesk Organizations describe the same company in your business.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Fields to include
References: HubSpot: Company documentationZendesk: Organizations documentation
Record matching
Compare whether HubSpot Ticket and Zendesk Tickets describe the same support case or ticket in your business.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Fields to include
References: HubSpot: Ticket documentationZendesk: Tickets documentation
Record matching
Compare whether HubSpot Users and Zendesk Users describe the same application user or identity in your business.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Fields to include
References: HubSpot: Users documentationZendesk: Users documentation
Record matching
Compare whether HubSpot Attachments and Zendesk Attachments describe the same file or document metadata in your business.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Fields to include
References: HubSpot: Attachments documentationZendesk: Attachments documentation
This pair can involve both record sync and process handoffs. Keep the Tasks / Tickets relationship explicit: copying fields and creating a downstream business transaction require different validation.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Starting event: A change to the selected Tasks or Tickets record needs a defined result in the other system.
Expected result: Escalate the same ticket twice, close one of several tasks, and verify that private ticket content is not copied into a public work item.
If it fails: Check whether a reply or notification was already sent before replaying ticket actions.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Company or Organizations record needs a defined result in the other system.
Expected result: Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
If it fails: Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Starting event: A change to the selected Ticket or Tickets record needs a defined result in the other system.
Expected result: Test a merged ticket, a private note, a reopened case, and an attachment with restricted access.
If it fails: Check whether a reply or notification was already sent before replaying ticket actions.
Validate the selected objects and operations even where connector-level direction is documented.
Starting event: A customer-facing change in HubSpot needs operational context in Zendesk.
Expected result: The relationship survives a lifecycle change without creating a duplicate customer or triggering an unintended business action.
If it fails: Inspect merge/conversion history and existing destination records before replaying a lifecycle transition.
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Escalate the same ticket twice, close one of several tasks, and verify that private ticket content is not copied into a public work item.
The expected support case or ticket relationship is preserved with no duplicate action or unintended write.
Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
The expected company relationship is preserved with no duplicate action or unintended write.
Test a merged ticket, a private note, a reopened case, and an attachment with restricted access.
The expected support case or ticket relationship is preserved with no duplicate action or unintended write.
Test a renamed login, disabled account, missing group, and a user existing in two tenants.
The expected application user or identity relationship is preserved with no duplicate action or unintended write.
Check that each connected account can read and write the chosen objects. Exercise both directions with a test record before enabling production changes.
Only an approved, supported direction and permitted fields are written.
Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Inspect HubSpot Tasks and Zendesk Tickets, their IDs, and the destination error.
Check whether a reply or notification was already sent before replaying ticket actions.
Inspect HubSpot Company and Zendesk Organizations, their IDs, and the destination error.
Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.
Inspect HubSpot Ticket and Zendesk Tickets, their IDs, and the destination error.
Check whether a reply or notification was already sent before replaying ticket actions.
Check the HubSpot and Zendesk connector guides, account permissions, and any operations marked On Request.
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
Read the Stacksync issues dashboard guide for retry and revert behavior.
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Detect changesRecord updates and association changes need separate validation. Association detection uses full scans unless Associations CDC Boost is configured for an eligible account.
Apply updatesSelected writable fields update in Zendesk. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Apply updatesSelected writable fields update in HubSpot. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Stacksync connects HubSpot and Zendesk with two-way sync for supported records. Authorize the accounts, select the record types, and map compatible fields. Both connectors support reading and writing; object permissions determine the available fields. Use the Issues dashboard to inspect and resolve rejected updates.
Stacksync supports two-way sync between writable records in both systems. The chosen objects and fields must permit updates in both directions. Read-only fields can supply values but cannot receive updates. Stacksync can read database views; it does not write back to the view.
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Have a HubSpot Super Admin authorize Stacksync through the account connection flow. Provide the Zendesk subdomain in the Stacksync connection form and authorize the app. Use the pair worksheet to record ownership and acceptance criteria.
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
Start by reviewing Tasks in HubSpot and Tickets in Zendesk. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
This pair can involve both record sync and process handoffs. Keep the Tasks / Tickets relationship explicit: copying fields and creating a downstream business transaction require different validation.
Integration directory
Review documented support, sync direction, and setup requirements on each pair page. Search all 537 integrations listed for HubSpot and Zendesk.
Popular · 8 of 537
HubSpot and eClinicalWorks 
HubSpot and FullEnrich 
HubSpot and Google Sheets 
HubSpot and Klaviyo 
Zendesk and SAP Sales Cloud 
Zendesk and Streak CRM 
Zendesk and SugarCRM 
Zendesk and Twenty CRM Next step
Walk through your HubSpot and Zendesk records, field mappings, and requirements with an integration engineer.
