Back to Integrations
integrationHTTP Request node
integrationZendesk node

HTTP Request and Zendesk integration

n8n lets you integrate HTTP Request with Zendesk to build powerful workflows. Design automation that extracts, transforms and loads data between your apps and services. You can choose from thousands of ready-made apps or use our universal HTTP connector to sync apps not yet in our library.

Integrate HTTP Request and Zendesk

Build your own HTTP Request and Zendesk integration

Create custom HTTP Request and Zendesk workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.

How to connect HTTP Request and Zendesk

  • Step 1: Add the first step

  • Step 2: Add HTTP Request and Zendesk nodes

  • Step 3: Connect HTTP Request and Zendesk

  • Step 4: Run workflow

Sync Zendesk tickets to Pipedrive contact owners

This workflow syncs Zendesk tickets to Pipedrive contact owners.

This workflow is triggered every day at 09:00 with Zendesk collecting all the tickets updated after the last execution timestamp and updating them according to Pipedrive contacts. It also adds Zendesk comments to the tickets as notes in Pipedrive.

Prerequisites

Note: The Pipedrive and the Zendesk accounts need to be created by the same person / with the same email.

How it works

  1. Cron node triggers the workflow every day at 09:00.
  2. Zendesk node collects all the tickets updated after the last execution timestamp.
  3. If node checks if the channel in the ticket is an email, and if so, it continues the workflow.
  4. The Item Lists node removes duplicates to make search efficient.
  5. Pipedrive node searches persons by email.
  6. Set node renames and keeps only needed fields (email & person id)
  7. Merge by key node adds the Pipedrive contact id to Zendesk tickets.
  8. The HTTP Request node gets Zendesk comments for tickets and the Merge node adds them to tickets.
  9. Split node adds nodes in batches with each iteration.
  10. Item list node splits comments into separate items.
  11. Pipedrive node adds comment as notes.
  12. If node checks if the data processing is done and if not, goes back to the Split node.
    The Function Item node sets the new last execution timestamp.

Nodes used in this workflow

Over 3000 companies switch to n8n every single week

Zendesk supported actions

Create
Create a ticket
Delete
Delete a ticket
Get
Get a ticket
Get Many
Get many tickets
Recover
Recover a suspended ticket
Update
Update a ticket
Get
Get a ticket field
Get Many
Get many system and custom ticket fields
Create
Create a user
Delete
Delete a user
Get
Get a user
Get Many
Get many users
Get Organizations
Get a user's organizations
Get Related Data
Get data related to the user
Search
Search users
Update
Update a user
Count
Count organizations
Create
Create an organization
Delete
Delete an organization
Get
Get an organization
Get Many
Get many organizations
Get Related Data
Get data related to the organization
Update
Update a organization

Looking to integrate HTTP Request and Zendesk in your company?

Why use n8n to integrate HTTP Request with Zendesk

Build complex workflows, really fast

Build complex workflows, really fast

Handle branching, merging and iteration easily.
Pause your workflow to wait for external events.

Code when you need it, UI when you don't

Simple debugging

Your data is displayed alongside your settings, making edge cases easy to track down.

Use templates to get started fast

Use 1000+ workflow templates available from our core team and our community.

Reuse your work

Copy and paste, easily import and export workflows.

Implement complex processes faster with n8n

red iconyellow iconred iconyellow icon