Key Concepts

Zaia Endless is built around a set of core concepts. Understanding these will help you design Agents more effectively and avoid unnecessary complexity.


Agent

The central unit of Endless. Defined by Role + Prompt + Settings.

Example: “Assistant specialized in financial client data.” Best practice: Start with the simplest configuration (Role + Prompt), then add Tools or Knowledge only if needed.


Role

A short sentence that summarizes what the Agent does. It helps position the Agent’s purpose.

Example: “Customer support agent for SaaS products.”


Prompt

The main instruction set that defines how the Agent behaves. Supports up to 5000 characters.

Example: “You are a sales assistant. Always ask the customer their name and product of interest. Be polite and concise.”


Temperature

Controls the creativity of the Agent’s responses:

  • 0% → fully methodical (good for factual Agents, e.g., finance, legal).

  • 100% → highly creative (good for brainstorming, marketing ideas).


Effort

Defines how many steps the Agent can take to reach an answer. Range: 10–100.

  • Low effort (10–20): simple tasks, FAQ Agents.

  • High effort (80–100): complex Agents orchestrating multiple Tools and Workflows.


Planning

When enabled, the Agent creates a plan at the start of execution, considering available Tools and resources. Useful for Agents in complex environments.


Supervision

When enabled, the Agent reviews progress and adjusts the plan mid-execution. Useful when the Agent needs multiple iterations or decision-making along the way.


Tools

Extensions that allow the Agent to go beyond the Prompt. Each Tool must be explicitly created and linked.

Examples:

  • Memory Tool → save variables like name, deadline, budget.

  • Table Tools → insert, update, or search in a Table.

  • Workflow Tool → execute a Workflow.

  • Ticket Tool → transfer conversation to a CRM Team.

  • HTTP Tool → connect to APIs.

Best practice: Only add Tools your Agent will actually use.


Knowledge Base (KB)

A structured repository of documents, FAQs, or policies. Agents can search KBs through the Knowledge Base Search Tool.


Tables

Native databases in Zaia Endless. Store and query structured data like leads, CRM records, or inventory.

Operations available via Tools:

  • Insert

  • Update

  • Search

  • Semantic/Similarity Search


Workflows

Sequences of steps that automate business logic. Must be created first, then linked via a Workflow Execution Tool.

Example: “Check product availability → calculate delivery time → return result to user.”


MCP (Managed Connector Provider)

Native integrations with external apps. Require a Connection (OAuth or API Key) to activate.

Examples:

  • Google Calendar → create/list events.

  • Gmail → fetch emails.

  • Supabase → query external databases.

  • Notion/Airtable → manage content.


Connection

Authentication that enables MCPs or channels. Without a Connection, the Agent cannot use the external service.


CRM Team

Groups of humans that can receive conversations from Agents. Must be created before adding a Ticket Tool.


Ticket Tool

The only supported way for Agents to transfer conversations to humans. Always linked to a CRM Team.


Channels

Where the Agent interacts with people.

Available options:

  • Widget (web)

  • WhatsApp

  • Instagram

Best practice: Test first using the internal chat (no channel required), then publish.


Tasks

Conditional rules that trigger instructions.

Examples:

  • If user says “finalize” → deliver Launch Checklist.

  • If user says “I want to talk to a human” → trigger Ticket Tool.

Limits: up to 1000 characters for descriptions. Best practice: Keep tasks specific and avoid overlapping conditions.


Last updated