MariaDB trigger

Node catalog Triggers

On this page

Poll for inserted, updated or deleted MariaDB 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 : mariadb_trigger. Runtime : nodulz.

Credentials and prerequisites

MariaDB (database / mariadb). MySQL-compatible SQL 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 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

credentialId Credential: Choose a credential matching the node engine. The SQL account controls read and write permissions.
table Table: Exact name in the credential database. Triggers use a fixed name without expressions.
keyColumn Unique key column: Unique, non-null, stable column, for example id. Composite keys are not supported.
events Events: Select at least one event. Output: operation, table, row, oldRow and triggeredAt.
pollInterval 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 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.