Keep Zendesk organisations in step with recent HubSpot company changes. The flow runs every five minutes to create new records or update existing ones so support agents always see current company data. It suits teams that sell in HubSpot and serve customers in Zendesk.

A schedule starts the run every five minutes. A small function reads the last run time and gives it to HubSpot to fetch only recently modified companies. The flow also loads all Zendesk organisations and merges both lists by company name to find matches. A check sends matched items to an update in Zendesk and sends the rest to a create step, then a final function saves a new last run time.

You will need a HubSpot private app token and a Zendesk API token. Confirm the name and domain fields map from HubSpot to Zendesk, and keep the merge key set to name on both sides, or adjust it to fit your data. Expect fewer data entry tasks and faster ticket handling because agents always see up to date organisation details. This can cut manual updates from hours each week to minutes.

• Runs on a schedule every five minutes using a Cron trigger.
• Reads the last run time so only recent HubSpot company changes are fetched.
• Pulls recently modified HubSpot companies with a since filter.
• Loads all Zendesk organisations for a full comparison.
• Merges HubSpot and Zendesk data by company name to find matches.
• Checks for a Zendesk id to decide between update or create.
• Creates new Zendesk organisations with name and domain from HubSpot.
• Updates existing Zendesk organisations when details change.
• Saves a new last run timestamp to support reliable incremental syncing.

• Reduce manual company updates from hours each week to minutes
• Automate 100% of company creation and updates in Zendesk from HubSpot changes
• Improve data accuracy by removing copy and paste steps
• Connect HubSpot and Zendesk so agents see the same company info
• Keep records fresh with five minute checks for near real time sync

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with HubSpot and Zendesk. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, create a HubSpot credential. In your HubSpot portal, create a Private App and copy the access token. In n8n, choose HubSpot App Token, paste the token, give the credential a clear name, and save.
4. Open the HubSpot node named Get modified companies and select your HubSpot credential. Confirm the resource is company and the operation is getRecentlyModified. Leave the since filter connected to the lastExecution field.
5. Create a Zendesk credential in the n8n credentials manager. In Zendesk Admin Center, enable API access and create an API token. In n8n, choose Zendesk API token, enter your subdomain, email, and API token, name the credential, and save. You may also follow the on screen instructions if using OAuth.
6. Assign the Zendesk credential to the nodes Get all Zendesk organisations, Create organisation, and Update organisation by opening each node and selecting the saved credential.
7. Open the Merge node Add Zendesk company data to Hubspot data. Confirm the mode is mergeByKey with propertyName1 set to properties.name.value and propertyName2 set to name. Adjust only if your field names differ.
8. Check field mappings for domain data. Ensure the HubSpot company property domain is available and used in the Zendesk nodes for domain_names. If your HubSpot property name is different, update the expression to match.
9. Set up the last execution timestamp logic. In the function node Get last execution timestamp, ensure it outputs a field named lastExecution in ISO format. If you are unsure, set a safe default like a recent past date.
10. Run a test. Update a company name or domain in HubSpot, then execute the workflow once. Verify that a matching organisation is updated in Zendesk or that a new organisation is created.
11. Check results in Zendesk. Confirm the organisation name and domain match the HubSpot record. If nothing changes, verify the company name match and the since filter timestamp.
12. Activate the workflow so the schedule runs every five minutes. Monitor the n8n execution list for errors. If matches fail due to naming differences, consider changing the merge key to use domain for a stronger match.