# When webhook received

> Part of the NocoDB documentation (Workflows > Workflows > Nodes > Trigger). 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/workflows/nodes/trigger-nodes/webhook
Last updated: 2026-10-03

The When webhook received trigger starts a NocoDB workflow from an incoming HTTP request.

<Callout type="info">
  Available on NocoDB Cloud (Plus plan and above) and licensed on-premise deployments.
</Callout>

This NocoDB trigger starts a workflow when an HTTP request arrives at a URL that belongs to the workflow. Use it to start automations from systems that can send HTTP requests but have no dedicated NocoDB integration.

The node needs no configuration. NocoDB generates its webhook URL when the node is configured. A request to the URL starts the workflow only while the workflow is published. The trigger accepts `GET`, `POST`, `PUT`, `PATCH`, and `DELETE`.

### Testing

The test step of the trigger listens for a real request. While it listens, send a request to the webhook URL. The trigger captures that request as its sample data. NocoDB only records the captured request as the sample. It does not run the rest of the workflow.

### Output

The trigger gives the request to the rest of the workflow:

| Output                                 | Content                           |
| -------------------------------------- | --------------------------------- |
| `request.body`                         | The request body, as JSON         |
| `request.headers`                      | The request headers               |
| `request.query`                        | The URL query parameters          |
| `request.method`                       | The HTTP method of the request    |
| `trigger.type` and `trigger.timestamp` | How and when the workflow started |

After NocoDB captures a test request, later nodes can select the individual fields in the body, headers, and query parameters. Without a test request, they can select only the whole object.

### Use cases

* Start a workflow from the outgoing webhook of an external service
* Let a script or a scheduled job in another system start a NocoDB automation
* Receive a payload from a form or payment provider and write it into a table

***

---

## Related pages

- [Manual](https://nocodb.com/docs/workflows/nodes/trigger-nodes/manual.md): The Manual Trigger node starts a NocoDB workflow only when a user runs it.
- [Button clicked](https://nocodb.com/docs/workflows/nodes/trigger-nodes/button-clicked.md): Start a workflow when a user clicks a Run automation button on an interface page or record.
- [Scheduled](https://nocodb.com/docs/workflows/nodes/trigger-nodes/scheduled.md): The Scheduled Trigger runs a NocoDB workflow on a fixed schedule.
- [Record Created](https://nocodb.com/docs/workflows/nodes/trigger-nodes/record-created.md): Trigger workflows when new records are created in NocoDB.
- [Record Updated](https://nocodb.com/docs/workflows/nodes/trigger-nodes/record-updated.md): Trigger workflows when records are updated in NocoDB.
- [Record Deleted](https://nocodb.com/docs/workflows/nodes/trigger-nodes/record-deleted.md): Trigger workflows when records are deleted in NocoDB.
- [Record Matches Condition](https://nocodb.com/docs/workflows/nodes/trigger-nodes/record-matches-condition.md): Trigger workflows when records meet specific conditions in NocoDB.
- [Record Created via Specific Form](https://nocodb.com/docs/workflows/nodes/trigger-nodes/record-created-form.md): Trigger workflows when new records are created via a specific form in NocoDB.