Skip to Workflow Atlas
ETL PipelineIntermediate

Zendesk-HubSpot Company Sync

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

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.

9

Nodes

10

Links

1

Run groups

Connected tools

2 integrations

  • HubSpot
  • Zendesk

Canvas controls

Fit wide systems, then zoom into any run group.

Zendesk-HubSpot Company Sync execution lanes1 run groups containing 9 workflow nodes and 10 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 last execution timestamp. transform node, functionItem. 1 incoming and 1 outgoing connections.STEP 02Get last execution timest…TRANSFORMFUNCTIONITEM1 IN / 1 OUTGet modified companies. HubSpot node, hubspot. 1 incoming and 2 outgoing connections.STEP 03Get modified companiesHUBSPOTHUBSPOT1 IN / 2 OUTGet all Zendesk organisations. integration node, zendesk. 1 incoming and 1 outgoing connections.STEP 04Get all Zendesk organisat…INTEGRATIONZENDESK1 IN / 1 OUTAdd Zendesk company data to Hubspot data. HubSpot node, merge. 2 incoming and 1 outgoing connections.STEP 05Add Zendesk company data …HUBSPOTMERGE2 IN / 1 OUTCompany exists in Zendesk. decision node, if. 1 incoming and 2 outgoing connections.STEP 06Company exists in ZendeskDECISIONIF1 IN / 2 OUTUpdate organisation. integration node, zendesk. 1 incoming and 1 outgoing connections.STEP 07Update organisationINTEGRATIONZENDESK1 IN / 1 OUTCreate organisation. integration node, zendesk. 1 incoming and 1 outgoing connections.STEP 07Create organisationINTEGRATIONZENDESK1 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.9 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

10 Execution Links
  1. Start

    Every 5 minutes

    Integration

  2. Step 2

    Get last execution timestamp

    Transform

  3. Step 3

    Get modified companies

    Integration

  4. Step 4

    Get all Zendesk organisations

    Integration

  5. Step 5

    Add Zendesk company data to Hubspot data

    Decision

  6. Step 6

    Company exists in Zendesk

    Decision

  7. Step 7

    Update organisation

    Integration

    Create organisation

    Integration

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