Building Agents

This chapter unpacks every tab inside Builder so you can craft agents that are reliable, on‑brand, and policy‑compliant. Each subsection ends with pro‑tips distilled from real deployments.

7.1 Basic Tab

Field
Purpose
Best Practice

Agent Name

Display name in dashboards, timeline logs, and Slack notifications.

Use verb‑role patterns (e.g. Invoice‑Bot, QA‑Companion) so teammates grasp the agent's job instantly.

Intro Message

Sets the greeting in chat‑like interfaces & first Slack post.

Keep < 20 words, friendly, mention core function ("Hi, I triage Zendesk tickets.").

Model Selection

Choose foundation model (GPT‑4o, Claude 4.0 Sonnet, Gemini 2.5 Pro, Grok 3, or BYO).

Start with GPT‑4o for balanced cost & quality; downgrade if tokens spike.

Response Length

Hint to the model (Short, Medium, Long).

Medium is safest. Adjust if answers are too terse/verbose.

Save Draft before navigating away this writes the agent record and unlocks downstream tabs.

7.2 Personality Tab

Define tone, formality, emoji usage, and brand voice.

Pro Tip ✨ Match personality to channel. Slack likes informal + emoji; emails require more formality.

7.3 Instructions Tab

This is the agent's "constitution." It combines:

  1. System Prompt – Non‑negotiable rules (security, legal, brand).

  2. Task Prompt – Dynamic instructions passed per task.

  3. Guardrails – Regex or JSON schema the output must satisfy.

Example System Prompt "You are Invoice‑Bot. Never reveal customer PII. If uncertain, ask for clarification."

Validation: The builder auto‑lints for prompt injections and calls out risky phrases.

7.4 Knowledge Tab

Upload documents (PDF, DOCX, TXT), paste URLs, or import SQL rows.

  • Legacy Text Box – Quick notes. Good for < 8 KB snippets.

  • Advanced Ingestion – Document Upload, URL ingestion, MCP integration.

7.5 Tasks Tab

A Task = Agent + Input Payload (JSON). Run one‑offs or queue thousands via bulk CSV.

Column
Meaning

Status

queued → running → succeeded / failed

Timeline

visual trace of tool calls & latencies

Retry Logic: Configure up to 3 auto‑retries for network errors. Combine with Policy Escalations for safety.

7.6 Attaching Tools & Integrations

Navigate to Integrations. Click Sign in to Connect for any tool; once connected it appears in Builder → Tools list and can be referenced in prompts.

Category
MCP Integration

Communication

Slack • Discord

Development & Ops

GitHub • Docker • Terraform • Amazon EKS

Payments

Stripe • PayPal

Databases

PostgreSQL • MongoDB • SupaBase

Cloud Storage

AWS S3 • Google Drive

Cloud Suite

Microsoft 365 / Azure

Docs & Notes

Notion

Networking & Security

CloudFlare

Search & Analytics

Elasticsearch

Automation

Zapier

AI & Data

ElevenLabs • Fire Crawl

Custom

Any REST/GraphQL via Custom API → MCP (email [email protected])

Last updated