Concepts
Agent
An AI worker with a role, instructions, and scoped access to your tables, files, and apps.
What a agent is
An agent is hired the way a person is: you write its instructions (the job description), pick its runtime, and grant it access to exactly the data and apps it needs. Agents can be asked things in chat, put on a schedule, given steps in a flow, or wired to a surface so they handle inbound work on their own.
For example
A triage agent reads each new support email, labels the issue, and files a row in the Tickets table.
Reach for it when
- The work needs judgment: drafting, classifying, extracting, summarizing, deciding.
- Inbound items vary too much for fixed rules.
- A person currently does the step by reading and thinking, not by following a checklist.
- You want chat-style help that knows this pod’s data.
Hire your first agent
- Open Agents in the sidebar and create one with a single, narrow job.
- Write instructions like a job description: what comes in, what should go out, what to do when unsure.
- Grant it an access scope — only the tables, folders, and apps the job needs.
- Run it once from chat with a real example before wiring it anywhere.
Where it lives
Agents in the left sidebar. Each agent has Runs, Edit, and History tabs.
Related concepts
| Concept | In short |
|---|---|
| Runtime | The model and harness an agent runs on — pick per agent. |
| Workflow | A repeatable process: steps of agents, functions, decisions, and human approvals that run in order. |
| Surface | A place where work reaches the pod: Slack, Gmail, WhatsApp, Telegram, Teams, Outlook. |
| Function | Deterministic code for steps that shouldn’t be AI judgment: validation, math, formatting. |