Skip to Workflow Atlas
Web Automation and ReportingAI systemIntermediate

PG&E Automated Cost Monitoring

PG&E Automated Cost Monitoring is a 14-node automation blueprint connecting PG&E website, Gmail. 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.

14

Nodes

13

Links

1

Run groups

Connected tools

2 integrations

  • PG&E website
  • Gmail

Canvas controls

Fit wide systems, then zoom into any run group.

PG&E Automated Cost Monitoring execution lanes1 run groups containing 14 workflow nodes and 13 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.Schedule Trigger. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTSchedule TriggerTRIGGERSCHEDULETRIGGER0 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 OUTCreate browser window. integration node, airtop. 1 incoming and 1 outgoing connections.STEP 04Create browser windowINTEGRATIONAIRTOP1 IN / 1 OUTType username. integration node, airtop. 1 incoming and 1 outgoing connections.STEP 05Type usernameINTEGRATIONAIRTOP1 IN / 1 OUTType password. integration node, airtop. 1 incoming and 1 outgoing connections.STEP 06Type passwordINTEGRATIONAIRTOP1 IN / 1 OUTClose modal (if any). integration node, airtop. 1 incoming and 1 outgoing connections.STEP 07Close modal (if any)INTEGRATIONAIRTOP1 IN / 1 OUTWait 5 secs. integration node, wait. 1 incoming and 1 outgoing connections.STEP 08Wait 5 secsINTEGRATIONWAIT1 IN / 1 OUTGo to "Energy Usage Details". integration node, airtop. 1 incoming and 1 outgoing connections.STEP 09Go to "Energy Usage Detai…INTEGRATIONAIRTOP1 IN / 1 OUTGo to "Energy Costs". integration node, airtop. 1 incoming and 1 outgoing connections.STEP 10Go to "Energy Costs"INTEGRATIONAIRTOP1 IN / 1 OUTGo to "Electricity and Gas". integration node, airtop. 1 incoming and 1 outgoing connections.STEP 11Go to "Electricity and Gas"INTEGRATIONAIRTOP1 IN / 1 OUTExtract Costs. integration node, airtop. 1 incoming and 2 outgoing connections.STEP 12Extract CostsINTEGRATIONAIRTOP1 IN / 2 OUTEnd session. integration node, airtop. 1 incoming and 0 outgoing connections.OUTCOMEEnd sessionINTEGRATIONAIRTOP1 IN / 0 OUTSend email. Gmail node, gmail. 1 incoming and 0 outgoing connections.OUTCOMESend emailGMAILGMAIL1 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

Schedule Trigger

13 Execution Links
  1. Start

    Schedule Trigger

    Trigger

  2. Step 2

    Variables

    Transform

  3. Step 3

    Create session

    Integration

  4. Step 4

    Create browser window

    Integration

  5. Step 5

    Type username

    Integration

  6. Step 6

    Type password

    Integration

  7. Step 7

    Close modal (if any)

    Integration

  8. Step 8

    Wait 5 secs

    Integration

  9. Step 9

    Go to "Energy Usage Details"

    Integration

  10. Step 10

    Go to "Energy Costs"

    Integration

  11. Step 11

    Go to "Electricity and Gas"

    Integration

  12. Step 12

    Extract Costs

    Integration

  13. Outcome

    End session

    Integration

    Send email

    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.