Skip to Workflow Atlas
Event-Driven AutomationAI systemIntermediate

Automated Zoom & Stripe Workflow

Automated Zoom & Stripe Workflow is a 16-node automation blueprint connecting Zoom, Stripe, 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.

16

Nodes

15

Links

1

Run groups

Connected tools

4 integrations

  • Zoom
  • Stripe
  • Gmail
  • Google Sheets

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Zoom & Stripe Workflow execution lanes1 run groups containing 16 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.Creation Form. trigger node, formTrigger. 0 incoming and 1 outgoing connections.STARTCreation FormTRIGGERFORMTRIGGER0 IN / 1 OUTOn payment. Stripe node, stripeTrigger. 0 incoming and 1 outgoing connections.STARTOn paymentSTRIPESTRIPETRIGGER0 IN / 1 OUTConfig. transform node, set. 2 incoming and 1 outgoing connections.STEP 02ConfigTRANSFORMSET2 IN / 1 OUTif is creation flow. decision node, if. 1 incoming and 2 outgoing connections.STEP 03if is creation flowDECISIONIF1 IN / 2 OUTCreate Zoom meeting. integration node, zoom. 1 incoming and 1 outgoing connections.STEP 04Create Zoom meetingINTEGRATIONZOOM1 IN / 1 OUTFormat participant. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Format participantTRANSFORMSET1 IN / 1 OUTCreate Stripe Product. Stripe node, httpRequest. 1 incoming and 1 outgoing connections.STEP 05Create Stripe ProductSTRIPEHTTPREQUEST1 IN / 1 OUTAdd participant to list. Google Sheets node, googleSheets. 1 incoming and 1 outgoing connections.STEP 05Add participant to listGOOGLE SHEETSGOOGLESHEETS1 IN / 1 OUTCreate payment link. integration node, httpRequest. 1 incoming and 2 outgoing connections.STEP 06Create payment linkINTEGRATIONHTTPREQUEST1 IN / 2 OUTSend confirmation to participant. Gmail node, gmail. 1 incoming and 1 outgoing connections.STEP 06Send confirmation to part…GMAILGMAIL1 IN / 1 OUTFormat event. transform node, set. 1 incoming and 1 outgoing connections.STEP 07Format eventTRANSFORMSET1 IN / 1 OUTCreate participant list. Google Sheets node, googleSheets. 1 incoming and 1 outgoing connections.STEP 07Create participant listGOOGLE SHEETSGOOGLESHEETS1 IN / 1 OUTNotify teacher. Gmail node, gmail. 1 incoming and 1 outgoing connections.STEP 07Notify teacherGMAILGMAIL1 IN / 1 OUTStore event. Google Sheets node, googleSheets. 1 incoming and 0 outgoing connections.OUTCOMEStore eventGOOGLE SHEETSGOOGLESHEETS1 IN / 0 OUTSend email to teacher. Gmail node, gmail. 1 incoming and 0 outgoing connections.OUTCOMESend email to teacherGMAILGMAIL1 IN / 0 OUTthe end. integration node, noOp. 1 incoming and 0 outgoing connections.OUTCOMEthe endINTEGRATIONNOOP1 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.16 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

Creation Form

15 Execution Links
  1. Start

    Creation Form

    Trigger

    On payment

    Trigger

  2. Step 2

    Config

    Transform

  3. Step 3

    if is creation flow

    Decision

  4. Step 4

    Create Zoom meeting

    Integration

    Format participant

    Transform

  5. Step 5

    Create Stripe Product

    Integration

    Add participant to list

    Integration

  6. Step 6

    Create payment link

    Integration

    Send confirmation to participant

    Integration

  7. Step 7

    Format event

    Transform

    Create participant list

    Integration

    Notify teacher

    Integration

  8. Outcome

    Store event

    Integration

    Send email to teacher

    Integration

    the end

    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.