# Azure Cosmos DB - Workflow node | Docs - nodulz

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

Language: en

Query and modify Azure Cosmos DB for NoSQL documents.

## 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 : `cosmosdb`. Runtime : `nodulz`.

## Credentials and prerequisites

- [Azure Cosmos DB](/docs/credentials) (`integration` / `cosmosdb`). Query and modify Azure Cosmos DB for NoSQL documents.

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` | `""` | - |
| `timeout` | `number` | `30` | -; ≥ 1, ≤ 600 |
| `maxRows` | `number` | `100` | -; ≥ 1, ≤ 10000 |
| `operation` | `enum` | `"query"` | `query`, `get`, `create`, `upsert`, `delete` |
| `collection` | `string` | `""` | - |
| `documentId` | `string` | `""` | - |
| `partitionKey` | `string` | `"[]"` | - |
| `query` | `string` | `"SELECT * FROM c"` | - |
| `parameters` | `string` | `"[]"` | - |
| `data` | `string` | `"{}"` | - |
| `pageToken` | `string` | `""` | - |

## Configuration help

| Setting | Purpose and guidance |
| --- | --- |
| `credentialId`<br>Credential | Credentials are encrypted. Firestore and BigQuery reuse a GCP credential; DynamoDB and Redshift reuse an AWS credential. |
| `operation`<br>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",
  "collection": "",
  "documentId": "",
  "partitionKey": "[]",
  "query": "SELECT * FROM c",
  "parameters": "[]",
  "data": "{}",
  "pageToken": ""
}
```

## 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)