Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineIntermediate

Zendesk to Pipedrive Ticket Sync

Zendesk to Pipedrive Ticket Sync is a 21-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.

21

Nodes

23

Edges

6

Zones

System stack

2 integrations

  • Zendesk
  • Pipedrive
Zendesk to Pipedrive Ticket Sync interactive execution graphStructural view of 21 workflow nodes and 23 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.Every day at 09:00. integration node, cron. 0 incoming and 1 outgoing connections.Every day at 09:00INTEGRATIONCRON0 IN / 1 OUTGet last execution timestamp. transform node, functionItem. 1 incoming and 1 outgoing connections.Get last execution timest…TRANSFORMFUNCTIONITEM1 IN / 1 OUTGet tickets updated after last execution. integration node, zendesk. 1 incoming and 1 outgoing connections.Get tickets updated after…INTEGRATIONZENDESK1 IN / 1 OUTChannel is email. decision node, if. 1 incoming and 3 outgoing connections.Channel is emailDECISIONIF1 IN / 3 OUTSet search email. transform node, set. 1 incoming and 1 outgoing connections.Set search emailTRANSFORMSET1 IN / 1 OUTRemove duplicates to make search efficient. transform node, itemLists. 1 incoming and 1 outgoing connections.Remove duplicates to make…TRANSFORMITEMLISTS1 IN / 1 OUTSearch persons by email. integration node, pipedrive. 1 incoming and 1 outgoing connections.Search persons by emailINTEGRATIONPIPEDRIVE1 IN / 1 OUTNoOp. integration node, noOp. 1 incoming and 0 outgoing connections.NoOpINTEGRATIONNOOP1 IN / 0 OUTAdd Pipedrive person Id to Zendesk tickets. decision node, merge. 2 incoming and 1 outgoing connections.Add Pipedrive person Id t…DECISIONMERGE2 IN / 1 OUTPipedrive person Id found. decision node, if. 1 incoming and 3 outgoing connections.Pipedrive person Id foundDECISIONIF1 IN / 3 OUTRename fields and keep only needed fields. transform node, set. 1 incoming and 1 outgoing connections.Rename fields and keep on…TRANSFORMSET1 IN / 1 OUTAdd comments to tickets. decision node, merge. 2 incoming and 1 outgoing connections.Add comments to ticketsDECISIONMERGE2 IN / 1 OUTGet Zendesk comments for tickets. integration node, httpRequest. 1 incoming and 1 outgoing connections.Get Zendesk comments for …INTEGRATIONHTTPREQUEST1 IN / 1 OUTNoOp1. integration node, noOp. 1 incoming and 0 outgoing connections.NoOp1INTEGRATIONNOOP1 IN / 0 OUTProcess commenst per ticket. integration node, splitInBatches. 2 incoming and 1 outgoing connections.Process commenst per ticketINTEGRATIONSPLITINBATCHES2 IN / 1 OUTSplit comments to seperate items. transform node, itemLists. 1 incoming and 1 outgoing connections.Split comments to seperat…TRANSFORMITEMLISTS1 IN / 1 OUTNew comment. decision node, if. 1 incoming and 2 outgoing connections.New commentDECISIONIF1 IN / 2 OUTAdd comment as a note in Pipedrive. integration node, pipedrive. 1 incoming and 1 outgoing connections.Add comment as a note in …INTEGRATIONPIPEDRIVE1 IN / 1 OUTSet new last execution timestamp. transform node, functionItem. 1 incoming and 0 outgoing connections.Set new last execution ti…TRANSFORMFUNCTIONITEM1 IN / 0 OUTDone processing. decision node, if. 1 incoming and 2 outgoing connections.Done processingDECISIONIF1 IN / 2 OUTNoOp2. integration node, noOp. 1 incoming and 0 outgoing connections.NoOp2INTEGRATIONNOOP1 IN / 0 OUT

Signal inspector

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

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.21 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 day at 09:00

Integration

02

Data & operations

10 nodes

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

Get last execution timestamp

Transform

Get Zendesk comments for tickets

Integration

Get tickets updated after last execution

Integration

Rename fields and keep only needed fields

Transform

Search persons by email

Integration

Remove duplicates to make search efficient

Transform

+ 4 more in system map
03

Intelligence & routing

6 nodes

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

Pipedrive person Id found

Decision

Add comments to tickets

Decision

Add Pipedrive person Id to Zendesk tickets

Decision

Channel is email

Decision

New comment

Decision

Done processing

Decision

04

Terminal actions

4 nodes

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

NoOp

Integration

Set new last execution timestamp

Transform

NoOp1

Integration

NoOp2

Integration

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