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

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

21

Nodes

23

Links

1

Run groups

Connected tools

2 integrations

  • Zendesk
  • Pipedrive

Canvas controls

Fit wide systems, then zoom into any run group.

Zendesk to Pipedrive Ticket Sync execution lanes1 run groups containing 21 workflow nodes and 23 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.Every day at 09:00. integration node, cron. 0 incoming and 1 outgoing connections.STARTEvery day at 09:00INTEGRATIONCRON0 IN / 1 OUTGet last execution timestamp. transform node, functionItem. 1 incoming and 1 outgoing connections.STEP 02Get last execution timest…TRANSFORMFUNCTIONITEM1 IN / 1 OUTGet tickets updated after last execution. integration node, zendesk. 1 incoming and 1 outgoing connections.STEP 03Get tickets updated after…INTEGRATIONZENDESK1 IN / 1 OUTChannel is email. decision node, if. 1 incoming and 3 outgoing connections.STEP 04Channel is emailDECISIONIF1 IN / 3 OUTSet search email. transform node, set. 1 incoming and 1 outgoing connections.STEP 05Set search emailTRANSFORMSET1 IN / 1 OUTNoOp. integration node, noOp. 1 incoming and 0 outgoing connections.STEP 05NoOpINTEGRATIONNOOP1 IN / 0 OUTRemove duplicates to make search efficient. transform node, itemLists. 1 incoming and 1 outgoing connections.STEP 06Remove duplicates to make…TRANSFORMITEMLISTS1 IN / 1 OUTSearch persons by email. integration node, pipedrive. 1 incoming and 1 outgoing connections.STEP 07Search persons by emailINTEGRATIONPIPEDRIVE1 IN / 1 OUTRename fields and keep only needed fields. transform node, set. 1 incoming and 1 outgoing connections.STEP 08Rename fields and keep on…TRANSFORMSET1 IN / 1 OUTAdd Pipedrive person Id to Zendesk tickets. decision node, merge. 2 incoming and 1 outgoing connections.STEP 09Add Pipedrive person Id t…DECISIONMERGE2 IN / 1 OUTPipedrive person Id found. decision node, if. 1 incoming and 3 outgoing connections.STEP 10Pipedrive person Id foundDECISIONIF1 IN / 3 OUTGet Zendesk comments for tickets. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 11Get Zendesk comments for …INTEGRATIONHTTPREQUEST1 IN / 1 OUTNoOp1. integration node, noOp. 1 incoming and 0 outgoing connections.STEP 11NoOp1INTEGRATIONNOOP1 IN / 0 OUTAdd comments to tickets. decision node, merge. 2 incoming and 1 outgoing connections.STEP 12Add comments to ticketsDECISIONMERGE2 IN / 1 OUTProcess commenst per ticket. integration node, splitInBatches. 2 incoming and 1 outgoing connections.STEP 13Process commenst per ticketINTEGRATIONSPLITINBATCHES2 IN / 1 OUTSplit comments to seperate items. transform node, itemLists. 1 incoming and 1 outgoing connections.STEP 14Split comments to seperat…TRANSFORMITEMLISTS1 IN / 1 OUTNew comment. decision node, if. 1 incoming and 2 outgoing connections.STEP 15New commentDECISIONIF1 IN / 2 OUTAdd comment as a note in Pipedrive. integration node, pipedrive. 1 incoming and 1 outgoing connections.STEP 16Add comment as a note in …INTEGRATIONPIPEDRIVE1 IN / 1 OUTNoOp2. integration node, noOp. 1 incoming and 0 outgoing connections.STEP 17NoOp2INTEGRATIONNOOP1 IN / 0 OUTDone processing. decision node, if. 1 incoming and 2 outgoing connections.STEP 18Done processingDECISIONIF1 IN / 2 OUTSet new last execution timestamp. transform node, functionItem. 1 incoming and 0 outgoing connections.OUTCOMESet new last execution ti…TRANSFORMFUNCTIONITEM1 IN / 0 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.21 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

Every day at 09:00

23 Execution Links

  1. Start

    Every day at 09:00

    Integration

  2. Step 2

    Get last execution timestamp

    Transform

  3. Step 3

    Get tickets updated after last execution

    Integration

  4. Step 4

    Channel is email

    Decision

  5. Step 5

    Set search email

    Transform

    NoOp

    Integration

  6. Step 6

    Remove duplicates to make search efficient

    Transform

  7. Step 7

    Search persons by email

    Integration

  8. Step 8

    Rename fields and keep only needed fields

    Transform

  9. Step 9

    Add Pipedrive person Id to Zendesk tickets

    Decision

  10. Step 10

    Pipedrive person Id found

    Decision

  11. Step 11

    Get Zendesk comments for tickets

    Integration

    NoOp1

    Integration

  12. Step 12

    Add comments to tickets

    Decision

  13. Step 13

    Process commenst per ticket

    Integration

  14. Step 14

    Split comments to seperate items

    Transform

  15. Step 15

    New comment

    Decision

  16. Step 16

    Add comment as a note in Pipedrive

    Integration

  17. Step 17

    NoOp2

    Integration

  18. Step 18

    Done processing

    Decision

  19. Outcome

    Set new last execution timestamp

    Transform

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