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

Zendesk-HubSpot Ticket Sync

Zendesk-HubSpot Ticket Sync is a 13-node automation blueprint connecting Zendesk, HubSpot. Inspect its trigger, execution graph, branches, and implementation requirements.

ZendeskHubSpot

Interactive system map

Execution flows, separated by connected path.

Each horizontal lane is one connected flow. Solid lines show runtime execution; dashed lines show AI, model, memory, or tool dependencies.

13

Nodes

14

Links

1

Flows

Connected tools

2 integrations

  • Zendesk
  • HubSpot
Zendesk-HubSpot Ticket Sync execution lanes1 connected flows containing 13 workflow nodes and 14 visible links. Solid lines are execution links and dashed lines are support dependencies. Focus any node to inspect its immediate path.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 updated after last execution. integration node, zendesk. 1 incoming and 2 outgoing connections.Get tickets updated after…INTEGRATIONZENDESK1 IN / 2 OUTGet user data of Ticket requester. integration node, zendesk. 1 incoming and 1 outgoing connections.Get user data of Ticket r…INTEGRATIONZENDESK1 IN / 1 OUTOnly keep needed data. transform node, set. 1 incoming and 1 outgoing connections.Only keep needed dataTRANSFORMSET1 IN / 1 OUTAdd user data. decision node, merge. 2 incoming and 1 outgoing connections.Add user dataDECISIONMERGE2 IN / 1 OUTTicket Exists. decision node, if. 1 incoming and 2 outgoing connections.Ticket ExistsDECISIONIF1 IN / 2 OUTUpdate existing ticket. HubSpot node, hubspot. 1 incoming and 1 outgoing connections.Update existing ticketHUBSPOTHUBSPOT1 IN / 1 OUTCreate or update contact. HubSpot node, hubspot. 1 incoming and 1 outgoing connections.Create or update contactHUBSPOTHUBSPOT1 IN / 1 OUTUpdate External Id in Zendesk for contact. integration node, zendesk. 1 incoming and 1 outgoing connections.Update External Id in Zen…INTEGRATIONZENDESK1 IN / 1 OUTCreate new Ticket. HubSpot node, hubspot. 1 incoming and 1 outgoing connections.Create new TicketHUBSPOTHUBSPOT1 IN / 1 OUTUpdate Zendesk ticket with External Id. integration node, zendesk. 1 incoming and 1 outgoing connections.Update Zendesk ticket wit…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 OUT

Signal inspector

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

Execution linkSupport dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.13 connected nodesEnter or click to lock · Escape to clear

Execution breakdown

Follow each connected flow from start to outcome.

The readable view below uses the same graph relationships as the interactive map. Each row is a connected flow; columns advance only when an actual link connects the nodes.

01

Connected Flow

Every 5 minutes

14 Execution Links

  1. Start

    Every 5 minutes

    Integration

  2. Step 2

    Get last execution timestamp

    Transform

  3. Step 3

    Get tickets updated after last execution

    Integration

  4. Step 4

    Get user data of Ticket requester

    Integration

  5. Step 5

    Only keep needed data

    Transform

  6. Step 6

    Add user data

    Decision

  7. Step 7

    Ticket Exists

    Decision

  8. Step 8

    Update existing ticket

    Integration

    Create or update contact

    Integration

  9. Step 9

    Update External Id in Zendesk for contact

    Integration

  10. Step 10

    Create new Ticket

    Integration

  11. Step 11

    Update Zendesk ticket with External Id

    Integration

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