> 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-in-ame-action.md).

# Job Render in AME Action

With the help of the Job Render in AME Action it is possible to transfer a file to AME and process it with a defined encoding profile. This is equally possible for imports and exports and can be executed on a MAC or Windows client (both support AME).

AME returns the progress of the encoding process to Helmut and this is displayed on the dashboard if the node is used as part of a workflow that creates a job object. This is always the case when the Helmut4 panel (auto import, export) is involved, or a watch folder that is monitored by the server.

The node does not need any information about the file extension in the source path, as this is set by AME itself (is defined in the .epr file). If desired, AME will also count up if the file is already available on the target path. (Setting in AME). The node sets the wildcard {job.destination} in the paypload job, which in the further course of the stream contains the target path of the file defined in the node including the file extension.


---

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