メインコンテンツにスキップ
商品詳細は英語で表示されます。翻訳は近日公開予定です。
Instagram & Facebook Messenger Inbox — A build-to-order ERPNext app that pulls Instagram DMs and Facebook Messenger threads i — 1/1イメージプレビュー

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.

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. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $999.00 USD; request a quote for a scoped proposal.

主な機能

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

受注生産、すべておまかせ

自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。

  1. 1

    ご注文

    一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。

  2. 2

    構築とインストール

    ECOSIRE がお客様の ERPNext 上で構築・設定・インストールします。

  3. 3

    本番稼働 + サポート

    約1週間(営業日ベース)で稼働し、本番稼働後2週間のサポートが付きます。納品したコードの不具合は無償で修正します。

技術仕様

ERPNext互換性
—
ライセンス
ライセンスの確認が必要です
Python要件
Python 3.10+
データベース
MariaDB 10.6+

この製品について

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.

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 one working week 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.

得られるもの

  • 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

これは誰のためのものですか

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.

Instagram & Facebook Messenger Inbox の比較方法

基準エコシエールカスタムビルド競合他社ERPNext 標準機能
Instagram DM + Messenger unified inboxBoth channels in one ERPNext inbox, built for your sitePossible but you build the Graph API layer yourselfOften broadcast-only or one channelNo social connector at all
Lead capture into ERPNext CRMAuto-creates Lead/Deal with source attribution via doc_eventsDepends entirely on your developer's timeRarely wired into ERPNext CRM recordsManual data entry only
Reply from inside ERPNextServer-side send via whitelisted method, logged as outboundYou implement the Send API integrationSometimes read-only or external UINot available
Comment-to-message automationPublic comment triggers private-reply DM automaticallyExtra scope for your team to designUsually not includedNot available
Frappe/ERPNext v15/v16 fitBuilt and UAT-tested against your exact versionYou own version compatibilityMay lag ERPNext releasesN/A
Code ownershipFull git repo handover, self-hostableYou own it, but you built itClosed source, vendor-lockedN/A
Delivery timeone working week from confirmed scopeUnpredictable, depends on internal roadmapInstant install but generic fitImmediate but no capability
Support and maintenancePost-go-live window plus optional ongoing supportYour team maintains itVendor SaaS support, subscription-basedCommunity only

Instagram & Facebook Messenger Inbox に関するよくある質問

How long does delivery take?

This is a build-to-order app, not an instant download. Typical delivery is one working week 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

見積もりを依頼

Instagram & Facebook Messenger Inbox のご要望をお知らせください。価格、ライセンスの選択肢、貴社に合わせたご提案を、通常1営業日以内にお送りします。

今すぐのお支払いはありません。これはチームへの見積もり依頼を送信します。価格と次のステップをメールでご案内します。