SQL Server trigger

Node catalog Triggers

On this page

React to rows added, changed or deleted in SQL Server

Usage and specifics

Select a SQL Server credential and target resource. Account permissions apply to queries and monitoring. Trigger settings determine which changes are detected after publishing.

Technical type : mssql_trigger. Runtime : nodulz.

Credentials and prerequisites

Microsoft SQL Server (database / mssql). SQL Server or Azure 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"`	-
`mode`	`enum`	`"snapshot"`	`snapshot`, `change_tracking`
`events`	`array`	`["insert"]`	-; min 1
`pollInterval`	`number`	`60`	-; ≥ 10, ≤ 86400
`testPayload`	`string`	`""`	-

Configuration help

credentialId Connection credential: SQL Server credential. Enable SSL for Azure SQL.
table Table: Table name, for example dbo.users.
keyColumn Unique key column: Unique, non-null column, for example id.
mode Change detection: Change Tracking is more reliable and faster, but must be enabled on the database and table.
events Events: At least one event.
pollInterval Polling interval (seconds): The first pass sets the baseline and triggers nothing.
testPayload JSON test data: Event used for a manual test. Empty: generated example.

Initial configuration

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

json

{
  "credentialId": "",
  "table": "",
  "keyColumn": "id",
  "mode": "snapshot",
  "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.