> 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/integrations/flows/tool-modules/file-job-execute-module.md).

# File Job Execute Module

### Definition

The "**File Job Execute**" tool module allows you to run actions on files within a workflow, enabling batch operations and file handling directly in the workflow.

{% hint style="warning" %}
To use this module, [**Data Management**](https://docs.skyone.cloud/english/skyone-studio/data-management.md) must be enabled, and a [**Data Engine**](https://docs.skyone.cloud/english/skyone-studio/data-management/engine.md) must be configured beforehand.&#x20;
{% endhint %}

### Add the "File Job Execute” Module

The "**File Job Execute**" module appears under the Tools section when editing a flow. After clicking to add it, the initial configuration modal will be displayed.

\[gif]

Fill in or select the following items to execute a File Job in your flow:

* Select the Data Engine
* Choose the desired File Job by clicking the corresponding item.

\[imagem]

To finish, click **"Save".**

#### Edit module

To edit the module, simply click **"**[**Edit**](https://docs.skyone.cloud/english/skyone-studio/integrations/flows/editing-triggers-and-modules.md#edit-component)**"** on the module.

Under "**Actions"**, check the read groups, write groups, and tags associated with the File Job.

Click **"Next"** to be redirected to the test execution screen.

If everything looks good, just click **"Save".**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.skyone.cloud/english/skyone-studio/integrations/flows/tool-modules/file-job-execute-module.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
