Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

AI-Powered WhatsApp Support Workflow

AI-Powered WhatsApp Support Workflow is a 11-node automation blueprint connecting OpenAI, WhatsApp Business API, PostgreSQL. Inspect its trigger, execution graph, branches, and implementation requirements.

OpenAIWhatsApp Business APIPostgreSQLLangChain

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.

11

Nodes

10

Links

1

Run groups

Connected tools

4 integrations

  • OpenAI
  • WhatsApp Business API
  • PostgreSQL
  • LangChain

Canvas controls

Fit wide systems, then zoom into any run group.

AI-Powered WhatsApp Support Workflow execution lanes1 run groups containing 11 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.WhatsApp Trigger. trigger node, whatsAppTrigger. 0 incoming and 1 outgoing connections.STARTWhatsApp TriggerTRIGGERWHATSAPPTRIGGER0 IN / 1 OUTAI Agent. ai node, agent. 5 incoming and 1 outgoing connections.STEP 02AI AgentAIAGENT5 IN / 1 OUT24-hour window check. transform node, code. 1 incoming and 1 outgoing connections.STEP 0324-hour window checkTRANSFORMCODE1 IN / 1 OUTIf. decision node, if. 1 incoming and 2 outgoing connections.STEP 04IfDECISIONIF1 IN / 2 OUTcleanAnswer. transform node, code. 1 incoming and 1 outgoing connections.STEP 05cleanAnswerTRANSFORMCODE1 IN / 1 OUTSend Pre-approved Template Message to Reopen the Conversation. integration node, whatsApp. 1 incoming and 0 outgoing connections.STEP 05Send Pre-approved Templat…INTEGRATIONWHATSAPP1 IN / 0 OUTSend AI Agent's Answer. integration node, whatsApp. 1 incoming and 0 outgoing connections.OUTCOMESend AI Agent's AnswerINTEGRATIONWHATSAPP1 IN / 0 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTlist_links. ai node, toolHttpRequest. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1list_linksAITOOLHTTPREQUEST0 IN / 1 OUTget_page. ai node, toolHttpRequest. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1get_pageAITOOLHTTPREQUEST0 IN / 1 OUTPostgres Users Memory. PostgreSQL node, memoryPostgresChat. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Postgres Users MemoryPOSTGRESQLMEMORYPOSTGRESCHAT0 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.11 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

WhatsApp Trigger

6 Execution Links4 Support Dependencies

  1. Start

    WhatsApp Trigger

    Trigger

  2. Step 2

    AI Agent

    AI reasoning

  3. Step 3

    24-hour window check

    Transform

  4. Step 4

    If

    Decision

  5. Step 5

    cleanAnswer

    Transform

    Send Pre-approved Template Message to Reopen the Conversation

    Integration

  6. Outcome

    Send AI Agent's Answer

    Integration

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

4 nodes

  • OpenAI Chat Model

    AI reasoning dependency

  • list_links

    AI reasoning dependency

  • get_page

    AI reasoning dependency

  • Postgres Users Memory

    AI reasoning dependency

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