> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/helmut4-components/streamdesigner/nodes/actions/cosmo-16/cosmo-asset-report-action.md).

# Cosmo Asset Report Action

The **Cosmo Asset Report Action** node generates a JSON report describing how often and in which projects a specific asset is used.

By providing an **Asset ID** and a destination file, the node exports a report containing project usage information for that asset. The behavior when the destination file already exists can also be configured.

This node is typically used together with the **Cosmo Get Project Assets Action** to create reports for iterated assets.

#### Input Parameters

**Asset ID**\
ID of the asset for which the report should be generated.\
Commonly retrieved from [{job.assetId}](/helmut4-releases/helmut4-components/streamdesigner/wildcards/job-related-wildcards-32/job-assetid.md) or from the result of a previous node.

**Destination File**\
Full file path and filename of the JSON report.

**If New File Exists**\
Defines how the node handles an already existing file:

* **APPEND** — adds the new report data to the existing file
* **INCREMENT\_NAME** — creates a new file with an incremented filename
* **DELETE\_EXISTING** — overwrites the existing file

<figure><img src="/files/0R7K9mHClkRCfQDnqwIV" alt="" width="349"><figcaption><p>Cosmo Asset Report Action</p></figcaption></figure>

#### Output

The node exports a JSON file containing information about:

* how many projects reference the asset
* which projects currently use the asset

#### Behavior

* Reads asset usage information from the Cosmo database
* Does not require the media file to be online
* Can be executed for single assets or as part of an iteration workflow
* Supports asynchronous execution

If the provided Asset ID is invalid or the asset does not exist, the node fails.

#### Typical Workflow

1. Iterate through project assets using [Cosmo Get Project Assets Action](/helmut4-releases/helmut4-components/streamdesigner/nodes/actions/cosmo-16/cosmo-get-project-assets-action.md)
2. For each asset, execute this node
3. Generate a usage report per asset

This allows automated reporting such as dependency tracking or archive validation.

#### Practical Use Cases

* identifying frequently used media
* verifying whether media can be archived
* detecting shared assets across productions
* compliance or documentation workflows

In simple terms:\
This node answers a very practical question — **“If I delete or archive this file, what projects will I break?”**