Haboo Facebook & Instagram Messenger Integration
by Haboo Technologies Pvt Ltd https://www.habootechnologies.com$ 1.00
Facebook & Instagram DMs,
Inside Odoo Discuss
Connect your Meta Graph API and receive Facebook Messenger and Instagram DMs directly inside Odoo â with rich media support, message templates, and a full message history model for each platform.
messenger.provider model authenticates via Meta's Graph API â validate the connection with the /me endpoint directly from Odoo settings.messenger.template model stores reusable message templates â with model binding, body HTML, language, and component definitions.GenerateMessengerVerifyToken method creates the required verification token for the Meta webhook subscription setup.Facebook Messenger and Instagram DMs unified in Odoo
Meta's Graph API is the official way to build messaging integrations for Facebook Messenger and Instagram Direct. This module connects Odoo to that API through the messenger.provider model â which handles authentication state, Graph API URL, token, account ID, and connection validation via a live /me endpoint check.
Separate history models for Facebook Messenger and Instagram each support image, document, audio, and video media types â keeping conversation history rich and complete. The Messenger Template model stores reusable outbound templates with body HTML, language, state (draft/imported/added), and template component definitions. A verify token generator handles the Meta webhook subscription handshake without any manual code.
Connect, receive, and reply in three steps
Create a Messenger Provider record with your Graph API URL, access token, and account ID. Generate the verify token and register it as your Meta webhook. Click Reload Status to validate the live connection.
Inbound Messenger and Instagram messages are stored in their respective history models with full media type support â text, image, document, audio, and video all captured as separate records.
Agents select a saved Messenger Template and send from the history record â outbound messages are routed back through the Graph API to the correct platform and recipient.
Everything the module gives you
messenger.provider stores Graph API URL, access token, account ID, and authentication state. Live connection validated by calling the /me endpoint directly from Odoo.
Dedicated message history model for Facebook Messenger with support for all rich media types: image, document, audio, and video â each stored with sender details and timestamp.
Parallel history model for Instagram Direct Messages â same rich media type structure as Messenger, keeping both platforms' history cleanly separated and individually searchable.
messenger.template stores reusable outbound templates with name, provider, model binding, body HTML, language, state (draft/imported/added), and component definitions.
GenerateMessengerVerifyToken creates the verification token needed for the Meta webhook subscription handshake â no manual token generation or config file editing required.
The provider model tracks graph_api_authenticated state and authentication type â so Odoo always shows whether the Meta connection is live and valid.
The provider stores the Meta account's username and account_id â so messages are always routed to and from the correct verified business account.
The template_components_ids One2many on each template stores header, body, and footer component definitions â enabling structured Meta template messages with approved layouts.
Who needs this module
Any business that receives customer messages via Facebook Messenger can keep all conversations inside Odoo â with rich media history and template-based responses, without needing the Facebook dashboard open.
Direct-to-consumer brands receiving Instagram DMs about products can capture those messages in Odoo â linking them to partner records and CRM leads without toggling between Meta Business Suite and Odoo.
Support teams handling customers across Facebook and Instagram can centralise all message history in one place â separate models for each platform keep the data clean while a single Odoo interface covers both.
Every capability, listed plainly
messenger.provider â Graph API connection with live validation via /me endpointmessenger.template â name, provider, model binding, body HTML, language, state, component definitionsGenerateMessengerVerifyToken â creates the Meta webhook subscription verify tokengraph_api_authenticated state, username, and account IDbase and mail. Requires a Meta developer app with Messenger and Instagram Graph API access.Our Odoo Services

Need Help?
Questions about installation, configuration, or customisation? We're here â just write to us.
habootechnologies@gmail.com
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 14400 |
| Technical Name |
haboo_facebook_instagram_messenger |
| License | OPL-1 |
| Website | https://www.habootechnologies.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module