Run SQL, a stored procedure or row operations on 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.
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
""
-
operation
enum
"query"
query, select, insert, update, delete, procedure
query
string
"SELECT 1 AS ok"
-
parameters
string
"{}"
-
procedure
string
""
-
table
string
""
-
data
string
"{}"
-
match
string
"{}"
-
orderBy
string
""
-
limit
number
100
-; ≥ 1, ≤ 10000
returnRows
boolean
true
-
timeout
number
30
-; ≥ 1, ≤ 600
Configuration help
credentialId Connection credential
SQL Server credential. Enable SSL for Azure SQL.
operation Operation
Update and delete require at least one condition.
query SQL query
Use @name with the parameters. An expression in the query is sent as a parameter: do not wrap it in quotes.
procedure Stored procedure
Procedure name, with its schema if needed.
parameters JSON parameters
Object {"name": value} for @name, or an array for @p1, @p2…
table Table
Table name, for example dbo.users.
match JSON conditions
Equalities combined with AND. null matches IS NULL.
orderBy Sort
Comma-separated columns, with ASC or DESC.
limit Maximum rows
From 1 to 10,000.
returnRows Return changed rows
Turn off if the table has SQL triggers.
timeout Timeout (seconds)
The query is cancelled after this delay.
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
json
{"credentialId":"","operation":"query","query":"SELECT 1 AS ok","parameters":"{}","procedure":"","table":"","data":"{}","match":"{}","orderBy":"","limit":100,"returnRows":true,"timeout":30}
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.
Run SQL, a stored procedure or row operations on 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. Runtime :nodulz.Credentials and prerequisites
database/mssql). SQL Server or Azure SQL databaseCreate 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.
credentialIdstring""operationenum"query"query,select,insert,update,delete,procedurequerystring"SELECT 1 AS ok"parametersstring"{}"procedurestring""tablestring""datastring"{}"matchstring"{}"orderBystring""limitnumber100returnRowsbooleantruetimeoutnumber30Configuration help
credentialIdConnection credential
operationOperation
querySQL query
procedureStored procedure
parametersJSON parameters
tableTable
matchJSON conditions
orderBySort
limitMaximum rows
returnRowsReturn changed rows
timeoutTimeout (seconds)
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
{ "credentialId": "", "operation": "query", "query": "SELECT 1 AS ok", "parameters": "{}", "procedure": "", "table": "", "data": "{}", "match": "{}", "orderBy": "", "limit": 100, "returnRows": true, "timeout": 30 }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, Executions, Node catalog.