Trigger Chat

The Trigger Chat node turns a workflow into a conversational AI assistant: it publishes a chat page served by the Floogos engine itself (at /c/<token>) and uses the AI Agent you connect to answer. It’s the fastest way to get a chatbot running: no need to build a frontend or a separate server.

What it does

Exposes a public chat URL (/c/<token>) with its own page, ready to share or embed.
When it receives a user message, it triggers the workflow and returns the connected agent’s answer.
Keeps the conversation (thread memory) so the assistant answers with context.
It is the first node of the flow (a trigger), just like a Webhook or a FormTrigger.

Configuration

Field	Type	Required	Description
agent_name	text	No	Visible assistant name in the chat window (e.g. “Vera”)
greeting	textarea	No	Welcome message the user sees when opening the chat
public_token	text	No	Token of the public URL `/c/<token>`. Generated automatically on publish

How to build it

Place a Trigger Chat node as the workflow start and set the assistant name and greeting.
Add an AI Agent node and connect the Trigger Chat to its input.
Connect the agent’s pieces: a Brain (the LLM that reasons), and optionally tools, RAG and skills.
Publish the workflow. Floogos generates the public_token and the page becomes available at /c/<token>.

The agent gives the answer

Trigger Chat only publishes the chat and triggers the flow: who answers and with what capabilities is defined by the AI Agent you connect. That’s where you choose the LLM provider, the tone (system prompt), which tools it can run and which documentation it answers from (RAG). Start with the AI agent fundamentals.

Output

{
  "success": true,
  "public_token": "a1b2c3d4",
  "chat_url": "/c/a1b2c3d4",
  "message": "Chat published"
}

Use cases

24/7 customer support

An assistant that answers FAQs and hands off to a human when needed.

See case →

Assistant over your documentation

A chat that answers with RAG using your manuals, catalogs or policies.