# MariaDB - Workflow node | Docs - nodulz

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

Language: en

Run SQL and select, insert, update or delete 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`. Runtime : `nodulz`.

## Credentials and prerequisites

- [MariaDB](/docs/credentials) (`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](/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` | `""` | - |
| `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

| Setting | Purpose and guidance |
| --- | --- |
| `credentialId`<br>Credential | Choose a credential matching the node engine. The SQL account controls read and write permissions. |
| `operation`<br>Operation | Run SQL or act on rows. Updates and deletes require a non-empty filter. |
| `query`<br>SQL query | Use ? for values, in parameter order. Expressions are sent as parameters: do not wrap them in quotes. |
| `parameters`<br>JSON parameters | JSON array, for example [42, "Alice"]. Workflow expressions are supported. Values bind to ? placeholders. |
| `rawExpressions`<br>Insert expressions as-is (unsafe) | Only for dynamic table or column names, with trusted values. |
| `table`<br>Table | Exact name in the credential database. Triggers use a fixed name without expressions. |
| `data`<br>JSON data | Non-empty JSON object of column names and values. Expressions supported; values are parameterized. |
| `match`<br>JSON conditions | JSON object of equality conditions combined with AND. null matches SQL NULL. An empty object is allowed only for reads. |
| `limit`<br>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.

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)