# MySQL trigger - Workflow trigger | Docs - nodulz

Source: https://nodulz.com/docs/nodes/mysql_trigger

Language: en

Poll for inserted, updated or deleted MySQL rows

## Usage and specifics

Select the database connection and table or query. Write and delete operations change remote data. For a trigger, configure tracking fields and interval, then publish.

Technical type : `mysql_trigger`. Runtime : `nodulz`.

## Credentials and prerequisites

- [MySQL](/docs/credentials) (`database` / `mysql`). MySQL relational database

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the [credentials guide](/docs/credentials) for access and rotation.

## Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

| Parameter | Type | Default | Values / limits |
| --- | --- | --- | --- |
| `credentialId` | `string` | `""` | - |
| `table` | `string` | `""` | - |
| `keyColumn` | `string` | `"id"` | - |
| `events` | `array` | `["insert"]` | -; min 1 |
| `pollInterval` | `number` | `60` | -; ≥ 10, ≤ 86400 |
| `testPayload` | `string` | `""` | - |

## Configuration help

| Setting | Purpose and guidance |
| --- | --- |
| `credentialId`<br>Credential | Choose a credential matching the node engine. The SQL account controls read and write permissions. |
| `table`<br>Table | Exact name in the credential database. Triggers use a fixed name without expressions. |
| `keyColumn`<br>Unique key column | Unique, non-null, stable column, for example id. Composite keys are not supported. |
| `events`<br>Events | Select at least one event. Output: operation, table, row, oldRow and triggeredAt. |
| `pollInterval`<br>Polling interval (seconds) | First poll establishes a baseline. Compares up to 10,000 rows and 5 MiB per table. Transient changes between polls may be missed. A delivery may repeat after an interruption. |
| `testPayload`<br>JSON test payload | JSON object for a manual run. Empty: sample event using the selected key column. |

## Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

```json
{
  "credentialId": "",
  "table": "",
  "keyColumn": "id",
  "events": [
    "insert"
  ],
  "pollInterval": 60,
  "testPayload": ""
}
```

## Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.

See also : [Expressions and data](/docs/expressions), [Executions](/docs/executions), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)