> For the complete documentation index, see [llms.txt](https://docs.videsk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videsk.io/es-dashboard/extensiones.md).

# Extensiones

- [¿Qué son las extensiones?](https://docs.videsk.io/es-dashboard/extensiones/que-son-las-extensiones.md): Las extensiones te permiten que tus agentes vean tus propias herramientas (CRM, ticketera, fichas de cliente, etc.) directamente dentro de la consola de Videsk, sin cambiar de pestaña.
- [Crear una extensión](https://docs.videsk.io/es-dashboard/extensiones/crear-extension.md): Cómo registrar una nueva extensión en tu cuenta para que tus agentes la vean durante las llamadas.
- [Editar una extensión](https://docs.videsk.io/es-dashboard/extensiones/editar-extension.md): Cómo modificar una extensión existente y qué pasa con las llamadas que están ocurriendo en ese momento.
- [Eliminar una extensión](https://docs.videsk.io/es-dashboard/extensiones/eliminar-extension.md): Cómo eliminar una extensión que ya no usas y qué consecuencias tiene en la operación.
- [Consideraciones](https://docs.videsk.io/es-dashboard/extensiones/consideraciones.md): Puntos importantes a tener en cuenta al operar con extensiones en tu cuenta.


---

# 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.videsk.io/es-dashboard/extensiones.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.