# Job Destination

This wildcard is consistently substituted with the destination path of the preceding node and is consistently overwritten within the payload of the job object. For instance, when employing the Job Render In AME Action, the Destination File Path specified there is substituted in place of the {job.destination} wildcard. If a subsequent action node is employed, containing its own destination path, the {job.destination} wildcard is subsequently replaced by this new value.

An alternative method to retrieve the destination is by utilizing the [{node.result.?}](/helmut4-releases/v4.9.0/helmut4-components/streamdesigner/wildcards/result-or-return-wildcards-2/node-result.md) or [{stream.last\_result}](/helmut4-releases/v4.9.0/helmut4-components/streamdesigner/wildcards/result-or-return-wildcards-2/stream-last_result.md) wildcard as well.


---

# Agent Instructions: 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.9.0/helmut4-components/streamdesigner/wildcards/job-related-wildcards-32/job-destination.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.