Cosmos DBInstall

Summary

Updates selected fields on an existing Azure Cosmos DB item by sending JSON Patch set operations. Choose the authentication method and database and container, identify the item and its exact partition key, then add one or more field paths and values to set.

Inputs

• Authentication Type — Choose Master Key (default) or Microsoft Entra ID (Azure AD); provide the corresponding Cosmos DB credentials.
• Database Name or ID (required) — Select or specify the target database.
• Container Name or ID (required) — Select or specify the target container.
• Item (required) — Select the item from the list or enter its ID.
• Partition Key (required) — Supply the exact partition key value for the item, by selecting a value or entering it.
• Fields to Set (required) — Add one or more field paths and values. Paths are normalized to start with /; values that parse as JSON become their JSON types, while other values are sent as strings. At least one nonempty path is required.
• Use Dev Override (Custom Endpoint + Token) — Optionally bypass the selected credential flow with a custom Cosmos DB endpoint and bearer access token.
• Custom Endpoint — Cosmos DB account endpoint, shown when Dev Override is enabled.
• Custom Access Token — Bearer token scoped to Cosmos DB, shown when Dev Override is enabled. The node also accepts a token value prefixed with Bearer.

Output shape

One n8n output item for each processed input item, containing the updated Cosmos DB document when returned by the patch request.

If Cosmos DB returns no resource, the node outputs an object with the item ID, partition key, response status code, and an updated boolean. With Continue On Fail enabled, errors are emitted as { "error": "..." } for the corresponding input item.

Links

• n8n community nodes installation guide