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

Chart Generation and Google Drive Uploader

Chart Generation and Google Drive Uploader is a 4-node automation blueprint connecting QuickChart, Google Drive. Inspect its trigger, execution graph, branches, and implementation requirements.

QuickChartGoogle Drive

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.

4

Nodes

3

Links

1

Run groups

Connected tools

2 integrations

  • QuickChart
  • Google Drive

Canvas controls

Fit wide systems, then zoom into any run group.

Chart Generation and Google Drive Uploader execution lanes1 run groups containing 4 workflow nodes and 3 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 OUTEdit Fields: Set JSON data to test. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Edit Fields: Set JSON dat…TRANSFORMSET1 IN / 1 OUTQuickChart. integration node, quickChart. 1 incoming and 1 outgoing connections.STEP 03QuickChartINTEGRATIONQUICKCHART1 IN / 1 OUTGoogle Drive: Upload File. Google Drive node, googleDrive. 1 incoming and 0 outgoing connections.OUTCOMEGoogle Drive: Upload FileGOOGLE DRIVEGOOGLEDRIVE1 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.4 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’

3 Execution Links

  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    Edit Fields: Set JSON data to test

    Transform

  3. Step 3

    QuickChart

    Integration

  4. Outcome

    Google Drive: Upload File

    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