Community Contributed: Zendesk to Pipedrive Integration (Unverified)

Name: Community Contributed: Zendesk to Pipedrive Integration (Unverified)
Rating: 1.0 (1 reviews)
Author: Free N8N

Beginner

0 nodes connected

detail.loadingPreview

Free N8N Temples

38 views

0 downloads

Customer Supportautomationcrmintegrationpipedriveticketingzendesk

Automate ticket assignment in Zendesk based on Pipedrive contact ownership.

🚀Ready to Deploy This Workflow?

⚡Deploy on Zeabur 🎁Get $200 Credit on DigitalOcean

About This Workflow

Overview

This workflow is a community-contributed template designed to automatically update the assignee of Zendesk tickets to match the owner of the associated Pipedrive contact. It runs periodically to check for new or updated tickets.

Key Features

Periodically checks Zendesk for new tickets created since the last execution.
Retrieves requester information from Zendesk.
Searches for the requester in Pipedrive using their email.
If found in Pipedrive, it identifies the owner of the Pipedrive contact.
Updates the Zendesk ticket's assignee to the identified Pipedrive contact owner.
Supports both agents and admins as potential assignees.

How To Use

Set up Credentials: Ensure you have valid Zendesk and Pipedrive API credentials configured in n8n.
Configure Environment Variables: Set BASE_URL for Pipedrive API calls if needed.
Adjust Cron Schedule: Modify the 'Every 5 minutes' node if you need a different execution frequency.
Review Node Logic: Examine the 'functionCode' and query parameters in each node to understand and customize the workflow's behavior.
Test Thoroughly: Before enabling in production, run the workflow and verify that tickets are being assigned correctly based on your Pipedrive contacts.

Apps Used

automation

crm

integration

pipedrive

ticketing

zendesk

Workflow JSON

{
  "id": "b9a2105f-7e89-492e-9820-1eddfbb90a0a",
  "name": "Community Contributed: Zendesk to Pipedrive Integration (Unverified)",
  "nodes": 0,
  "category": "Customer Support",
  "status": "active",
  "version": "1.0.0"
}

Note: This is a sample preview. The full workflow JSON contains node configurations, credentials placeholders, and execution logic.