# Automate the Coding Agent > 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/automate-coding Last updated: 2026-10-29 Automate a NocoDB coding agent with schedules, record triggers and webhooks, for automated bug fixing and AI agent orchestration of up to 3 parallel runs. A trigger starts a NocoDB coding agent run without a chat. Each triggered run starts a coding session on the repository that the trigger names. For example, a coding agent can update dependencies every Monday, or start work when a bug record is created in a table. ## Add a trigger to a coding agent You add a trigger to a NocoDB coding agent the same way as to any agent: 1. Open the coding agent. 2. In the top bar, click **Settings**. 3. Go to **Triggers**. 4. Click **Add trigger**. 5. Select the trigger type, and set its options. 6. In **Repository**, keep **Default**, or select another repository of the agent. 7. Click **Add trigger**. For the trigger types and their options, see [Trigger types](/docs/agents/triggers#trigger-types). To call the agent from another system, see [Run an agent from a webhook](/docs/agents/triggers#run-an-agent-from-a-webhook). ## Which triggers start a coding run A trigger on a NocoDB coding agent starts a coding session. Each trigger has a **Repository** option: the **Default** repository of the agent, or one of its other repositories. Some rules apply only to coding agents: * A schedule always starts a coding run. Another trigger starts a coding run only when the member or agent that fired it has the **Editor** role or higher. For example, a public form submission, or a webhook call with the token of a **Viewer**, does not start one. * A [channel](/docs/agents/channels) message does not start a coding run. * An agent can have up to 3 triggered coding runs at the same time. * When you remove a repository, its triggers run on the default repository. ## Fix bugs automatically from a Bugs table Automated bug fixing with a NocoDB coding agent can start from a table of bug reports. A **When record created** trigger on a `Bugs` table starts a coding run for each new bug record. The run gets the record that was created. 1. Add a trigger to the coding agent. See [Add a trigger to a coding agent](#add-a-trigger-to-a-coding-agent). 2. Select **When record created**. 3. In **Table**, select the `Bugs` table. 4. In **Repository**, select the repository of the code. The trigger starts a coding run only when the member who created the record has the **Editor** role or higher. ## AI agent orchestration with triggers AI agent orchestration in NocoDB uses triggers to run several coding runs side by side. An agent can have up to 3 triggered coding runs at the same time. Each run works on its own branch and starts on a fresh copy of the [machine](/docs/agents/machines), so runs do not affect each other. ## Where the results go A triggered coding run has no **Results go to** setting. The result is the session and the work on its branch. A session that a trigger started has no owner. Members can watch it, but nobody can send it messages. See [Who can work in a session](/docs/agents/coding-sessions#who-can-work-in-a-session). ## Related * [Triggers and results](/docs/agents/triggers) * [Coding Agent](/docs/agents/coding-agent) * [Coding sessions](/docs/agents/coding-sessions) * [Repositories and pull requests](/docs/agents/repositories) --- ## Related pages - [Agents](https://nocodb.com/docs/agents.md): 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. - [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.