> 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.md).

# Flujos

Un flujo es un conjunto de operaciones ejecutadas de forma secuencial, que está vinculado a uno o más **disparadores** que inician su ejecución, para luego agregar una o más operaciones de módulos existentes o incluso crear parámetros del flujo.

Al crear un flujo, podrás integrar diferentes sistemas fácilmente, utilizando los módulos y operaciones que crees o aquellos disponibles mediante compartición en Skyone Studio.

### Cómo acceder

Para acceder, haz clic en una integración para acceder al flujo deseado.

En las páginas siguientes, encontrarás toda la documentación sobre los **"Flujos"**:

* [**Gestión de los flujos**](/espanol/skyone-studio/modulos/gestion-de-modulos.md)
* [**Disparadores del flujo**](/espanol/skyone-studio/integraciones/flujos/disparadores.md)
* [**Módulos de herramientas**](/espanol/skyone-studio/integraciones/flujos/modulos-de-herramientas.md)


---

# 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.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.