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

HR & IT Helpdesk AI Chatbot

HR & IT Helpdesk AI Chatbot is a 21-node automation blueprint connecting OpenAI, Telegram, PostgreSQL. Inspect its trigger, execution graph, branches, and implementation requirements.

OpenAITelegramPostgreSQL

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.

21

Nodes

20

Links

2

Run groups

Connected tools

3 integrations

  • OpenAI
  • Telegram
  • PostgreSQL

Canvas controls

Fit wide systems, then zoom into any run group.

HR & IT Helpdesk AI Chatbot execution lanes2 run groups containing 21 workflow nodes and 20 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 clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTHTTP Request. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02HTTP RequestINTEGRATIONHTTPREQUEST1 IN / 1 OUTExtract from File. integration node, extractFromFile. 1 incoming and 1 outgoing connections.STEP 03Extract from FileINTEGRATIONEXTRACTFROMFILE1 IN / 1 OUTCreate HR Policies. ai node, vectorStorePGVector. 3 incoming and 0 outgoing connections.OUTCOMECreate HR PoliciesAIVECTORSTOREPGVECTOR3 IN / 0 OUTEmbeddings OpenAI. OpenAI node, embeddingsOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Embeddings OpenAIOPENAIEMBEDDINGSOPENAI0 IN / 1 OUTDefault Data Loader. ai node, documentDefaultDataLoader. 1 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Default Data LoaderAIDOCUMENTDEFAULTDATALOAD1 IN / 1 OUTRecursive Character Text Splitter. ai node, textSplitterRecursiveCharacterTextSplitter. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2Recursive Character Text …AITEXTSPLITTERRECURSIVECH0 IN / 1 OUTTelegram Trigger. Telegram node, telegramTrigger. 0 incoming and 1 outgoing connections.STARTTelegram TriggerTELEGRAMTELEGRAMTRIGGER0 IN / 1 OUTVerify Message Type. decision node, switch. 1 incoming and 3 outgoing connections.STEP 02Verify Message TypeDECISIONSWITCH1 IN / 3 OUTEdit Fields. transform node, set. 1 incoming and 1 outgoing connections.STEP 03Edit FieldsTRANSFORMSET1 IN / 1 OUTTelegram1. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 03Telegram1TELEGRAMTELEGRAM1 IN / 1 OUTUnsupported Message Type. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 03Unsupported Message TypeTELEGRAMTELEGRAM1 IN / 0 OUTOpenAI. OpenAI node, openAi. 1 incoming and 1 outgoing connections.STEP 04OpenAIOPENAIOPENAI1 IN / 1 OUTAI Agent. ai node, agent. 5 incoming and 1 outgoing connections.STEP 05AI AgentAIAGENT5 IN / 1 OUTTelegram. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMETelegramTELEGRAMTELEGRAM1 IN / 0 OUTAnswer questions with a vector store. ai node, toolVectorStore. 2 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Answer questions with a v…AITOOLVECTORSTORE2 IN / 1 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTPostgres Chat Memory. PostgreSQL node, memoryPostgresChat. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Postgres Chat MemoryPOSTGRESQLMEMORYPOSTGRESCHAT0 IN / 1 OUTPostgres PGVector Store. PostgreSQL node, vectorStorePGVector. 1 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2Postgres PGVector StorePOSTGRESQLVECTORSTOREPGVECTOR1 IN / 1 OUTOpenAI Chat Model1. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2OpenAI Chat Model1OPENAILMCHATOPENAI0 IN / 1 OUTEmbeddings OpenAI1. OpenAI node, embeddingsOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 3Embeddings OpenAI1OPENAIEMBEDDINGSOPENAI0 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.21 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 clicking ‘Test workflow’

3 Execution Links3 Support Dependencies

  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    HTTP Request

    Integration

  3. Step 3

    Extract from File

    Integration

  4. Outcome

    Create HR Policies

    AI reasoning

Attached dependencies

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

3 nodes

  • Embeddings OpenAI

    AI reasoning dependency

  • Default Data Loader

    AI reasoning dependency

  • Recursive Character Text Splitter

    AI reasoning dependency

02

Run Group

Telegram Trigger

8 Execution Links6 Support Dependencies

  1. Start

    Telegram Trigger

    Trigger

  2. Step 2

    Verify Message Type

    Decision

  3. Step 3

    Edit Fields

    Transform

    Telegram1

    Integration

    Unsupported Message Type

    Integration

  4. Step 4

    OpenAI

    AI reasoning

  5. Step 5

    AI Agent

    AI reasoning

  6. Outcome

    Telegram

    Integration

Attached dependencies

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

6 nodes

  • Answer questions with a vector store

    AI reasoning dependency

  • Postgres PGVector Store

    AI reasoning dependency

  • OpenAI Chat Model1

    AI reasoning dependency

  • OpenAI Chat Model

    AI reasoning dependency

  • Postgres Chat Memory

    AI reasoning dependency

  • Embeddings OpenAI1

    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