Skip to Workflow Atlas
Event-Driven AutomationAI systemIntermediate

AI-Driven Chat Workflow Automation

AI-Driven Chat Workflow Automation is a 11-node automation blueprint connecting OpenAI, Custom API. 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.

11

Nodes

9

Links

2

Run groups

Connected tools

2 integrations

  • OpenAI
  • Custom API

Canvas controls

Fit wide systems, then zoom into any run group.

AI-Driven Chat Workflow Automation execution lanes2 run groups containing 11 workflow nodes and 9 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 chat message received. trigger node, chatTrigger. 0 incoming and 1 outgoing connections.STARTWhen chat message receivedTRIGGERCHATTRIGGER0 IN / 1 OUTAI Agent. ai node, agent. 4 incoming and 0 outgoing connections.OUTCOMEAI AgentAIAGENT4 IN / 0 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTSimple Memory. ai node, memoryBufferWindow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Simple MemoryAIMEMORYBUFFERWINDOW0 IN / 1 OUTActivity Tool. ai node, toolWorkflow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Activity ToolAITOOLWORKFLOW0 IN / 1 OUTWhen Executed by Another Workflow. trigger node, executeWorkflowTrigger. 0 incoming and 1 outgoing connections.STARTWhen Executed by Another …TRIGGEREXECUTEWORKFLOWTRIGGER0 IN / 1 OUTWork out activity type and number of people1. ai node, informationExtractor. 2 incoming and 1 outgoing connections.STEP 02Work out activity type an…AIINFORMATIONEXTRACTOR2 IN / 1 OUTCall the API. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Call the APIINTEGRATIONHTTPREQUEST1 IN / 1 OUTCombine. transform node, aggregate. 1 incoming and 1 outgoing connections.STEP 04CombineTRANSFORMAGGREGATE1 IN / 1 OUTSet 'response' value. transform node, set. 1 incoming and 0 outgoing connections.OUTCOMESet 'response' valueTRANSFORMSET1 IN / 0 OUTOpenAI Chat Model1. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat Model1OPENAILMCHATOPENAI0 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

When chat message received

1 Execution Link3 Support Dependencies
  1. Start

    When chat message received

    Trigger

  2. Outcome

    AI Agent

    AI reasoning

Attached dependencies

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

3 nodes
  • OpenAI Chat Model

    AI reasoning dependency

  • Simple Memory

    AI reasoning dependency

  • Activity Tool

    AI reasoning dependency

02

Run Group

When Executed by Another Workf…

4 Execution Links1 Support Dependency
  1. Start

    When Executed by Another Workflow

    Trigger

  2. Step 2

    Work out activity type and number of people1

    AI reasoning

  3. Step 3

    Call the API

    Integration

  4. Step 4

    Combine

    Transform

  5. Outcome

    Set 'response' value

    Transform

Attached dependencies

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

1 node
  • OpenAI Chat Model1

    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.