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

# Automatización

En **Automatización**, programas chats para que un Expert ejecute un prompt automáticamente en horarios definidos, como un resumen diario o un informe semanal.

### Crear un chat programado <a href="#crear-un-chat-programado" id="crear-un-chat-programado"></a>

Para crear una programación, sigue estos pasos:

1. En el menú lateral izquierdo, haz clic en **Automatización**.
2. En **Chats programados**, haz clic en el botón **+**.
3. Elige el Expert, escribe el prompt y define los horarios de ejecución.
4. Haz clic en **Crear** para guardar la cita.

{% hint style="info" %}
Puedes mantener hasta 10 programaciones. El contador en la parte inferior del panel muestra cuántas están en uso (p. ej.: **0 de 10 programaciones en uso**).
{% endhint %}

### Ejemplos de uso <a href="#ejemplos-de-uso" id="ejemplos-de-uso"></a>

* Resumen diario de noticias del sector, con fuentes.
* Recordatorio semanal con los puntos de atención de un proyecto.
* Informe mensual generado por un Expert de investigación.


---

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