Workflows and Automation with NocoDB MCP

An MCP client can build NocoDB workflows step by step, test and publish them, and read their runs. It can also manage webhooks, scripts and automation folders, and set up agents, talk to them and read what they did.

These 60 tools are in the Automation section of Tools & Permissions. A tool needs the access level in its row: Read, Read & write, or Read, write & delete. Two more tools, executeWorkflow and testHook, are opt-in tools: a connection gets them only when you switch them on.

How the assistant works with workflows

Read and write workflow drafts. Add nodes and test nodes. Publish an automation after all its nodes are tested.

List, read, create, update, and delete scripts.

A test of a workflow node over MCP is a check, not a run. The node does not do its action. For example, a create-record node writes no row, and a messaging node sends nothing. NocoDB resolves the node configuration against the results of the nodes before it and checks it with read-only calls. The result shows as simulated.

Some nodes can only be checked with a real run, for example a script step or a node that declares no outputs. For these nodes, the test fails and MCP cannot clear the failure. You cannot publish until someone runs that step in the automation editor.

executeWorkflow runs a published automation for real, so its steps write records, call external services and send messages. It is an opt-in tool, off until you switch it on for the connection.

Manage webhooks.

Tools

Workflows

Needs workflows on your plan. Without it, these tools are not offered.

ToolWhat it doesAccess level
listWorkflowsList the automations (workflows) of the current project.Read
getWorkflowGet one automation, including its editable draft graph and the published nodes/edges.Read
listWorkflowNodeTypesList automation node types available here: id, title, category, description, icon, ports, requiredConfigKeys, hidden status, and plan lock status.Read
getWorkflowAuthoringInstructionsHow to author an automation draft over this API: graph shape, trigger and edge rules, expression syntax, and what is rejected.Read
listExecutionsList past runs of an automation.Read
getExecutionGet one run of an automation, including its node results.Read
createWorkflowCreate an automation.Read & write
updateWorkflowUpdate an automation's title, description or draft graph.Read & write
duplicateWorkflowDuplicate an automation into the same project.Read & write
publishWorkflowPublish an automation: the tested draft becomes the live version and starts running for real on its trigger.Read & write
deleteWorkflowDelete an automation.Read, write & delete
executeWorkflowRun the published version of an automation now, with optional inputs for its trigger. This is a real run: its nodes write records, call external services and send messages. NocoDB refuses the run when the automation is turned off. The run is queued, so read its outcome with getExecution.Opt-in

Workflow steps

Needs workflows on your plan. Without it, these tools are not offered.

ToolWhat it doesAccess level
addWorkflowNodeAdd one node to an automation's draft.Read & write
updateWorkflowNodeUpdate one node of an automation's draft.Read & write
connectWorkflowNodesAdd one edge to an automation's draft.Read & write
disconnectWorkflowNodesRemove the edge between two nodes of an automation's draft.Read & write
validateWorkflowNodeTest one node of an automation and store the result, which is what the validate flag on the node-editing tools does, and what publish requires of every node.Read & write
deleteWorkflowNodeDelete one node from an automation's draft.Read, write & delete

Webhooks

Needs webhooks in MCP on your plan. Without it, these tools are not offered.

ToolWhat it doesAccess level
listHooksList webhooks of a table.Read
getHookGet a webhook by ID.Read
createHookCreate a webhook on a table.Read & write
updateHookUpdate an existing webhook.Read & write
deleteHookDelete a webhook.Read, write & delete
testHookFire a webhook once, as configured, with a sample payload built from its table. This is a real request to the hook URL, or a real email or message for other notification types, and the hook log records it.Opt-in

Scripts

Needs scripts in MCP on your plan. Without it, these tools are not offered.

ToolWhat it doesAccess level
listScriptsList NocoDB scripts in a project.Read
getScriptGet a NocoDB script by ID.Read
getScriptAuthoringInstructionsHow to write the source for a NocoDB script: the runtime globals, the record read/write API, and the silent-failure modes the generated editor typings do not mention.Read
createScriptCreate a new NocoDB script.Read & write
updateScriptUpdate an existing NocoDB script.Read & write
duplicateScriptDuplicate a script into the same project.Read & write
restoreScriptRestore a script from the project trash.Read & write
deleteScriptMove a script to the project trash.Read, write & delete

