> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/skyone-studio/data-management/jsonata-jobs.md).

# JSONata Jobs

The “**JSONata Jobs**” feature allows you to process files directly within the engine, without relying on intermediate steps. When creating a new **JSONata Job**, you must provide a **JSON** file, which will serve as the basis for transformations.

This approach is ideal for handling large volumes of text files or complex JSON structures, as the processing occurs internally and efficiently—ensuring performance and stability even with extensive content.

### Add JSONata Jobs

To add a new “**JSONata Jobs**”, follow these steps:

1. In the left-hand menu, click "**JSONata Jobs**".
2. Then, click "**Add JSONata Job**".
3. The edit screen for the new **JSONata Job** will open automatically. Create and configure your Job..
4. Click “**Execute current Job**” to execute the action.. &#x20;

### JSONata Jobs Options

The top-right menu provides the following actions:

<figure><img src="/files/hIOdZ6GMmnDGRQpsSgFW" alt=""><figcaption></figcaption></figure>

* **Create new Job**: Automatically creates a new Job, which will open in a new tab.
* **Execute current File Job**: Runs the active Job in the current tab, processing the defined queries.
* **Execute current Job in new tab**: Opens a new tab to run the same Job.
* **Job Process List**: Displays all running processes.
* **Job Configuration**: Allows you to configure parameters for the current Job. Settings are organized into two tabs:
  * **General**: Define the Job name and select the JSON file, directory, or file set. You can also specify the target directory where the result of the file manipulation will be saved.
  * **Groups**: Manage access permissions by adding or removing groups as needed.

&#x20;         Finally, click "**Apply** to save the settings.

* **Save Job**: Saves the current state of the Job.

### Returned Data Panel

After selecting or running a Job in the **Data Warehouse**, the **Returned Data Panel** section displays three distinct tabs with information related to data execution and structure:

{% tabs %}
{% tab title="Files" %}
In this tab, you can view the files available in the selected directory or file filter. It's the starting point to understand which data is being used as input.
{% endtab %}

{% tab title="Output" %}
This tab shows the results of the Job after execution. Here, you can review the content generated based on the applied SQL transformations and queries.
{% endtab %}

{% tab title="Table Metadata" %}
After selecting a table, you can view its metadata, such as column names, data types, and other properties. This tab helps you understand the structure of the data that was generated or manipulated.
{% endtab %}
{% endtabs %}


---

# 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.skyone.cloud/english/skyone-studio/data-management/jsonata-jobs.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.
