> For the complete documentation index, see [llms.txt](https://docs.flowbridge.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowbridge.app/documentation/social-integrations/instagram-messenger.md). # Instagram Messenger {% embed url="" %} To integrate Instagram Messenger with your Voiceflow project, you will need to follow the same steps as shown in the [quick start](/documentation/getting-started/quickstart.md) section. In short, in the admin panel, you will need to: 1. Create a Client Company 2. Create a Voiceflow Project and associate the Voiceflow project to the Client Company 3. Create a Client Integration and associate the Client Company & Voiceflow Project to the integration. ## Instagram Specific Steps Once you're on the `Create Client Integration` page, and have selected Intsagram as the social channel, you will have some options to choose from. First of, you will need to choose a provider. There are 2 provider types: ### Meta API (Embedded login) - :white\_check\_mark: **RECOMMENDED** This option is the quickest and easiest way to connect. Once selected, you will see a button `Login with Facebook` which will open a popup allowing you to connect your Facebook/Meta account. From here you can choose to create a new or use an existing business asset and page. Follow the steps as provided by Meta within the popup, you can continue on in the embedded login flow until it closes. Once closed, FlowBridge will try to make a connection to the Meta API. You will need to select which page you want to connect and click on `create` . Once the creation is complete, you're ready to go! Go ahead and open Instagram (Please do this on mobile) and try to send a message to the page. Your voiceflow flow will now respond as per your configuration. #### Manual token (bring your own app) - :x: NOT RECOMMENDED Optionally, you can create your own app on [https://developers.facebook.com](https://developers.facebook.com/) and connect your own API token here. This allows you to have more control over the connection though we do not provide support for this method and is only advised for expert users who require that extra level of control. If you do end up using this method, you will need to create the integration, and on the view integration page, you will see a button on the top right which allows you to get the Webhook URL and Verification code. Note that going with this approach will require your app to pass Meta's App Review process. This can generally take some days and often gets disapproved multiple times ## Extra Considerations * Meta never implemented all the functions in to their web version of Instagram. Buttons for example do not appear on the web version, but DO appear on the mobile version. It's recommended to test your integration using the Instagram mobile application * Keep your Access Token secure; it’s the key to your Instagram Messenger integration. * Cards must have at least 1 button, and no more then 3 * Buttons (on cards or otherwise) only allow for a total of 20 characters for Instagram Messenger --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.flowbridge.app/documentation/social-integrations/instagram-messenger.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.