Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

Zendesk to Pipedrive Ticket Automation

Zendesk to Pipedrive Ticket Automation is a 17-node automation blueprint connecting Zendesk, Pipedrive. Inspect its trigger, execution graph, branches, and implementation requirements.

ZendeskPipedrive

Interactive system map

The entire automation, wired and inspectable.

Brand marks identify the operational stack. Focus or select any node to isolate its real incoming and outgoing connections.

17

Nodes

19

Edges

6

Zones

System stack

2 integrations

  • Zendesk
  • Pipedrive
Zendesk to Pipedrive Ticket Automation interactive execution graphStructural view of 17 workflow nodes and 19 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.Every 5 minutes. integration node, cron. 0 incoming and 1 outgoing connections.Every 5 minutesINTEGRATIONCRON0 IN / 1 OUTGet last execution timestamp. transform node, functionItem. 1 incoming and 1 outgoing connections.Get last execution timest…TRANSFORMFUNCTIONITEM1 IN / 1 OUTGet tickets created after last execution. integration node, zendesk. 1 incoming and 2 outgoing connections.Get tickets created after…INTEGRATIONZENDESK1 IN / 2 OUTGet requester information. integration node, zendesk. 1 incoming and 1 outgoing connections.Get requester informationINTEGRATIONZENDESK1 IN / 1 OUTKeep only needed requester information. transform node, set. 1 incoming and 1 outgoing connections.Keep only needed requeste…TRANSFORMSET1 IN / 1 OUTAdd requester information to ticket data. decision node, merge. 2 incoming and 2 outgoing connections.Add requester information…DECISIONMERGE2 IN / 2 OUTSearch requester in pipedrive. integration node, pipedrive. 1 incoming and 1 outgoing connections.Search requester in piped…INTEGRATIONPIPEDRIVE1 IN / 1 OUTGet owner information of Pipedrive contact. integration node, httpRequest. 1 incoming and 1 outgoing connections.Get owner information of …INTEGRATIONHTTPREQUEST1 IN / 1 OUTKeep only requester owner email. transform node, set. 1 incoming and 1 outgoing connections.Keep only requester owner…TRANSFORMSET1 IN / 1 OUTGet agents and admins. integration node, zendesk. 0 incoming and 1 outgoing connections.Get agents and adminsINTEGRATIONZENDESK0 IN / 1 OUTKeep only email and Id. transform node, set. 1 incoming and 1 outgoing connections.Keep only email and IdTRANSFORMSET1 IN / 1 OUTAdd contact owner to ticket data. decision node, merge. 2 incoming and 1 outgoing connections.Add contact owner to tick…DECISIONMERGE2 IN / 1 OUTAdd Pipedrive agent data to pipedrive contact information. decision node, merge. 2 incoming and 1 outgoing connections.Add Pipedrive agent data …DECISIONMERGE2 IN / 1 OUTChange assignee to Pipedrive contact owner. integration node, zendesk. 1 incoming and 1 outgoing connections.Change assignee to Pipedr…INTEGRATIONZENDESK1 IN / 1 OUTSet new last execution timestamp. transform node, functionItem. 2 incoming and 0 outgoing connections.Set new last execution ti…TRANSFORMFUNCTIONITEM2 IN / 0 OUTContact exists in Pipedrive. decision node, if. 1 incoming and 2 outgoing connections.Contact exists in PipedriveDECISIONIF1 IN / 2 OUTAdd a note requester not found. integration node, zendesk. 1 incoming and 1 outgoing connections.Add a note requester not …INTEGRATIONZENDESK1 IN / 1 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.17 connected nodesEnter or click to lock · Escape to clear

Structured review

Read the workflow as a system, not a node dump.

The workflow is grouped into operational zones, then reviewed for the controls needed to adapt the pattern safely.

01

Entry signals

1 node

Events, schedules, and unconnected roots that can start an execution.

Every 5 minutes

Integration

02

Data & operations

11 nodes

Transformations and external-system actions that move the work forward.

Get last execution timestamp

Transform

Get tickets created after last execution

Integration

Get requester information

Integration

Keep only needed requester information

Transform

Keep only requester owner email

Transform

Search requester in pipedrive

Integration

+ 5 more in system map
03

Intelligence & routing

4 nodes

Model calls and control points that interpret, branch, or govern the run.

Add requester information to ticket data

Decision

Add Pipedrive agent data to pipedrive contact information

Decision

Add contact owner to ticket data

Decision

Contact exists in Pipedrive

Decision

04

Terminal actions

1 node

Nodes with no visible outgoing edge: the workflow’s observable outcomes.

Set new last execution timestamp

Transform

Adjacent systems

Keep tracing the stack.

Related workflows share tools and similar system patterns.

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas