> 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/espanol/skyone-studio/integraciones/flujos/modulos-de-herramientas/modulo-file-job-execute.md).
# Módulo File Job Execute
### Definición
El “File Job Execute” es un módulo instrumental que permite la ejecución de acciones sobre archivos dentro de un flujo de trabajo, posibilitando acciones en lote y la ejecución de operaciones sobre archivos dentro del flujo.
{% hint style="warning" %}
Para utilizar este módulo, es necesario tener habilitado Data Management y haber configurado previamente un Data Engine.
{% endhint %}
#### Agregar el módulo “File Job Execute”
El módulo “File Job Execute” aparece en la opción Herramientas dentro de la edición de un flujo.\
Después de seleccionarlo, se mostrará la ventana modal de configuración inicial.
Completa o selecciona los siguientes ítems para ejecutar un **File Job** en tu flujo:
* Selecciona el **Data Engine**
* Elige el File Job deseado haciendo clic en el ítem correspondiente
Para finalizar, haz clic en “**Guardar**”.
### Editar el módulo
Para editarlo, basta con hacer clic en “[**Editar**](broken://pages/Q2I7yv0ccj5S8pDfRuyg)” dentro del módulo.
En “**Acciones**”, verifica los grupos de lectura, escritura y tags del File Job.
Haz clic en “**Siguiente**” para ser redirigido a la pantalla de prueba de la ejecución.
Si todo está correcto, finaliza haciendo clic en “**Guardar**”.\
---
# 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/espanol/skyone-studio/integraciones/flujos/modulos-de-herramientas/modulo-file-job-execute.md?ask=&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.
