> For the complete documentation index, see [llms.txt](https://docs.omnileads.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnileads.net/configuracion-de-instagram.md).
# Configuración de Instagram
[**Meta**](https://facebook.com)**,** líder global en plataformas digitales como **Facebook**, **Instagram** y **WhatsApp**, pone a disposición de las empresas soluciones oficiales y seguras para interactuar con sus clientes de manera directa y eficiente.
A través de la **API oficial de Instagram**, las organizaciones pueden integrar sus redes sociales en OMniLeads y diseñar estrategias de atención omnicanal, automatizando procesos, optimizando la gestión de conversaciones y elevando significativamente la experiencia del cliente.
**La integración nativa entre OMniLeads e Instagram** permite aprovechar al máximo la robusta infraestructura del ecosistema Meta, garantizando altos niveles de confiabilidad y habilitando funcionalidades avanzadas como bots interactivos, automatizaciones y control integral de la cuenta de negocio.
De esta manera, **OMniLeads** se posiciona como una *plataforma omnicanal open source de última generación*, preparada para operar de forma oficial con **Meta**, ofreciendo a las empresas una solución escalable, moderna y alineada con los estándares internacionales de comunicación digital.
---
# 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.omnileads.net/configuracion-de-instagram.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.
