The AI Chat Agent Node: Answer Questions From Your Knowledge Base

Most blocks do one thing and move on. This one stays. Drop an AI Chat Agent block on the canvas and it reads what the person types, answers in its own words, and keeps listening until the conversation ends.

Two things make the answers worth reading. A knowledge base — documents you upload — gives it facts instead of guesses. Intents give it exits. An intent is a kind of request you want to catch, such as "where is my order". When a message matches one, the agent hands the conversation to a normal block on the canvas.

Add it from the + button on the canvas. On the node you will see one row per intent, plus small tags for the attached knowledge base and the mode. Each of those rows is a real output you can wire somewhere.

Click the block and the editor opens on the left. Under the block name sits Agent mode, and it decides what the rest of the editor shows:

• Chat Only — the agent only answers. No branches, no routing.
• Intents + Chat — it answers, and routes when the message matches one of your intents. This is what most support bots want.
• Intents Only — no answers at all. It only decides which intent fits and sends the person down that path. The Knowledge section disappears, because nothing is written.

Documents do not live in the block. They live in the workspace, so several blocks and several flows can share them.

Open Settings → AI in the left menu (the page is titled AI Settings). Scroll to Knowledge bases and press New knowledge base. Then fill it three ways:

• Upload document — TXT, Markdown, JSON, CSV, TSV, XML, YAML, PDF, DOC, DOCX and XLSX. The accepted list is printed above the buttons, so you never have to guess.
• Create document — type or paste the text in the browser. Good for a FAQ that only exists in someone's head.
• Import from website — paste your website address and FlowCastle reads the pages itself, one document per page. Usually the fastest way to fill a base, because the answers are already written on your site. Turn Your Website Into a Knowledge Base walks through it.

A new document is not searchable the moment it finishes uploading. FlowCastle first reads it and prepares it for search. While that runs you see the current stage. When it stops you see one of four statuses — Queued, Processing, Ready, Failed — and, next to the file name, how many pieces the document was split into. The four counters above the table (Documents, Ready, Processing, Failed) are the quick version. Only Ready documents are searched.

Edited a document? Reindex prepares that one file again. Reindex all does it for the whole base.

Back in the flow, open the block and go to the Settings tab.

Expand Knowledge. Knowledge bases is a multi-select — pick one or several. What you pick here is what the agent searches on every single turn.

Two fields above it matter just as much.

System prompt, under System Prompt, is the standing instruction the model reads before every answer: who it is and how it should reply. You get three choices: Inherit application prompt uses the workspace-wide prompt from that same AI Settings page, Extend application prompt keeps it and appends your instructions, Override prompt replaces it entirely. This is where you write the sentence that keeps the bot honest: answer only from the knowledge base, and say so when the answer is not there.

AI model, under AI Models, sits next to a Balance: 82/100 credits notice. Leave it on Auto unless you have a reason not to. Each option shows its price compared with the standard AI price: Auto shows 0.50x, which means half price. Web search underneath lets supported models look things up online; it stays greyed out on models that cannot.

Switch to the Intents tab. Every intent is a card: an on/off switch, a name, a description.

The description is the whole trick. Nobody sees it — it is what the model reads to decide whether this intent fits. Write it as a sentence about the person, not about your bot: "The customer asks where an order is, or asks about delivery status of an order they already placed."

Each card has two checkboxes. Show as quick reply turns the intent name into a tappable suggestion. Continue AI agent session after completion sends the person back to the agent after the branch has run, instead of dropping them out of the conversation.

Add Intent creates an empty card. The button under it opens a drawer of ready-made examples grouped by business type, so you can start from "Track order" or "Talk to an operator" instead of a blank field.

Nothing routes until you wire it. Every enabled intent grows its own output on the node, labelled with the intent name — drag it to any block. A "talk to a person" intent usually points at an Action block holding the Start Conversation action, which opens a conversation in Live Chat so someone on your team can reply.

Open the Fallback section. When no intent matches has three answers:

• Stop processing — the agent goes quiet and the flow ends.
• Send a fallback message — one message you write, then stop.
• Hand off to another block — the node grows an extra No Match output. Connect it wherever unanswered questions should land, usually the same handoff block your "talk to a person" intent uses.

Below it is Frustration Detection. It notices when a person is getting upset and reacts before they give up.

1. Turn the switch on.
2. Set Frustration threshold (0.7 by default). Lower reacts sooner. Higher reacts only when the person is clearly angry. Asking for a human counts as very upset.
3. Pick When frustration detected: Stop processing, Send a fallback message (you write a calming message), or Hand off to another block.
4. If you chose the hand-off, the block gets a Frustration output. Connect it to your "talk to a person" block.

Press Test above the canvas and use the Chat tab. Ask the question your documents answer and read what comes back. If the reply is vague, the fix is almost always the document, not the prompt — the agent can only be as specific as what it was given.

The third tab is Suggestions. Once the bot has handled real chats, Analyze conversations reads back through them. Choose the source — Agent history (unmatched messages) or Live chat conversation history — pick a window, and press Run analysis.

What comes back is grouped into four kinds: New intent (people keep asking something you never routed), Improve intent, Unused intent and Knowledge gap (a question your documents do not answer). Each suggestion shows how many of the analysed messages it covers, plus the real sentences behind it. Accept turns a suggested intent into a real one; Add to knowledge base writes a question-and-answer pair straight into a base, and it warns you first if an existing base already covers it.

Three things in FlowCastle call a model. They are not interchangeable.

The AI Chat Agent block is a conversation: it waits for replies, remembers the turn before, searches your documents and can route. Reach for it when the person is going to ask more than one thing.

The AI Action is a single shot inside an Action block — one prompt, one result, stored in a variable, no memory and no routing. Use it to summarise a message or classify an answer mid-flow. The Action Node: Everything Your Bot Can Do covers where it lives.

The OpenAI module adds an Ask ChatGPT action that runs on your own OpenAI key. Also one shot, no knowledge base, no intents — the reason to install it is that you want to bring your own key.

Two ready flows use this block, and both install in one click:

• AI FAQ Assistant + Human Handoff — a support bot that answers order, delivery and return questions from a knowledge base and passes the hard ones to a person.
• Website Chat Assistant (EN/RU) — the bilingual assistant that runs in the chat widget on flowcastle.ai. Pair it with Embed Web Chat on Your Site.

If your bot also sells, Accept Payments in Telegram: Stars and Card Providers is the other half of the same conversation.

Back to the main path — the outside services your bot can plug into: Modules: Connect Sheets, AI, Payments and More.