Skip to Workflow Atlas
Event-Driven AutomationIntermediate

WhatsApp Business Notification Bot

WhatsApp Business Notification Bot is a 12-node automation blueprint connecting WhatsApp API, Google Sheets. 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.

12

Nodes

10

Links

3

Run groups

Connected tools

2 integrations

  • WhatsApp API
  • Google Sheets

Canvas controls

Fit wide systems, then zoom into any run group.

WhatsApp Business Notification Bot execution lanes3 run groups containing 12 workflow nodes and 10 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.Get new entries. Google Sheets node, googleSheetsTrigger. 0 incoming and 1 outgoing connections.STARTGet new entriesGOOGLE SHEETSGOOGLESHEETSTRIGGER0 IN / 1 OUTUser consented for WA messages?. decision node, filter. 1 incoming and 1 outgoing connections.STEP 02User consented for WA mes…DECISIONFILTER1 IN / 1 OUTSent notification template. integration node, whatsApp. 1 incoming and 0 outgoing connections.OUTCOMESent notification templateINTEGRATIONWHATSAPP1 IN / 0 OUTWhatsApp Trigger. trigger node, whatsAppTrigger. 0 incoming and 1 outgoing connections.STARTWhatsApp TriggerTRIGGERWHATSAPPTRIGGER0 IN / 1 OUTIs message?. decision node, if. 1 incoming and 1 outgoing connections.STEP 02Is message?DECISIONIF1 IN / 1 OUTNew message from the user. Google Sheets node, googleSheets. 1 incoming and 0 outgoing connections.OUTCOMENew message from the userGOOGLE SHEETSGOOGLESHEETS1 IN / 0 OUTSchedule Trigger. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTSchedule TriggerTRIGGERSCHEDULETRIGGER0 IN / 1 OUTGet new answers. Google Sheets node, googleSheets. 1 incoming and 1 outgoing connections.STEP 02Get new answersGOOGLE SHEETSGOOGLESHEETS1 IN / 1 OUTLoop Over Items. integration node, splitInBatches. 2 incoming and 1 outgoing connections.STEP 03Loop Over ItemsINTEGRATIONSPLITINBATCHES2 IN / 1 OUTReply to the user. integration node, whatsApp. 1 incoming and 1 outgoing connections.STEP 04Reply to the userINTEGRATIONWHATSAPP1 IN / 1 OUTUpdate message status. Google Sheets node, googleSheets. 1 incoming and 1 outgoing connections.STEP 05Update message statusGOOGLE SHEETSGOOGLESHEETS1 IN / 1 OUTWait 1 sec. integration node, wait. 1 incoming and 1 outgoing connections.OUTCOMEWait 1 secINTEGRATIONWAIT1 IN / 1 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.12 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

Get new entries

2 Execution Links
  1. Start

    Get new entries

    Trigger

  2. Step 2

    User consented for WA messages?

    Decision

  3. Outcome

    Sent notification template

    Integration

02

Run Group

WhatsApp Trigger

2 Execution Links
  1. Start

    WhatsApp Trigger

    Trigger

  2. Step 2

    Is message?

    Decision

  3. Outcome

    New message from the user

    Integration

03

Run Group

Schedule Trigger

6 Execution Links
  1. Start

    Schedule Trigger

    Trigger

  2. Step 2

    Get new answers

    Integration

  3. Step 3

    Loop Over Items

    Integration

  4. Step 4

    Reply to the user

    Integration

  5. Step 5

    Update message status

    Integration

  6. Outcome

    Wait 1 sec

    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.