Back to Integrations
integrationHTTP Request node
integrationZendesk node

HTTP Request and Zendesk integration

Save yourself the work of writing custom integrations for HTTP Request and Zendesk and use n8n instead. Build adaptable and scalable Development, Core Nodes, and Communication workflows that work with your technology stack. All within a building experience you will love.

How to connect HTTP Request and Zendesk

  • Step 1: Create a new workflow
  • Step 2: Add and configure nodes
  • Step 3: Connect
  • Step 4: Customize and extend your integration
  • Step 5: Test and activate your workflow

Step 1: Create a new workflow and add the first step

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.

HTTP Request and Zendesk integration: Create a new workflow and add the first step

Step 2: Add and configure HTTP Request and Zendesk nodes

You can find HTTP Request and Zendesk in the nodes panel. Drag them onto your workflow canvas, selecting their actions. Click each node, choose a credential, and authenticate to grant n8n access. Configure HTTP Request and Zendesk nodes one by one: input data on the left, parameters in the middle, and output data on the right.

HTTP Request and Zendesk integration: Add and configure HTTP Request and Zendesk nodes

Step 3: Connect HTTP Request and Zendesk

A connection establishes a link between HTTP Request and Zendesk (or vice versa) to route data through the workflow. Data flows from the output of one node to the input of another. You can have single or multiple connections for each node.

HTTP Request and Zendesk integration: Connect HTTP Request and Zendesk

Step 4: Customize and extend your HTTP Request and Zendesk integration

Use n8n's core nodes such as If, Split Out, Merge, and others to transform and manipulate data. Write custom JavaScript or Python in the Code node and run it as a step in your workflow. Connect HTTP Request and Zendesk with any of n8n’s 1000+ integrations, and incorporate advanced AI logic into your workflows.

HTTP Request and Zendesk integration: Customize and extend your HTTP Request and Zendesk integration

Step 5: Test and activate your HTTP Request and Zendesk workflow

Save and run the workflow to see if everything works as expected. Based on your configuration, data should flow from HTTP Request to Zendesk or vice versa. Easily debug your workflow: you can check past executions to isolate and fix the mistake. Once you've tested everything, make sure to save your workflow and activate it.

HTTP Request and Zendesk integration: Test and activate your HTTP Request and Zendesk 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

Popular HTTP Request and Zendesk workflows

HTTP Request node
Item Lists node
+5

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 Pipedrive account and Pipedrive credentials Zendesk account and Zendesk credentials Note: The Pipedrive and the Zendesk accounts need to be created by the same person / with the same email. How it works Cron node triggers the workflow every day at 09:00. Zendesk node collects all the tickets updated after the last execution timestamp. If node checks if the channel in the ticket is an email, and if so, it continues the workflow. The Item Lists node removes duplicates to make search efficient. Pipedrive node searches persons by email. Set node renames and keeps only needed fields (email & person id) Merge by key node adds the Pipedrive contact id to Zendesk tickets. The HTTP Request node gets Zendesk comments for tickets and the Merge node adds them to tickets. Split node adds nodes in batches with each iteration. Item list node splits comments into separate items. Pipedrive node adds comment as notes. 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.
HTTP Request node
Merge node
+3

Send Zendesk tickets to Pipedrive contacts and assign tasks

This workflow automatically sends Zendesk tickets to Pipedrive contacts and makes them task assignees. The automation is triggered every 5 minutes, with Zendesk checking and collecting new tickets which are then individually assigned to a Pipedrive contact. Prerequisites Pipedrive account and Pipedrive credentials Zendesk account and Zendesk credentials Note: The Pipedrive and the Zendesk accounts need to be created by the same person / with the same email. How it works Cron node triggers the workflow every 5 minutes. Zendesk node collects all the tickets received after the last execution timestamp. Set node passes only the requester`s email and ID further to the Merge node. Merge by key node merges both inputs together, the tickets and their contact emails. Pipedrive node then searches for the requester. HTTP Request node gets owner information of Pipedrive contact. Set nodes keep only the requester owner's email and the agent`s email and id. Merge by key node merges the information and adds the contact owner to ticket data. Zendesk node changes the assignee to the Pipedrive contact owner or adds a note if the requester is not found. The Function Item node sets the new last execution timestamp.

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.

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
Use case

Save engineering resources

Reduce time spent on customer integrations, engineer faster POCs, keep your customer-specific functionality separate from product all without having to code.

Learn more

FAQs

  • Can HTTP Request connect with Zendesk?

  • Can I use HTTP Request’s API with n8n?

  • Can I use Zendesk’s API with n8n?

  • Is n8n secure for integrating HTTP Request and Zendesk?

  • How to get started with HTTP Request and Zendesk integration in n8n.io?

Looking to integrate HTTP Request and Zendesk in your company?

Over 3000 companies switch to n8n every single week

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