DuckDB

Node catalog Actions

On this page

Run analytical SQL against a local DuckDB file.

Usage and specifics

Select a connection and a database-compatible operation. SQLite and DuckDB use an existing file under HOST_FILES_ROOT and default to read-only. Firestore and BigQuery use Google Cloud; DynamoDB and Redshift use AWS. Account permissions restrict operations.

Technical type : duckdb. Runtime : nodulz.

Credentials and prerequisites

DuckDB (integration / duckdb). Run analytical SQL against a local DuckDB file.

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`	`""`	-
`timeout`	`number`	`30`	-; ≥ 1, ≤ 600
`maxRows`	`number`	`100`	-; ≥ 1, ≤ 10000
`operation`	`enum`	`"query"`	`query`
`query`	`string`	`"SELECT 1 AS ok"`	-
`parameters`	`string`	`"[]"`	-

Configuration help

credentialId Credential: Credentials are encrypted. Firestore and BigQuery reuse a GCP credential; DynamoDB and Redshift reuse an AWS credential.
operation Operation: Choose an action. Results are never paginated automatically; use the returned token to continue.

Initial configuration

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

json

{
  "credentialId": "",
  "timeout": 30,
  "maxRows": 100,
  "operation": "query",
  "query": "SELECT 1 AS ok",
  "parameters": "[]"
}

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.