VERAGEN
Sign in Sign up

Agentic Workflows

Chatbots, and Test chat

A workflow can answer people in a conversation. Start it with a Chat message block and end it with a Reply block. In between, add what it needs to answer — usually Project context for your documents, then an Agent / LLM that writes the answer.

The blocks

  • Chat message starts the workflow when someone sends a message. Every Agent after it is given that message and the conversation so far, so its prompt only needs to say how to answer. {{message}} in a prompt is the message itself.
  • Reply sends an answer back. By default it sends the previous step's answer, {{result}}.

Test chat

  1. Click Test chat in the editor's top bar.
  2. Type a message, the way a visitor would.

Each message saves the workflow, runs it and shows the reply. Under each reply: how many steps ran, what it cost, and View run for the full run. Start over begins a new conversation.

If the workflow has no Chat message or Reply block yet, the panel offers Set up for chat: it turns a Manual trigger into a Chat message block and adds a Reply after your Agent. Sending a message does the same for you.

Each test message is a real run: it is charged like one and listed in History.

Putting it on your website

Click Embed in the top bar (or Put it on a website… in the Test chat panel).

  1. List the websites it may appear on, one per line, such as example.com — up to 10. A site includes its subdomains, so example.com covers www.example.com. On any other site the chatbot does not appear.
  2. Choose the name at the top of the chat, a colour and an optional first message.
  3. Set the daily spending limit ($0.50 to $100, default $5.00) and messages per visitor, per 10 minutes (default 20). Answers are paid from your account's credit.
  4. Read the list of what visitors can ask about — everything its Project context and Fetch web pages blocks read — and tick the box.
  5. Click Publish.

Copy the code it shows. In WordPress, add a Custom HTML block to a page and paste it in; to show it on every page, paste it into your theme's footer or a header-and-footer plugin. On other sites, paste it just before </body>, or into the site builder's custom code box. A chat bubble appears in the bottom-right corner.

The chatbot answers with the workflow as it was when you published it. After you change the workflow, open Embed and click Update. Pause stops it answering until you Resume; Unpublish takes it off every site.

Account owners and admins, the project's owner, and the person who made the workflow can publish it. Anyone else who can open the project can test it.

A public chatbot can only read and answer. A workflow with a block that sends email, posts to Slack, calls a URL, saves into a project, crawls, loops, fans out, waits for a person or posts through Beacon cannot be published. Nothing visitors type is stored; only the number of messages and the cost are kept, shown in Observability as Chatbots on your websites.

What visitors may see

That's a lot of messages at once. Give it a few minutes and try again.One visitor reached the messages-per-10-minutes limit.
This chat has answered all it can for today. Please come back tomorrow.The daily spending limit is used up.
This chat is paused right now. Please try again later.You paused it, or the account is out of credit.
Speak instead of typing. The boxes here that the AI reads have a microphone beside them: press it, talk, and pause; the text lands in the box for you to check. Speaking instead of typing

Signed in to VeraGen? Press Guide me on any screen for a walkthrough, or ask Odin.