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

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.

17

Nodes

19

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 Automation execution lanes1 run groups containing 17 workflow nodes and 19 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 5 minutes. integration node, cron. 0 incoming and 1 outgoing connections.STARTEvery 5 minutesINTEGRATIONCRON0 IN / 1 OUTGet agents and admins. integration node, zendesk. 0 incoming and 1 outgoing connections.STARTGet agents and adminsINTEGRATIONZENDESK0 IN / 1 OUTGet last execution timestamp. transform node, functionItem. 1 incoming and 1 outgoing connections.STEP 02Get last execution timest…TRANSFORMFUNCTIONITEM1 IN / 1 OUTKeep only email and Id. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Keep only email and IdTRANSFORMSET1 IN / 1 OUTGet tickets created after last execution. integration node, zendesk. 1 incoming and 2 outgoing connections.STEP 03Get tickets created after…INTEGRATIONZENDESK1 IN / 2 OUTGet requester information. integration node, zendesk. 1 incoming and 1 outgoing connections.STEP 04Get requester informationINTEGRATIONZENDESK1 IN / 1 OUTKeep only needed requester information. transform node, set. 1 incoming and 1 outgoing connections.STEP 05Keep only needed requeste…TRANSFORMSET1 IN / 1 OUTAdd requester information to ticket data. decision node, merge. 2 incoming and 2 outgoing connections.STEP 06Add requester information…DECISIONMERGE2 IN / 2 OUTSearch requester in pipedrive. integration node, pipedrive. 1 incoming and 1 outgoing connections.STEP 07Search requester in piped…INTEGRATIONPIPEDRIVE1 IN / 1 OUTGet owner information of Pipedrive contact. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 08Get owner information of …INTEGRATIONHTTPREQUEST1 IN / 1 OUTKeep only requester owner email. transform node, set. 1 incoming and 1 outgoing connections.STEP 09Keep only requester owner…TRANSFORMSET1 IN / 1 OUTAdd Pipedrive agent data to pipedrive contact information. decision node, merge. 2 incoming and 1 outgoing connections.STEP 10Add Pipedrive agent data …DECISIONMERGE2 IN / 1 OUTAdd contact owner to ticket data. decision node, merge. 2 incoming and 1 outgoing connections.STEP 11Add contact owner to tick…DECISIONMERGE2 IN / 1 OUTContact exists in Pipedrive. decision node, if. 1 incoming and 2 outgoing connections.STEP 12Contact exists in PipedriveDECISIONIF1 IN / 2 OUTChange assignee to Pipedrive contact owner. integration node, zendesk. 1 incoming and 1 outgoing connections.STEP 13Change assignee to Pipedr…INTEGRATIONZENDESK1 IN / 1 OUTAdd a note requester not found. integration node, zendesk. 1 incoming and 1 outgoing connections.STEP 13Add a note requester not …INTEGRATIONZENDESK1 IN / 1 OUTSet new last execution timestamp. transform node, functionItem. 2 incoming and 0 outgoing connections.OUTCOMESet new last execution ti…TRANSFORMFUNCTIONITEM2 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.17 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 5 minutes

19 Execution Links

  1. Start

    Every 5 minutes

    Integration

    Get agents and admins

    Integration

  2. Step 2

    Get last execution timestamp

    Transform

    Keep only email and Id

    Transform

  3. Step 3

    Get tickets created after last execution

    Integration

  4. Step 4

    Get requester information

    Integration

  5. Step 5

    Keep only needed requester information

    Transform

  6. Step 6

    Add requester information to ticket data

    Decision

  7. Step 7

    Search requester in pipedrive

    Integration

  8. Step 8

    Get owner information of Pipedrive contact

    Integration

  9. Step 9

    Keep only requester owner email

    Transform

  10. Step 10

    Add Pipedrive agent data to pipedrive contact information

    Decision

  11. Step 11

    Add contact owner to ticket data

    Decision

  12. Step 12

    Contact exists in Pipedrive

    Decision

  13. Step 13

    Change assignee to Pipedrive contact owner

    Integration

    Add a note requester not found

    Integration

  14. 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