> 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/third-party/telestream/diva/diva-delete-content-action.md).

# Diva Delete Content Action

By using the Diva Delete Content Action node within a stream it is possible to trigger a delete object job in Diva.

For proceeding the job an "Object name", the name that got defined during archive, must be  provided. The "Object category" (a.k.a collection) must be an existing one in the system and must also be the same as during archive process. The combination of these both values are unique in DIVA and stands for exact identification of the objects. The "Priority level" of the job may be configured as well and can be any number between -1 and 100 where -1 stands for unset and is the lowest and default value.

<figure><img src="/files/xBvQBtzCkydwv6uNrvgD" alt=""><figcaption><p>Diva Delete Content Action V1 node</p></figcaption></figure>

Following the example values from [Diva](/helmut4-releases/helmut4-components/streamdesigner/nodes/actions/third-party/telestream/diva.md)\
\- Object category: PROJ PARK HELMUT


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.helmut.de/helmut4-releases/helmut4-components/streamdesigner/nodes/actions/third-party/telestream/diva/diva-delete-content-action.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.