Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

Automated Used Car Sales Process

Automated Used Car Sales Process is a 14-node automation blueprint connecting Airtop. Inspect its trigger, execution graph, branches, and implementation requirements.

Airtop

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.

14

Nodes

15

Links

1

Run groups

Connected tools

1 integrations

  • Airtop

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Used Car Sales Process execution lanes1 run groups containing 14 workflow nodes and 15 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.When clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTVariables. transform node, set. 1 incoming and 1 outgoing connections.STEP 02VariablesTRANSFORMSET1 IN / 1 OUTCreate session. integration node, airtop. 1 incoming and 1 outgoing connections.STEP 03Create sessionINTEGRATIONAIRTOP1 IN / 1 OUTLoad website. integration node, airtop. 1 incoming and 1 outgoing connections.STEP 04Load websiteINTEGRATIONAIRTOP1 IN / 1 OUTClick VIN button. integration node, airtop. 1 incoming and 1 outgoing connections.STEP 05Click VIN buttonINTEGRATIONAIRTOP1 IN / 1 OUTWait 7 secs. integration node, wait. 3 incoming and 1 outgoing connections.STEP 06Wait 7 secsINTEGRATIONWAIT3 IN / 1 OUTTake screenshot. integration node, airtop. 1 incoming and 1 outgoing connections.STEP 07Take screenshotINTEGRATIONAIRTOP1 IN / 1 OUTThink next action. integration node, airtop. 1 incoming and 1 outgoing connections.STEP 08Think next actionINTEGRATIONAIRTOP1 IN / 1 OUTParse response. transform node, code. 1 incoming and 1 outgoing connections.STEP 09Parse responseTRANSFORMCODE1 IN / 1 OUTSwitch. decision node, switch. 1 incoming and 3 outgoing connections.STEP 10SwitchDECISIONSWITCH1 IN / 3 OUTType. integration node, airtop. 1 incoming and 1 outgoing connections.STEP 11TypeINTEGRATIONAIRTOP1 IN / 1 OUTClick. integration node, airtop. 1 incoming and 1 outgoing connections.STEP 12ClickINTEGRATIONAIRTOP1 IN / 1 OUTOffer received. transform node, set. 1 incoming and 1 outgoing connections.STEP 13Offer receivedTRANSFORMSET1 IN / 1 OUTTerminate session. integration node, airtop. 1 incoming and 0 outgoing connections.OUTCOMETerminate sessionINTEGRATIONAIRTOP1 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.14 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

When clicking ‘Test workflow’

15 Execution Links

  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    Variables

    Transform

  3. Step 3

    Create session

    Integration

  4. Step 4

    Load website

    Integration

  5. Step 5

    Click VIN button

    Integration

  6. Step 6

    Wait 7 secs

    Integration

  7. Step 7

    Take screenshot

    Integration

  8. Step 8

    Think next action

    Integration

  9. Step 9

    Parse response

    Transform

  10. Step 10

    Switch

    Decision

  11. Step 11

    Type

    Integration

  12. Step 12

    Click

    Integration

  13. Step 13

    Offer received

    Transform

  14. Outcome

    Terminate session

    Integration

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