---
title: "CC"
description: "Explains recipient configuration and notification usage for the CC (Carbon Copy) node."
---

# CC

## Node Type

`cc`
Use the above `type` value when creating the node; do not use the documentation filename as the type.

## Node Description
Sends a CC task/notification to specified users, used for viewing or informing only.

## Business Scenario Examples
Sending a CC to relevant stakeholders for information after an approval is completed.

## Configuration Items
| Field | Type | Default | Required | Description |
| --- | --- | --- | --- | --- |
| users | array | [] | Yes | List of recipients. Specified as an array of user IDs or user queries. User IDs could be found by query `users:list` API, or use variables of user IDs form upstream. The query object will contains a `filter` object to describe the query condition of users collection.  See [Common Conventions - filter](../conventions/index.md#the-filter-field-in-trigger-and-node-configuration). |
| ccDetail | string | None | Yes | UID for the CC detail interface configuration (generated by UI). |
| title | string | Node Title | No | Task title, supports variable templates. |
| notifications | array | [] | No | Notification configurations (generated by UI). |

## Branch Description
Does not support branching.

## Test Support
Not supported. This node cannot use CLI `workflow flow-nodes test` or HTTP `flow_nodes:test`, because the server-side instruction does not implement `test()`.

## Example Configuration
```json
{
  "users": ["{{ $context.data.ownerId }}", { "filter": { "id": "{{ $context.data.managerId }}" } }, 123],
  "ccDetail": "cc-ui-uid",
  "title": "{{ $context.data.title }} - CC"
}
```

## Output Variables
This node does not output variables.
