CC Settings Nodes

Introduced in DC2025.02a - Arnhem (Dialogue Cloud Neo)

CC Settings nodes let you use cache information directly in Dialogue Studio, without retrieving it through SharePoint.

Action nodes

Icon Node and description

Icon	Node and description
	CC Settings Ingest Important Before you drag this node onto the canvas, Configure CC Settings nodes. Self-hosted HTTP endpoint that ingests Contact Center settings updates and maintains an in-memory LRU cache. Method: POST Default path: `/api/v1/settings` (configurable) Body: `JSON with fields Version, UccName, UccVersion, UpdateType, UpdateId, Update` Response: `{ Version, UccName, UpdateId }` Output 1: status payload with fields `Status, UccName, UpdateType, UpdateIdApplied, CollectionsTouched, Added, Changed, Removed, Persisted, CacheSize, CacheCap` LRU cache: The node tracks recently accessed UCC entries. When the number of cached UCCs exceeds Max cache size, the least recently used entries are evicted automatically to free space. This keeps memory bounded while retaining most actively accessed settings. Only the maximum cache size is configurable. All other pruning and skip rules follow the built-in logic.
	CC Settings Reader Important Before you drag this node onto the canvas, Configure CC Settings nodes. Reads a single cached Contact Center settings collection (or one item within it) previously ingested by cc-settings-ingest. Operation Resolves UccName via typed input (default `msg.name`), and chooses a collection either from the dropdown (fixed) or dynamically from `msg.collectionName` when the dropdown is set to “Set by msg.collectionName”. Fetches the raw stored object from the global context key `cc-settings:<UccName>`. If Item Id is provided, returns the single item that matches that Id; otherwise returns the entire collection. About Item Id (SharePoint Id) Item Id is the same as the SharePoint list item `Id`. During ingest, each collection is keyed by that SharePoint `Id` (the node uses `row.Id` as the key), so supplying this Id lets the reader return exactly one item. How to retrieve the SharePoint Item Id From an earlier message in your flow: If you already have an item object (e.g. from a custom call, webhook, or previous node), its SharePoint Id is usually at `msg.payload.Id`. Configure Item Id as a typed input set to `msg` and value `payload.Id`. From the ingested collection: When you read the whole collection, its keys are the SharePoint Ids. For example, send the collection to a function node and inspect `Object.keys(msg.payload)` to see available Ids. (The collection is stored as an object keyed by row Id.) Direct from SharePoint/Graph: Any REST/Graph call that returns list items includes an integer `Id` field—use that value here. Typed input examples String: Set type to string and value to the Id, e.g. 42. From `msg`: Set type to msg, value `payload.Id` (or wherever your Id is). The reader resolves typed inputs for UccName and Item Id in the same way. From `flow/global`: Store the Id in context (e.g. `global.itemId`) and choose the matching type and key. Outputs `msg.payload`: The entire collection (object keyed by SharePoint `Id`) or a single item when Item `Id` is set. `msg.ccSettings`: Metadata `{ UccName, Collection, ItemId, UpdateIdApplied }`. Errors Missing UccName, collection, item, or an uninitialized cache will raise a node error (no output). Use a Catch node to handle errors. Notes Does not mutate LRU or timestamps. Returns the entire collection when no Item Id is specified; no paging/filtering is applied.

CC Settings Ingest

Important

Before you drag this node onto the canvas, Configure CC Settings nodes.

Self-hosted HTTP endpoint that ingests Contact Center settings updates and maintains an in-memory LRU cache.

Method: POST
Default path: /api/v1/settings (configurable)
Body: JSON with fields Version, UccName, UccVersion, UpdateType, UpdateId, Update
Response: { Version, UccName, UpdateId }
Output 1: status payload with fields Status, UccName, UpdateType, UpdateIdApplied, CollectionsTouched, Added, Changed, Removed, Persisted, CacheSize, CacheCap

LRU cache: The node tracks recently accessed UCC entries. When the number of cached UCCs exceeds Max cache size, the least recently used entries are evicted automatically to free space. This keeps memory bounded while retaining most actively accessed settings.

Only the maximum cache size is configurable. All other pruning and skip rules follow the built-in logic.

CC Settings Reader

Important

Before you drag this node onto the canvas, Configure CC Settings nodes.

Reads a single cached Contact Center settings collection (or one item within it) previously ingested by cc-settings-ingest.

Operation

Resolves UccName via typed input (default msg.name), and chooses a collection either from the dropdown (fixed) or dynamically from msg.collectionName when the dropdown is set to “Set by msg.collectionName”.
Fetches the raw stored object from the global context key cc-settings:<UccName>.
If Item Id is provided, returns the single item that matches that Id; otherwise returns the entire collection.

About Item Id (SharePoint Id)

Item Id is the same as the SharePoint list item Id. During ingest, each collection is keyed by that SharePoint Id (the node uses row.Id as the key), so supplying this Id lets the reader return exactly one item.

How to retrieve the SharePoint Item Id

From an earlier message in your flow: If you already have an item object (e.g. from a custom call, webhook, or previous node), its SharePoint Id is usually at msg.payload.Id. Configure Item Id as a typed input set to msg and value payload.Id.
From the ingested collection: When you read the whole collection, its keys are the SharePoint Ids. For example, send the collection to a function node and inspect Object.keys(msg.payload) to see available Ids. (The collection is stored as an object keyed by row Id.)
Direct from SharePoint/Graph: Any REST/Graph call that returns list items includes an integer Id field—use that value here.

Typed input examples

String: Set type to string and value to the Id, e.g. 42.
From msg: Set type to msg, value payload.Id (or wherever your Id is). The reader resolves typed inputs for UccName and Item Id in the same way.
From flow/global: Store the Id in context (e.g. global.itemId) and choose the matching type and key.

Outputs

msg.payload: The entire collection (object keyed by SharePoint Id) or a single item when Item Id is set.
msg.ccSettings: Metadata { UccName, Collection, ItemId, UpdateIdApplied }.

Errors

Missing UccName, collection, item, or an uninitialized cache will raise a node error (no output). Use a Catch node to handle errors.

Notes

Does not mutate LRU or timestamps.
Returns the entire collection when no Item Id is specified; no paging/filtering is applied.