# Job As JSON Action

With the help of the Job As JSON action, it is possible to write all information that belongs to the job object in a JSON file and to define the location where it should be stored. This can be necessary for various workflows in which the payload of the stream should be externally accessible.

{% hint style="info" %}
**Update:**

The Job From JSON node will no longer import the job id of the job that has previously been extracted with the Job As JSON node. This change avoids having a wrong job ID reference after Job From JSON trigger that kept pushing all updates to the "old" exported job. Additionally, stream variables will now also be read in and be available after Job From JSON node execution.
{% endhint %}


---

# 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.6.2/helmut4-components/streamdesigner/nodes/actions/job-action/job-as-json-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.