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

Confluence AI Chatbot Automation

Confluence AI Chatbot Automation is a 12-node automation blueprint connecting OpenAI, Confluence, Telegram. Inspect its trigger, execution graph, branches, and implementation requirements.

OpenAIConfluenceTelegram

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

11

Links

1

Run groups

Connected tools

3 integrations

  • OpenAI
  • Confluence
  • Telegram

Canvas controls

Fit wide systems, then zoom into any run group.

Confluence AI Chatbot Automation execution lanes1 run groups containing 12 workflow nodes and 11 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, manualChatTrigger. 0 incoming and 1 outgoing connections.STARTWhen chat message receivedTRIGGERMANUALCHATTRIGGER0 IN / 1 OUTGlobals. transform node, set. 1 incoming and 1 outgoing connections.STEP 02GlobalsTRANSFORMSET1 IN / 1 OUTSearch By ID. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Search By IDINTEGRATIONHTTPREQUEST1 IN / 1 OUTSplit Out. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 04Split OutTRANSFORMSPLITOUT1 IN / 1 OUTPage Schema. transform node, set. 1 incoming and 1 outgoing connections.STEP 05Page SchemaTRANSFORMSET1 IN / 1 OUTConfluence Page Storage View. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 06Confluence Page Storage V…INTEGRATIONHTTPREQUEST1 IN / 1 OUTHTML to Markdown. integration node, markdown. 1 incoming and 1 outgoing connections.STEP 07HTML to MarkdownINTEGRATIONMARKDOWN1 IN / 1 OUTAI Agent. ai node, agent. 3 incoming and 2 outgoing connections.STEP 08AI AgentAIAGENT3 IN / 2 OUTSend Telegram Message. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMESend Telegram MessageTELEGRAMTELEGRAM1 IN / 0 OUTChat Response. transform node, set. 1 incoming and 0 outgoing connections.OUTCOMEChat ResponseTRANSFORMSET1 IN / 0 OUTgpt-4o-mini. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1gpt-4o-miniOPENAILMCHATOPENAI0 IN / 1 OUTWindow Buffer Memory. ai node, memoryBufferWindow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Window Buffer MemoryAIMEMORYBUFFERWINDOW0 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

When chat message received

9 Execution Links2 Support Dependencies

  1. Start

    When chat message received

    Trigger

  2. Step 2

    Globals

    Transform

  3. Step 3

    Search By ID

    Integration

  4. Step 4

    Split Out

    Transform

  5. Step 5

    Page Schema

    Transform

  6. Step 6

    Confluence Page Storage View

    Integration

  7. Step 7

    HTML to Markdown

    Integration

  8. Step 8

    AI Agent

    AI reasoning

  9. Outcome

    Send Telegram Message

    Integration

    Chat Response

    Transform

Attached dependencies

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

2 nodes

  • gpt-4o-mini

    AI reasoning dependency

  • Window Buffer 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