NocoDB Webhooks
A webhook makes NocoDB call another system when something happens to a table: a record is added, changed or deleted, or someone presses a button. This skill is the receiving-side and UI view — events, payload, conditions, testing. Creating, replacing and deleting hooks as code (the Meta API v3 / MCP hooks category, notification types such as Email, Slack, Script) is covered by nocodb-dev:webhooks.
Checked against the NocoDB docs ("Create Webhook") and a live MCP server in October 2026.
Events
| Source |
Events |
Edition |
| Record |
Send Me Everything, After Insert, After Update, After Delete |
all |
| Button |
fires when a Button field is clicked |
all |
| View |
Send Me Everything, After Create, After Update, After Delete |
paid plans (cloud and self-hosted) |
| Field |
Send Me Everything, After Create, After Update, After Delete |
paid plans |
| Comment |
Comment Added, Edited, Deleted, Resolved, Reopened |
paid plans |
- There are no separate bulk events: After Insert, After Update and After Delete cover "one or more records" — a bulk import or a change applied to every record in a view still arrives as these events, with several rows in one payload
- Paid plans also unlock: watching specific fields on After Update, firing on one form's submissions only (After Insert), and the Run Script action
Set One Up in the UI
- Open the table → Tools (toolbar) → Webhooks → Add New Webhook
- Give it a descriptive title (
Orders - New Order Created)
- Choose the source (Record, View, Field, Comment or Button) and the event
- Optional: add conditions (Record events only) and, on After Update, the fields to watch
- Choose the action — HTTP Request (method GET, POST, PUT, DELETE, PATCH or HEAD, URL, headers, body) or Run Script (paid)
- Press Test webhook — it sends a sample payload so you can see the receiver react
- Create Webhook
The default body is {{ json event }}, the complete event as JSON. A custom body can be a Handlebars template that sends only some fields. If the receiver needs Content-Type: application/json, add the header yourself.
Webhook URLs and tokens sit in the NocoDB webhook configuration, so use the production URL of the receiver (for n8n, the Webhook node's production URL, which works once the workflow is published) and prefer an Authorization header over a secret inside the URL.
What the Receiver Gets
Default body, record event (version v3):
{
"type": "records.after.insert",
"id": "<event id>",
"version": "v3",
"data": {
"table_id": "<tableId>",
"table_name": "Orders",
"view_id": "<viewId>",
"view_name": "Orders",
"rows": [
{ "Id": 1, "Title": "New Order", "Status": "pending", "CreatedAt": "2026-10-03T10:40:20.998Z", "UpdatedAt": "2026-10-03T10:40:20.998Z" }
]
}
}
| Key |
Meaning |
type |
records.after.insert, records.after.update, records.after.delete |
id, version |
the event id and the payload version ("v3") |
data.table_id, data.table_name |
which table — use the id, not the name, in follow-up calls |
data.view_id, data.view_name |
the view the change came through |
data.rows |
an array — one entry per affected record, field title → value |
data.previous_rows |
After Update only: the same records before the change (rows holds the new state) |
Receiver rules:
- Loop over
data.rows; never read only rows[0]
- Look the record up by its
Id and skip what is already done — treat the receiver as one that may see the same change twice
- Answer with a quick
2xx and do slow work afterwards (hand long jobs to a background task runner)
- Log
type and id while debugging
Conditions
Record events can carry conditions (AND/OR groups of field comparisons, for example Status = Complete AND Priority = High). A condition fires on the transition: the webhook runs only when the record goes from "condition not met" to "condition met" during the event, not on every later edit of a record that already matches. Conditions do not apply to Button webhooks.
Mind the loop. An automation that writes its status or result back to the same table fires After Update again. Gate the webhook with a condition on the status transition (for example status = pending, set by whoever requests a run, while the automation only writes processing, completed, failed), watch only the business fields on paid plans, or keep job state in a separate table.
Button Trigger
A Button field can start a webhook, which makes a record a remote control for an automation: the user presses the button on the row, NocoDB calls the receiver with that record. Use it for "approve", "send invoice", "start the import" — actions that should happen on purpose, not on every edit.
Webhooks Through MCP
| Edition |
What works |
| Community |
No hook tools — use the UI (or the REST API, see nocodb-dev:webhooks) |
| Cloud / licensed |
listHooks (tableId) and getHook (hookId) are listed directly; createHook, updateHook and deleteHook sit behind listTools with category: "hooks" and run through callTool |
mcp__plugin_nocodb-ops_nocodb__listHooks { "tableId": "<tableId>" }
mcp__plugin_nocodb-ops_nocodb__getHook { "hookId": "<hookId>" }
updateHook replaces the whole webhook: read it with getHook first and send every field you want to keep, notification included. Hook creation and the notification types are in nocodb-dev:webhooks; the full tool contract is in mcp-patterns.
Checklist
- The receiver URL is live and the workflow behind it is published
- Test webhook succeeded against the production URL
- The receiver loops over
data.rows and tolerates a repeated event
- A condition is set when only one state change should fire it
- When "nothing happens", list the table's webhooks (
listHooks or the Webhooks tool) and check the event, the conditions and whether the webhook is active
1---2name: webhooks-23description: |4 Use NocoDB webhooks from the business side — which events exist, how to set one up in the UI, what the receiving system gets (payload), conditions, the Button trigger, and testing. Use when:5 - "trigger something when a record changes"6 - "send NocoDB data to n8n / another system"7 - "set up a webhook in NocoDB"8 - "what does the NocoDB webhook payload look like"9 - "fire a webhook from a button"10 - "webhook only when status becomes ..."11 - "list the webhooks on a table"12metadata:13 source: https://skillmd.com/skills/agents-store/webhooks-214---1516# NocoDB Webhooks1718A webhook makes NocoDB call another system when something happens to a table: a record is added, changed or deleted, or someone presses a button. This skill is the **receiving-side and UI view** — events, payload, conditions, testing. Creating, replacing and deleting hooks as code (the Meta API v3 / MCP `hooks` category, notification types such as Email, Slack, Script) is covered by `nocodb-dev:webhooks`.1920Checked against the NocoDB docs ("Create Webhook") and a live MCP server in October 2026.2122## Events2324| Source | Events | Edition |25|--------|--------|---------|26| **Record** | *Send Me Everything*, *After Insert*, *After Update*, *After Delete* | all |27| **Button** | fires when a Button field is clicked | all |28| **View** | *Send Me Everything*, *After Create*, *After Update*, *After Delete* | paid plans (cloud and self-hosted) |29| **Field** | *Send Me Everything*, *After Create*, *After Update*, *After Delete* | paid plans |30| **Comment** | *Comment Added*, *Edited*, *Deleted*, *Resolved*, *Reopened* | paid plans |3132- There are **no separate bulk events**: *After Insert*, *After Update* and *After Delete* cover "one or more records" — a bulk import or a change applied to every record in a view still arrives as these events, with several rows in one payload33- Paid plans also unlock: watching specific fields on *After Update*, firing on one form's submissions only (*After Insert*), and the *Run Script* action3435## Set One Up in the UI36371. Open the table → **Tools** (toolbar) → **Webhooks** → **Add New Webhook**382. Give it a descriptive title (`Orders - New Order Created`)393. Choose the source (Record, View, Field, Comment or Button) and the event404. Optional: add **conditions** (Record events only) and, on *After Update*, the fields to watch415. Choose the action — **HTTP Request** (method GET, POST, PUT, DELETE, PATCH or HEAD, URL, headers, body) or **Run Script** (paid)426. Press **Test webhook** — it sends a sample payload so you can see the receiver react437. **Create Webhook**4445The default body is `{{ json event }}`, the complete event as JSON. A custom body can be a Handlebars template that sends only some fields. If the receiver needs `Content-Type: application/json`, add the header yourself.4647Webhook URLs and tokens sit in the NocoDB webhook configuration, so use the **production** URL of the receiver (for n8n, the Webhook node's production URL, which works once the workflow is published) and prefer an `Authorization` header over a secret inside the URL.4849## What the Receiver Gets5051Default body, record event (version `v3`):5253```json54{55 "type": "records.after.insert",56 "id": "<event id>",57 "version": "v3",58 "data": {59 "table_id": "<tableId>",60 "table_name": "Orders",61 "view_id": "<viewId>",62 "view_name": "Orders",63 "rows": [64 { "Id": 1, "Title": "New Order", "Status": "pending", "CreatedAt": "2026-10-03T10:40:20.998Z", "UpdatedAt": "2026-10-03T10:40:20.998Z" }65 ]66 }67}68```6970| Key | Meaning |71|-----|---------|72| `type` | `records.after.insert`, `records.after.update`, `records.after.delete` |73| `id`, `version` | the event id and the payload version (`"v3"`) |74| `data.table_id`, `data.table_name` | which table — use the id, not the name, in follow-up calls |75| `data.view_id`, `data.view_name` | the view the change came through |76| `data.rows` | **an array** — one entry per affected record, field title → value |77| `data.previous_rows` | *After Update* only: the same records before the change (`rows` holds the new state) |7879Receiver rules:8081- Loop over `data.rows`; never read only `rows[0]`82- Look the record up by its `Id` and skip what is already done — treat the receiver as one that may see the same change twice83- Answer with a quick `2xx` and do slow work afterwards (hand long jobs to a background task runner)84- Log `type` and `id` while debugging8586## Conditions8788Record events can carry conditions (AND/OR groups of field comparisons, for example *Status = Complete* AND *Priority = High*). A condition fires **on the transition**: the webhook runs only when the record goes from "condition not met" to "condition met" during the event, not on every later edit of a record that already matches. Conditions do not apply to Button webhooks.8990**Mind the loop.** An automation that writes its status or result back to the same table fires *After Update* again. Gate the webhook with a condition on the status transition (for example `status` = `pending`, set by whoever requests a run, while the automation only writes `processing`, `completed`, `failed`), watch only the business fields on paid plans, or keep job state in a separate table.9192## Button Trigger9394A Button field can start a webhook, which makes a record a remote control for an automation: the user presses the button on the row, NocoDB calls the receiver with that record. Use it for "approve", "send invoice", "start the import" — actions that should happen on purpose, not on every edit.9596## Webhooks Through MCP9798| Edition | What works |99|---------|------------|100| **Community** | No hook tools — use the UI (or the REST API, see `nocodb-dev:webhooks`) |101| **Cloud / licensed** | `listHooks` (`tableId`) and `getHook` (`hookId`) are listed directly; `createHook`, `updateHook` and `deleteHook` sit behind `listTools` with `category: "hooks"` and run through `callTool` |102103```104mcp__plugin_nocodb-ops_nocodb__listHooks { "tableId": "<tableId>" }105mcp__plugin_nocodb-ops_nocodb__getHook { "hookId": "<hookId>" }106```107108`updateHook` replaces the whole webhook: read it with `getHook` first and send every field you want to keep, `notification` included. Hook creation and the notification types are in `nocodb-dev:webhooks`; the full tool contract is in **mcp-patterns**.109110## Checklist111112- The receiver URL is live and the workflow behind it is published113- *Test webhook* succeeded against the production URL114- The receiver loops over `data.rows` and tolerates a repeated event115- A condition is set when only one state change should fire it116- When "nothing happens", list the table's webhooks (`listHooks` or the Webhooks tool) and check the event, the conditions and whether the webhook is active