Azure Cosmos DB

Use the Azure Cosmos DB node to automate work in Azure Cosmos DB and integrate Azure Cosmos DB with other applications. n8n has built-in support for a wide range of Azure Cosmos DB features, which includes creating, getting, updating, and deleting containers and items.

On this page, you'll find a list of operations the Azure Cosmos DB node supports, and links to more resources.

Credentials

You can find authentication information for this node here.

Operations

• Container:

  • Create

  • Delete

  • Get

  • Get Many

• Item:

  • Create

  • Delete

  • Get

  • Get Many

  • Execute Query

  • Update

Item: Execute Query

Execute a NoSQL SQL query against a container and return matching items.

Parameters

Parameter	Required	Description
Container	Yes	The container to run the query against. Select from a list or enter the container ID directly.
Query	Yes	The SQL query to execute. Use $1, $2, $3, etc. as positional placeholders for query parameters. n8n automatically converts these to @Param1, @Param2, @Param3 before sending the request to Azure Cosmos DB. For example: SELECT * FROM c WHERE c.status = $1 AND c.startDate = $2.
Simplify	No	When enabled (default), strips internal Cosmos DB metadata fields (those starting with _) from the returned items. Disable to receive the full raw API response.

Options

Expand Options to configure query parameters.

Option	Description
Query Parameters	A comma-separated list of string values mapped positionally to $1, $2, etc. in the query. All values are always sent as strings. Use this for simple text filters such as names or status values. Example: active,2024.
Query Parameters (JSON)	A JSON array of values mapped positionally to $1, $2, etc. in the query. Preserves native types: numbers, booleans, null, and strings with leading zeros. Use this instead of Query Parameters when type precision matters. Example: [1737062400000, "01234", true, null].

Choosing between Query Parameters and Query Parameters (JSON)

Azure Cosmos DB performs type-sensitive comparisons. A filter like WHERE c.startDate = $1 returns no results if startDate is stored as a number in the database but the parameter arrives as a string.

• Use Query Parameters when all your filter values are text (names, statuses, identifiers).

• Use Query Parameters (JSON) when you need to filter on numbers, booleans, null, or strings that start with digits and must stay as strings (for example, zip codes such as "01234").

Limitation: JavaScript's JSON parser can't represent integers larger than Number.MAX_SAFE_INTEGER (9007199254740991) with full precision. Values beyond this limit may lose precision when using Query Parameters (JSON).

Templates and examples

Browse Azure Cosmos DB node documentation integration templates or search all templates

Related resources

Refer to Azure Cosmos DB's documentation for more information about the service.

If this node doesn't support the operation you want to do, you can use the HTTP Request node to call the service's API.

You can use the credential you created for this service in the HTTP Request node:

1. In the HTTP Request node, select Authentication > Predefined Credential Type.

2. Select the service you want to connect to.

3. Select your credential.

Refer to Custom API operations for more information.