Run SQL and select, insert, update or delete 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. Runtime : nodulz.
Credentials and prerequisites
MySQL (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 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
query
string
"SELECT 1 AS ok"
-
parameters
string
"[]"
-
table
string
""
-
data
string
"{}"
-
match
string
"{}"
-
limit
number
100
-; ≥ 1, ≤ 10000
rawExpressions
boolean
false
-
Configuration help
credentialId Credential
Choose a credential matching the node engine. The SQL account controls read and write permissions.
operation Operation
Run SQL or act on rows. Updates and deletes require a non-empty filter.
query SQL query
Use ? for values, in parameter order. Expressions are sent as parameters: do not wrap them in quotes.
parameters JSON parameters
JSON array, for example [42, "Alice"]. Workflow expressions are supported. Values bind to ? placeholders.
rawExpressions Insert expressions as-is (unsafe)
Only for dynamic table or column names, with trusted values.
table Table
Exact name in the credential database. Triggers use a fixed name without expressions.
data JSON data
Non-empty JSON object of column names and values. Expressions supported; values are parameterized.
match JSON conditions
JSON object of equality conditions combined with AND. null matches SQL NULL. An empty object is allowed only for reads.
limit Maximum rows
Between 1 and 10,000 rows for a select.
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
json
{"credentialId":"","operation":"query","query":"SELECT 1 AS ok","parameters":"[]","table":"","data":"{}","match":"{}","limit":100,"rawExpressions":false}
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 and select, insert, update or delete 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. Runtime :nodulz.Credentials and prerequisites
database/mysql). MySQL relational 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,deletequerystring"SELECT 1 AS ok"parametersstring"[]"tablestring""datastring"{}"matchstring"{}"limitnumber100rawExpressionsbooleanfalseConfiguration help
credentialIdCredential
operationOperation
querySQL query
parametersJSON parameters
rawExpressionsInsert expressions as-is (unsafe)
tableTable
dataJSON data
matchJSON conditions
limitMaximum rows
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
{ "credentialId": "", "operation": "query", "query": "SELECT 1 AS ok", "parameters": "[]", "table": "", "data": "{}", "match": "{}", "limit": 100, "rawExpressions": false }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.