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

SQL Dataset Comparison Workflow

SQL Dataset Comparison Workflow is a 5-node automation blueprint connecting MySQL. Inspect its trigger, execution graph, branches, and implementation requirements.

MySQL

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.

5

Nodes

5

Links

1

Run groups

Connected tools

1 integrations

  • MySQL

Canvas controls

Fit wide systems, then zoom into any run group.

SQL Dataset Comparison Workflow execution lanes1 run groups containing 5 workflow nodes and 5 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 "Execute Workflow". trigger node, manualTrigger. 0 incoming and 2 outgoing connections.STARTWhen clicking "Execute Wo…TRIGGERMANUALTRIGGER0 IN / 2 OUTOrders from 2003 and 2004. MySQL node, mySql. 1 incoming and 1 outgoing connections.STEP 02Orders from 2003 and 2004MYSQLMYSQL1 IN / 1 OUTOrders from 2004 and 2005. MySQL node, mySql. 1 incoming and 1 outgoing connections.STEP 02Orders from 2004 and 2005MYSQLMYSQL1 IN / 1 OUTChange ordercount. transform node, set. 1 incoming and 1 outgoing connections.STEP 03Change ordercountTRANSFORMSET1 IN / 1 OUTCompare Datasets. decision node, compareDatasets. 2 incoming and 0 outgoing connections.OUTCOMECompare DatasetsDECISIONCOMPAREDATASETS2 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.5 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 "Execute Workflow"

5 Execution Links

  1. Start

    When clicking "Execute Workflow"

    Trigger

  2. Step 2

    Orders from 2003 and 2004

    Integration

    Orders from 2004 and 2005

    Integration

  3. Step 3

    Change ordercount

    Transform

  4. Outcome

    Compare Datasets

    Decision

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