Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.flowyble.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Basic settings

FieldDescriptionDefault
NameDisplay name for the agentRequired
DescriptionShort description of what the agent doesOptional
IconBootstrap icon class for visual identificationbi-robot
StatusActive, Inactive, or ArchivedActive

​
LLM Model

Choose which language model powers your agent. Available models vary by provider:
  • Azure OpenAI — GPT-4o, GPT-4o Mini
  • OpenAI — GPT-4o, GPT-4 Turbo, o1, o3
  • Anthropic — Claude Sonnet, Claude Haiku, Claude Opus
Each model has different capabilities, context windows, and credit costs. See Billing & Credits for pricing details.

​
Behavior Prompt

The behavior prompt is the system message sent to the LLM. It defines the agent’s personality, instructions, and constraints. Write it as if you’re briefing a human assistant. 
You are an expert data analyst. When given a dataset description:
1. Identify key patterns and anomalies
2. Suggest relevant visualizations
3. Provide actionable insights

Always cite specific data points in your analysis.
Be concise — limit responses to 500 words.
Be specific about output format, constraints, and edge cases. The more precise your prompt, the more consistent the agent’s behavior.

​
Execution settings

SettingDescriptionDefault
Max StepsMaximum tool-call iterations per run (1–12)8
Conversation MemoryInclude previous messages from the same conversationEnabled
Auto Tool SelectionLet a ToolSelector system agent dynamically pick toolsDisabled

​
Max Steps

Each “step” is one LLM call that results in a tool invocation. If the agent reaches the step limit without finishing, it returns whatever output it has so far. Higher limits allow more complex multi-step reasoning but consume more credits.

​
Conversation Memory

When enabled, the agent receives the full conversation history with each new message. This enables multi-turn interactions where the agent remembers context. Disable it for stateless, one-shot tasks to save tokens.

​
Knowledge Base

Attach a Knowledge Base to give the agent access to your documents. The agent automatically gets a SearchKnowledge tool that performs semantic search over uploaded documents.

​
Attached Tools

Add tools that the agent can call during execution. These can be:
  • Built-in functions — platform-provided utilities
  • Custom tools — workflow automations you’ve built
  • Integration tools — functions from connected services
  • Other agents — invoke another agent as a sub-task