Product details are displayed in English. Translations coming soon.
Quick facts
- Price
- $299.00 USD
- ERPNext versions
- —
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
एक बार की खरीदारी
Instagram & Facebook Messenger Inbox
A build-to-order ERPNext app that pulls Instagram DMs and Facebook Messenger threads into your CRM, captures leads automatically, and lets your team reply from inside ERPNext. ECOSIRE scopes, builds, installs, and supports it for your Frappe v15/v16 site.
$299.00USD
अभी कोई भुगतान नहीं। यह हमारी टीम को एक कोटेशन अनुरोध भेजता है — हम कीमत और अगले चरणों के साथ ईमेल द्वारा संपर्क करेंगे।
प्रमुख सुविधाएँ
Meta Graph API integration for both Instagram Direct Messaging and the Facebook Messenger Platform under a single connected `Social Account` DocType
Whitelisted webhook endpoint with `X-Hub-Signature-256` HMAC verification and guest access, so Meta's servers can post events securely
Inbound events enqueued to Frappe background jobs (`frappe.enqueue`) to absorb DM bursts without blocking the webhook response
`Social Conversation` parent DocType with a child `Social Message` table storing direction, timestamp, and Meta message id for idempotent de-duplication
Reply-from-ERPNext: agents send outbound messages via a server-side whitelisted method that posts to the Meta Send API and logs the outbound turn
`hooks.py` `doc_events` handler that matches inbound senders to an existing `Contact` or auto-creates a `Lead` with the social handle and source channel
Conversation-to-record linking so any thread can be attached to a `Lead`, `CRM Deal`, or Helpdesk `HD Ticket` with a dynamic link
Comment-to-message automation that detects comments on posts/ads and triggers a private-reply DM via the Meta comment reply API
Encrypted long-lived Page/IG access token storage using Frappe's `Password` fieldtype, with scheduler-driven refresh before expiry
Scheduler events (`scheduler_events` in `hooks.py`) for token refresh, failed-send retry with backoff, and reconciliation of dropped webhooks
Role-profile and permission wiring so only Social Agent / Sales roles see conversations, respecting ERPNext's standard permission model
Client script and desk UI for a threaded inbox view with unread indicators, quick-reply, and one-click lead/deal creation
24-hour messaging-window handling with message-tag support so replies outside the standard window comply with Meta policy
Attachment handling for images and media sent through DMs, stored as Frappe `File` records against the conversation
REST API exposure so external tools or dashboards can read conversation and lead-conversion data through Frappe's standard `/api/resource` endpoints
इस उत्पाद के बारे में
D2C brands increasingly close sales in the DMs. A customer asks "is this back in stock?" under an Instagram post, sends a Messenger question about sizing, and buys within the hour. But those conversations live in the Meta Business Suite inbox, completely disconnected from ERPNext. Reps tab back and forth between apps, promising leads never become Lead or CRM Deal records, response times slip, and there is zero reporting on which social conversations actually convert to revenue. ERPNext core has strong CRM and helpdesk primitives, but it ships with no Instagram or Messenger connector. The Meta Graph API integration, webhook handling, token lifecycle, and a two-way conversation UI simply do not exist out of the box, and most generic "social" marketplace apps are broadcast schedulers rather than inbox tools wired into your CRM.
Instagram & Facebook Messenger Inbox क्यों चुनें
Meta Graph API integration for both Instagram Direct Messaging and the Facebook Messenger Platform under a single connected `Social Account` DocType
Whitelisted webhook endpoint with `X-Hub-Signature-256` HMAC verification and guest access, so Meta's servers can post events securely
Inbound events enqueued to Frappe background jobs (`frappe.enqueue`) to absorb DM bursts without blocking the webhook response
`Social Conversation` parent DocType with a child `Social Message` table storing direction, timestamp, and Meta message id for idempotent de-duplication
Reply-from-ERPNext: agents send outbound messages via a server-side whitelisted method that posts to the Meta Send API and logs the outbound turn
`hooks.py` `doc_events` handler that matches inbound senders to an existing `Contact` or auto-creates a `Lead` with the social handle and source channel
ECOSIRE builds a proper Frappe app for this: its own module with a clean hooks.py, versioned DocTypes, and permission wiring, that connects to the Meta Graph API (Instagram Messaging plus the Messenger Platform) and mirrors every inbound and outbound message into ERPNext. A Social Conversation DocType groups messages by contact and channel; a child Social Message table stores each turn with direction, timestamp, and Meta message id for idempotency; and a Social Account DocType holds the connected Facebook Page / Instagram Professional account plus its encrypted long-lived access token. Inbound events arrive at a whitelisted webhook endpoint (@frappe.whitelist(allow_guest=True)) that verifies the X-Hub-Signature-256 HMAC before enqueuing work to a background job, so bursts of DMs never block the request.
On top of that data model we build the workflow you actually want. A hooks.py doc_events handler on inbound messages runs lead-capture logic: match the sender against an existing Contact, or create a new Lead with the social handle, first message, and source channel, then link the Social Conversation to that Lead, CRM Deal, or Helpdesk HD Ticket. Agents reply from inside ERPNext through a custom desk page or Frappe UI form; the reply is posted back to Meta via a server-side whitelisted method and stored as an outbound Social Message. A comment-to-message automation watches for comments on your posts and ads and triggers a private-reply DM using Meta's comment API, so a public "how much?" becomes a private sales thread without manual work. Scheduler events refresh long-lived tokens before expiry, retry failed sends, and reconcile any webhook the platform dropped.
Because this is built to order, nothing is a black box. We start with a scoping call to confirm your channels, CRM routing rules, role profiles, and whether conversations should land as Leads, Deals, or Tickets. We build against Frappe/ERPNext v15 or v16 to match your site, run UAT on a staging bench, then install on production behind your own Meta app and tokens. Typical delivery is 2 to 4 weeks from confirmed scope. You receive the full source in a git repository, so you own the code and can extend or self-host it independently of ECOSIRE.
What you get
- Installable source code for your version of the app, delivered as a Frappe app installable via `bench get-app` / `bench install-app`
- Installation and configuration on your bench, including Meta app connection, webhook registration, token setup, and channel wiring
- Technical documentation covering the DocType schema, `hooks.py` events, webhook contract, and whitelisted methods for your developers
- End-user guide plus a live training session for your sales and support agents on the inbox and lead-capture workflow
- Post-go-live support window for bug fixes and configuration adjustments after production launch
- UAT on a staging bench with an agreed test plan, plus a documented rollback plan before production install
- Full git repository handover so you own and can extend or self-host the code independently
- Configuration of role profiles and permissions mapped to your team structure
Who this is for
D2C brand owner selling through social DMs
Runs an Instagram-first apparel or beauty brand on ERPNext and loses track of sales conversations scattered across Meta Business Suite. Needs every DM to become a trackable lead so no ready-to-buy customer slips through.
Social media / community manager
Handles a high volume of Instagram and Messenger conversations daily and wants one threaded inbox inside ERPNext with quick replies, unread indicators, and one-click hand-off to sales, instead of juggling the Meta app and a spreadsheet.
Sales / CRM lead
Owns the `Lead` and `CRM Deal` pipeline and needs social conversations to route automatically into CRM with source attribution, so social becomes a measurable channel with real conversion reporting.
ERPNext administrator / in-house developer
Maintains the Frappe site and wants a clean, documented app with proper DocTypes, permission wiring, and a git repo they can audit and extend, rather than an opaque third-party integration.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Instagram & Facebook Messenger Inbox app ZIP from your account dashboard.
Add the app to your bench
Extract the ZIP into your bench's apps folder, or run `bench get-app` with the path to the extracted app.
Install on your site
Run `bench --site SITE_NAME install-app APP_NAME` followed by `bench migrate` to install Instagram & Facebook Messenger Inbox and apply its schema.
Activate your license
Open the ECOSIRE License settings on your site and activate your license key. Requires the free ecosire_connect and ecosire_license_client apps.
How Instagram & Facebook Messenger Inbox Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Instagram DM + Messenger unified inbox | Both channels in one ERPNext inbox, built for your site | Possible but you build the Graph API layer yourself | Often broadcast-only or one channel | |
| Lead capture into ERPNext CRM | Auto-creates Lead/Deal with source attribution via doc_events | Depends entirely on your developer's time | Rarely wired into ERPNext CRM records | |
| Reply from inside ERPNext | Server-side send via whitelisted method, logged as outbound | You implement the Send API integration | Sometimes read-only or external UI | |
| Comment-to-message automation | Public comment triggers private-reply DM automatically | Extra scope for your team to design | Usually not included | |
| Frappe/ERPNext v15/v16 fit | Built and UAT-tested against your exact version | You own version compatibility | May lag ERPNext releases | |
| Code ownership | Full git repo handover, self-hostable | You own it, but you built it | Closed source, vendor-locked | |
| Delivery time | 2 to 4 weeks from confirmed scope | Unpredictable, depends on internal roadmap | Instant install but generic fit | |
| Support and maintenance | Post-go-live window plus optional ongoing support | Your team maintains it | Vendor SaaS support, subscription-based |
Frequently Asked Questions about Instagram & Facebook Messenger Inbox
+How long does delivery take?
This is a build-to-order app, not an instant download. Typical delivery is 2 to 4 weeks from confirmed scope. After the scoping call we agree on channels, CRM routing, and roles, then build on Frappe/ERPNext v15 or v16, run UAT on a staging bench, and install on production. Timeline depends on how many channels and custom routing rules you need.
+How do support and updates work after go-live?
Every build includes a post-go-live support window for bug fixes and configuration tweaks. Because you receive the full git repository, your own team can maintain and extend the app, or you can engage ECOSIRE for ongoing support, Meta API version upgrades, and new features on a separate agreement.
+Do I need my own Meta app and access tokens?
Yes. The app connects to your own Meta app with the required Instagram Messaging and Messenger permissions, using your Facebook Page and Instagram Professional account. We handle the technical setup, webhook registration, and encrypted token storage during installation, and we can guide you through the Meta app review process where required.
+Which ERPNext versions are supported?
We build against Frappe/ERPNext v15 or v16 to match your production site. We confirm your exact version during scoping and target it specifically, so the app is validated on a staging bench for your version before it reaches production.
+Can conversations become Leads, Deals, or Tickets?
Yes, that routing is part of scoping. Inbound messages can auto-create a `Lead`, link to an existing `Contact`, or open a `CRM Deal` or Helpdesk `HD Ticket`. We wire the `hooks.py` doc-event logic to your rules, so an incoming DM lands exactly where your team works.
+Will this comply with Meta's messaging policies?
The app respects the 24-hour standard messaging window and supports message tags for permitted follow-ups outside it. Webhook events are verified with HMAC signature checking, and tokens are stored encrypted. We build to Meta's current platform policies at the time of delivery.
+Do we own the code?
Yes. You get the complete source in a git repository at handover. You can self-host, audit, and extend it independently of ECOSIRE. There is no lock-in and no per-message SaaS fee from us.
कोटेशन का अनुरोध करें
Instagram & Facebook Messenger Inbox
A build-to-order ERPNext app that pulls Instagram DMs and Facebook Messenger threads into your CRM, captures leads automatically, and lets your team reply from inside ERPNext. ECOSIRE scopes, builds, installs, and supports it for your Frappe v15/v16 site.
- Meta Graph API integration for both Instagram Direct Messaging and the Facebook Messenger Platform under a single connected `Social Account` DocType
- Whitelisted webhook endpoint with `X-Hub-Signature-256` HMAC verification and guest access, so Meta's servers can post events securely
- Inbound events enqueued to Frappe background jobs (`frappe.enqueue`) to absorb DM bursts without blocking the webhook response
- `Social Conversation` parent DocType with a child `Social Message` table storing direction, timestamp, and Meta message id for idempotent de-duplication