Automation folders

Needs folders on your plan. Without it, these tools are not offered.

ToolWhat it doesAccess level
listAutomationFoldersList the automation folders of the current project with the workflows and scripts inside each, plus the unfoldered automations under topLevel.Read
createAutomationFolderCreate an automation folder in the current project.Read & write
updateAutomationFolderRename an automation folder or change its order.Read & write
moveAutomationToFolderMove a workflow or script into an automation folder, or back to the top level with folderId: null.Read & write
deleteAutomationFolderDelete an automation folder.Read, write & delete

Agents

Needs agents on your plan. Without it, these tools are not offered. Creating, changing and deleting agents and their channels needs the Creator role or a higher role in the project.

A turn runs in the background. Poll getAgentSession until its turn is no longer running, then read the reply with listAgentMessages.

ToolWhat it doesAccess level
listAgentsList the agents of the current project, with their roles and channels.Read
getAgentGet one agent: its instructions, tools, triggers, delivery and, for a coding agent, its code settings.Read
listAgentSessionsList the conversations and triggered runs of an agent.Read
getAgentSessionWhere the turn of one session stands: idle, running, waiting for a person to approve the tools that it named, or failed.Read
listAgentMessagesRead the messages of one agent session. The messages of a coding turn are written when it ends.Read
sendAgentMessageSend a message to an agent, in a new session or an existing one. For a coding agent this works on its default repository.Read & write
stopAgentSessionStop the turn that a session is running. The session stays, so another message carries on from there. You can stop a session that you started, and a Creator can stop the coding session of anyone.Read & write
createAgentCreate an agent in a project.Read & write
updateAgentUpdate an agent. The change applies at once, with no separate publish step.Read & write
duplicateAgentCopy an agent with its instructions, tools, triggers and, for a coding agent, its repositories.Read & write
createAgentChannelConnect an agent to a channel, for example Slack or Telegram, through a channel integration of the workspace.Read & write
updateAgentChannelRename an agent channel, switch it off, or change its settings.Read & write
testAgentChannelCheck the connection of an agent channel to its platform, without sending a message.Read & write
deleteAgentMove an agent to the project trash.Read, write & delete
deleteAgentChannelDisconnect an agent from a channel. The integration stays.Read, write & delete

Coding agents

Needs coding agents on your plan, and they run on NocoDB Cloud only. Without them, these tools are not offered. Listing the repositories of an agent, starting a session and reading its changes need the Editor role or a higher role in the project. Launching an agent, finding repositories and their tasks, and changing the repositories of an agent need the Creator role or higher.

ToolWhat it doesAccess level
listAgentReposList the GitHub repositories of a coding agent. A session starts on the default one unless it names another.Read
listAvailableReposList the repositories that a GitHub App connection of the workspace can reach.Read
listRepoTasksList the open issues and pull requests of a repository, to start a session from.Read
getCodingSessionDiffGet everything that a coding session changed, as one patch, with its branch and its commits. A large patch is cut at file boundaries and names the files that it left out.Read
launchCodingAgentCreate a coding agent ready to run: its repositories, its machine and its first session, in one call.Read & write
startCodingSessionStart a coding session on one of the repositories of the agent. It starts from the start branch of the repository unless it names a branch, an issue or a pull request.Read & write
addAgentRepoAdd a GitHub repository to a coding agent. The first repository becomes the default and starts a setup session that installs the project.Read & write
setDefaultAgentRepoMake a repository the default of a coding agent, where sessions and triggers start.Read & write
updateAgentRepoChange the branch that sessions on this repository start from.Read & write
removeAgentRepoTake a repository off a coding agent. Sessions already on it keep their checkout.Read, write & delete

Last updated on

Latest product updates?See Changelog
Stay in the loop? Follow us onLinkedInLinkedInYouTubeYouTubeXX