> 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/v4.6.0/helmut4-components/streamdesigner/nodes/actions/job-action/job-render-proxy-in-ame-action.md).

# Job Render Proxy in AME Action

The Job Render Proxy in AME Action works exactly like the Job render in AME Action, with the only difference that it defines the target path defined in the node as wildcard {job.proxy} in the job payload. This is now available in the further course of the stream.

#### Example:

This node can be used, for example, to generate a suitable proxy file for the Premiere proxy workflow. This can be transferred to Cosmo and linked to a high res file.


---

# 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:

```
GET https://docs.helmut.de/helmut4-releases/v4.6.0/helmut4-components/streamdesigner/nodes/actions/job-action/job-render-proxy-in-ame-action.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.