Skip to content
FlowHubFluxonLab
HubSpot
HubSpotfree

Sync Zendesk tickets to your HubSpot contacts

by n8n Teamadapted from n8n official workflow galleryUpdated Aug 2026
RequiresHubSpotHubSpotZendeskZendesk
Share Post Share
MeAdd Zendesk company data to Hubspot dataAdd Zendesk com…FISet new last execution timestampSet new last ex…FIGet last execution timestampGet last execut…Get modified companiesGet modified co…Get all Zendesk organisationsGet all Zendesk…IfCompany exists in ZendeskCompany exists …Create organisationCreate organisa…Update organisationUpdate organisa…CrEvery 5 minutes12345678910
1/5
STEPS · 10
Runs on a schedule

This workflow automatically syncs your Zendesk tickets to your HubSpot contacts. Every 5 minutes, your HubSpot account collects all the newly modified data and updates it into your Zendesk account, updating the current tickets or creating new ones. Prerequisites Zendesk account and Zendesk credentials HubSpot account and HubSpot credentials How it works Cron node triggers the workflow every 5 minutes. Function Item node collects all the tickets received after the last execution timestamp. HubSpot node collects all the recently modified companies. Zendesk node checks all the Zendesk tickets associated with those companies. Merge by key node merges the Zendesk and Hubspot data related to those companies. If node splits the workflow conditionally, based on data received. If the company already exists in, Zendesk node updates organization’sdata. If the company does not exist yet, Zendesk node will create an organization. The Function Item node sets the new last execution timestamp.

Tags

n8nreference-onlyhubspotzendesk
Connects
hubspotHubSpotzendeskZendesk
CategoryHubSpot
Triggermanual
Complexitymedium
Nodes9
AddedDec 23, 2022

Related workflows

See all HubSpot
hubspotzendesk
free

Update HubSpot contacts with Zendesk tickets

This workflow automatically syncs your Zendesk tickets to your HubSpot contacts. Every 5 minutes, your Zendesk account collects all the new or updated tickets and syncs them accordingly, with your HubSpot contacts database. Prerequisites Zendesk account and Zendesk credentials HubSpot account and HubSpot credentials How it works Cron node triggers the workflow every 5 minutes. Function Item node checks all the tickets received after the last execution timestamp. Zendesk node collects all tickets updated after last execution. Zendesk node collects the user data of ticket requester. Set node collects the contact`s email, name and externalID. Merge by key node combines two inputs, ticket data and ticket requester data. If node splits the workflow conditionally, based on data received. If the data corresponds to a ticket that already exists, HubSpot node will update the ticket. If the data does not correspond to a ticket, HubSpot node creates/updates the contact. Zendesk node updates the external Id in Zendesk for the said contact. HubSpot node creates a new ticket. Zendesk node updates the ticket with the external Id. The Function Item node sets the new last execution timestamp.

by n8n Team
hubspot
free

Two-way sync between Pipedrive and HubSpot

This workflow synchronizes data both ways between Pipedrive and HubSpot. Cron node** schedules the workflow to run every minute. Pipedrive* and *Hubspot nodes** pull in both lists of persons from Pipedrive and contacts from HubSpot. Merge1* and *Merge2 nodes** with the option Remove Key Matches identify the items that uniquely exist in HubSpot and Pipedrive, respectively. Update Pipedrive* and *Update HubSpot nodes** take those unique items and add them in Pipedrive and HubSpot, respectively.

by Lorena
hubspot
free

Update HubSpot when a new invoice is registered in Stripe

This workflow automatically posts a message in Slack when a new invoice is uploaded in Stripe, and it updates the fields in the HubSpot CRM. Prerequisites A Slack account and credentials A HubSpot account and credentials A Stripe account and credentials Nodes Stripe Trigger node triggers the workflow when a new invoice is uploaded. IF nodes filter the invoices that don't have a PO number and if there is no deal for the PO. HubSpot nodes retrieve deals with the specific PO number and update the deal status to 'paid'. Slack nodes post messages about the deals in a Slack channel.

by Jonathan