# Agents
> Part of the NocoDB documentation (Agents). Index of all pages: https://nocodb.com/llms.txt. Any docs page is available as Markdown by adding `.md` to its URL.
URL: https://nocodb.com/docs/agents
Last updated: 2026-10-29
NocoDB agents are AI agents that work in a project: they read and change your tables, documents and code, answer in chat, and run on their own on a trigger.
Create an agent that answers questions about [open deals] and [who owns them]
Create an agent that sums up [last week's new deals] every [Monday] and posts it to [#sales] in Slack
Create an agent that fills in [missing company details] when a [contact] is added
Create a coding agent that fixes [reported bugs] and opens a pull request
NocoDB **agents** are AI agents that work inside a NocoDB project. You give an agent instructions and access, and it reads and changes your tables, documents and code. People chat with the agent. The agent can also run on its own, for example on a schedule or when records change. A form, a webhook call or a Telegram message can also start it.
An agent is a member of its project. It has its own project role, and the records it changes show the agent as the author. Its instructions, access and triggers are settings that you can change at any time.
## Two kinds of agent
NocoDB has two kinds of agent. You pick the kind when you create the agent, and you cannot change it later.
| | General agent | Coding agent |
| ---------------------- | --------------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| **What it does** | Works across your tables, documents and the web. | Works in your GitHub repositories and opens pull requests. |
| **Typical jobs** | Answer questions, write digests, triage requests, fill in records, draft replies. | Fix issues, address review comments, make code changes. |
| **Where it runs** | A managed machine that NocoDB sets up for it. | A machine that you configure, with a new copy for each run. |
| **What it gives back** | A reply in chat, an email, or a Slack message. | A branch and a pull request, with a live preview while it works. |
| **Read more** | [AI Agents](/docs/agents/ai-agents) | [Coding Agent](/docs/agents/coding-agent) |
## Agent or workflow?
A NocoDB [workflow](/docs/workflows) and an agent can both start when a record changes or on a schedule. They suit different jobs.
| Use | When the job |
| -------------- | --------------------------------------------------------------------------------------------------- |
| **A workflow** | Is a fixed sequence of steps: when X happens, set Y, then send Z. Every run does the same thing. |
| **An agent** | Needs judgment: to read records, decide what matters, answer, summarize, triage, draft or fix code. |
## How agents are structured
A NocoDB agent uses the concepts in this table:
| Concept | Description |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Agent** | An AI agent in one project. Each agent has a name, instructions, access and triggers. The mini sidebar of the project lists agents under **Agents**. |
| **Instructions** | What the agent must do, written as you would brief a teammate. See [Instructions and files](/docs/agents/instructions). |
| **Files** | Reference files that the agent reads on every run, for example a price list or a style guide. See [Files](/docs/agents/instructions#files). |
| **Tools and access** | What the agent can read and change: tables and records, documents, and the web. See [Tools and access](/docs/agents/tools-and-access). |
| **Agent role** | The project role of the agent: **Viewer**, **Commenter** or **Editor**. The role limits what the agent can do. See [Roles and permissions](/docs/agents/permissions). |
| **Trigger** | An event that starts the agent without a chat, for example a schedule or a new record. See [Triggers and results](/docs/agents/triggers). |
| **Results** | Where an agent sends what it finds after a triggered run: the chat, an email or a Slack channel. See [Results](/docs/agents/triggers#choose-where-results-go). |
| **Channel** | A chat platform where people can message the agent outside NocoDB. See [Channels](/docs/agents/channels). |
| **Skill** | A reusable set of instructions that the agent loads when it is relevant. See [Skills](/docs/agents/skills). |
| **Session** | One chat with the agent, or one run that a trigger started. See [Chat with an agent](/docs/agents/chat-with-agent). |
| **Repository** | A GitHub repository that a coding agent works in. See [Repositories and code settings](/docs/agents/repositories). |
| **Machine** | The computer that a coding agent runs on, with the languages, databases and tools that your code needs. See [Machines](/docs/agents/machines). |
## Who can do what
Each action on NocoDB agents needs a minimum project role:
| Action | Minimum project role |
| --------------------------------------------------------------- | -------------------- |
| **Create, change, turn on or off, duplicate and delete agents** | **Creator** |
| **Start and open coding sessions** | **Editor** |
| **Chat with an agent and see its triggered runs** | **Viewer** |
For the full list, see [Roles and permissions](/docs/agents/permissions).
## Get started
To start with NocoDB agents, pick the kind of agent:
* **An AI agent for your data:** [create an agent](/docs/agents/create-agent), or start from a [template](/docs/agents/use-cases). Then review its [instructions](/docs/agents/instructions), [access](/docs/agents/tools-and-access) and [triggers](/docs/agents/triggers), and turn it on.
* **A coding agent for your repository:** [set up a coding agent](/docs/agents/coding-agent#set-up-a-coding-agent), and give it a first task. Read [Write good tasks](/docs/agents/write-good-tasks) for better pull requests.
You can also ask [NocoAI](/docs/product/noco-ai) in the chat to create an agent for you. See [Ask NocoAI to create an agent](/docs/agents/create-agent#ask-nocoai-to-create-an-agent).
## Availability
NocoDB agents are available on these plans and editions:
| | Agents |
| ------------------------------------------------------------ | -------------------------------- |
| **NocoDB Cloud, Plus, Business, Scale and Enterprise plans** | General agents and coding agents |
| **NocoDB Cloud, Free plan** | Not available |
| **Self-hosted NocoDB** | Not available |
Agents use the [credits](/docs/product/workspaces/credits) of the workspace. An agent uses credits for its AI model, by token, and for the time its machine runs. Web searches also use credits. Agents that run on an AI integration with your own API key do not use credits for the model: your provider bills you directly.
## Related
* [AI Agents](/docs/agents/ai-agents)
* [Coding Agent](/docs/agents/coding-agent)
* [Use cases and templates](/docs/agents/use-cases)
* [Security](/docs/agents/security)
* [NocoAI](/docs/product/noco-ai)
* [Workflows](/docs/workflows)
---
## Related pages
- [AI Agents](https://nocodb.com/docs/agents/ai-agents.md): NocoDB is a no-code AI agent builder for business: AI agents that work on your tables and documents, answer in chat, and run agentic workflows on triggers.
- [Create an AI Agent](https://nocodb.com/docs/agents/create-agent.md): How to create an AI agent in NocoDB: describe the job in a setup chat or pick a template, then review and turn it on. NocoAI can also build it.
- [AI Agent Use Cases and Templates](https://nocodb.com/docs/agents/use-cases.md): AI agent use cases and examples for sales, customer service, marketing, operations and project management: 13 NocoDB templates to start from.
- [Instructions and Files](https://nocodb.com/docs/agents/instructions.md): Write the instructions of a NocoDB agent as a brief for a teammate, mention tables and documents with @, and attach files that the agent reads on every run.
- [Tools and Access](https://nocodb.com/docs/agents/tools-and-access.md): Set the AI agent tools of a NocoDB agent: what it can read and change in tables, records, documents and the web, its project role and its managed machine.
- [AI Agent Skills](https://nocodb.com/docs/agents/skills.md): Turn on AI agent skills in NocoDB: reusable instructions from the project, workspace or organization catalog that an agent loads when a task needs them.
- [Triggers and Results](https://nocodb.com/docs/agents/triggers.md): Build an AI agent workflow in NocoDB with triggers: a schedule, record changes, comments, forms or webhooks. Send the results to chat, email or Slack.
- [Channels](https://nocodb.com/docs/agents/channels.md): Connect a NocoDB agent to a Telegram channel so people can message it outside NocoDB, and choose which messages it answers and who can reach it.