Automate the Coding Agent

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. To call the agent from another system, see 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 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.
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, 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.

Related

• Triggers and results
• Coding Agent
• Coding sessions
• Repositories and pull requests