Generic Chat Assistant
Overview
A ready-to-use conversational AI template powered by Chat Assistant and LLM Agent nodes. Provides a simple chat interface where users can ask questions and receive answers from a large language model, with support for file attachments and graceful error handling.
Generic Chat Assistant
Generic Chat Assistant is a ready-to-use conversational AI template powered by Robomotion's Chat Assistant and LLM Agent nodes. It provides a simple chat interface where users can ask questions and receive answers from a large language model, with no additional configuration required out of the box.
Whether you need a quick internal help desk bot, a knowledge assistant, or a starting point for a more advanced conversational agent, this template gives you a working chat flow in minutes.
What Generic Chat Assistant can do
- Accept user messages through the built-in Chat Assistant UI
- Route questions to an LLM Agent for intelligent responses
- Support file attachments alongside text messages
- Handle unexpected errors gracefully with user-friendly error messages
- Work immediately with Robomotion AI Credits or your own API keys (BYOK)
Behind the scenes
The flow listens for incoming messages through the Chat In node. Each message, along with any attached files, is forwarded to the LLM Agent node, which processes the query and generates a response. The response is then sent back to the user through the Chat Out node. If an error occurs at any point, a Catch node intercepts it and returns a friendly error message instead of failing silently.
Setup Guide
- Configure Credentials: Use Robomotion AI Credits (default) or set up your own API keys in the Vault for a Bring Your Own Key (BYOK) configuration.
- Version & Publish: Create a new version of this flow and Publish it to make it available for deployment.
- Create Agent: Navigate to the Admin Console > Agents screen, create a new agent, and select this flow and its published version.
- Install Desktop App: Download and install the Robomotion Desktop App from robomotion.io/downloads and log in to your workspace.
- Locate Agent: Refresh your robot list in the Desktop App to find the newly created agent for this flow.
- Connect & Start: Connect the robot and press the Play button to start the agent.
- Launch Chat: Return to the Agents screen in the Admin Console, find your agent, and click the Open button to start chatting.
Customization
Double-click the LLM Agent node to update the System Prompt or select skills for your agent. This lets you tailor the assistant's personality, domain knowledge, and capabilities to your specific use case.
More ai templates
See all 10 →- Website Pitch BuilderFinds a shop that has no website and builds it one. Google Maps is searched through the scrape.do API, the listings are filtered down to businesses with a phone, enough reviews to prove they have customers, and no real site of their own - a Facebook page or a Wix subdomain counts as no site - and the best one is scored out. Its opening hours, ten best reviews and four public domain photographs are gathered, and a DeepSeek Agent writes a single self-contained page from that brief and nothing else. A real browser then photographs the page, and the screenshot and a CSV row are mailed to you. Google Maps has no email column, so the packet comes to you with the shop's phone number in it, and a person makes the call.
- Clinic Support AssistantA customer support assistant for a website, served to the page as one MCP tool. A visitor and a signed-in patient are answered by two different Hermes Agents, and the difference is not a prompt or a flag, it is two wires: the visitor's agent is wired to the practice documents and to nothing else, so nothing on that side of the canvas can reach a patient record whatever the model is asked. The signed-in tools take no arguments at all. They read the record number the website established from a session cookie, so the model cannot name a patient, and every turn is written to a dialog log the practice can read in the morning.
- Conversational Order AssistantA conversational chat assistant that takes a return in whatever order the customer explains it. An LLM Agent asks for whatever is missing, and an ordinary automation wired to its tools port looks the order up mid conversation and hands the answer back.
- Guided Returns DeskA guided chat assistant that opens a product return, one question at a time. Uses Chat Assistant widget nodes for the questions, checks the order number while the customer is still in the conversation, and loops back to the question when it does not recognise one instead of throwing an exception.
- Knowledge Base EndpointAsk your own documents a question over HTTP. A Robomotion Knowledge Base is indexed by a workspace agent on your machine and searched locally by the robot; one Query Knowledge Base node returns the passages that answer a question, each with the document and heading it came from. Http In and Http Out turn the flow into a service anything can call, and a Min Score fence means it answers "I could not find that" instead of inventing something. Ships four sample documents and a thirty-line Python client.
- Tax Portal MCP ServerServes an ordinary RPA automation to an AI assistant as MCP tools, so a model can ask a question of a system it could never sign into. One Listen HTTP node makes the flow a stateless MCP server; three Tool In nodes declare the contracts a model reads, with no arguments, one required argument and one optional. Behind them a sign in subflow answers a government portal's tax number, password and one-time code from the vault, and two more subflows read VAT returns, penalties and electronic invoices off the page. The caller is given a bearer token and nothing else, and Tool Out's Is Error flag lets the flow refuse a company it holds no mandate for instead of returning an empty answer the model will fill in for itself.