WasapFlow Bridge

com.wasapflow由 wasapflow.com 發布官方發布者v1.0.1更新於 Nov 4, 2026

Official WhatsApp Business API for your own CRM or SaaS: docs, numbers, messages, webhooks.

已驗證Streamable HTTP可網頁執行開發者工具溝通與協作商業與電商

概覽

AI 產生的概覽

WasapFlow Bridge 讓助理接入官方 WhatsApp Business API:查閱文件、查看號碼狀態、發送訊息與範本、排查 webhook 問題。

可以做什麼
  • 閱讀整合文件與逐步上線方案,取得完整文件章節
  • 列出已註冊的 WhatsApp 號碼、其 Meta 即時狀態、範本及 Bridge 方案用量
  • 產生短期有效的 Embedded Signup 連結,供商家綁定號碼
  • 從已連結號碼發送真實文字、範本與行銷訊息
  • 檢視並重新投遞失敗的 webhook 事件,建立或列出支援工單
  • 直接呼叫其他 Bridge 端點,不可逆操作需確認
適用情境
適合在透過 WasapFlow 以官方 WhatsApp Business API 建置或維護 CRM、SaaS 時使用,也適合讓助理檢查號碼狀態、發送測試訊息或排查收不到訊息的情況。
執行需求
遠端 streamable HTTP 端點,無需本機安裝。呼叫即時 API 的工具需在 x-partner-key 標頭提供合作夥伴金鑰,可從 WasapFlow 合作夥伴入口取得;文件與入門工具不需金鑰。實際接入號碼需要已綁定信用卡的合作夥伴帳戶。
安裝前請注意
發送類工具會送出真實 WhatsApp 訊息,範本與行銷訊息可能由 Meta 收費;Bridge 本身每三個號碼每月計費。合作夥伴金鑰屬機密,不應回顯給使用者。部分工具會修改或刪除資料,通用 API 工具可觸及不可逆端點,呼叫前應先確認。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 WasapFlow Bridge,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.wasapflow%2Fbridge/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "wasapflow-bridge": {
      "type": "http",
      "url": "https://officialapi.wasapflow.com/bridge/mcp"
    }
  }
}

README

WhatsApp CRM Starter: official WhatsApp Business API in your own app

A minimal, working WhatsApp CRM on the official WhatsApp Business API (Meta Cloud API) through WasapFlow Bridge. You don't need to become a Meta Tech Provider or go through Meta App Review. Clone it and run it, then let your AI (Claude Code, Cursor, Codex, Copilot) grow it into your CRM or SaaS.

It's about 400 lines of Node.js across four files, with two dependencies and no build step.

What it does

  • Connect WhatsApp button. Your client connects their number through Meta Embedded Signup. Coexistence is supported, so the business can keep using the WhatsApp Business app on their phone.
  • Signed webhooks. Incoming messages, delivery and read status, replies typed on the phone (message.echo), and chat history backfill (message.history).
  • Inbox. Conversations, unread counts, the 24-hour window, and text or template replies.
  • Multi-number. Everything is keyed by phone_number_id.
  • BSUID-safe contacts. WhatsApp usernames don't break your phone field.
  • AGENTS.md, CLAUDE.md and .cursor/rules. These tell your AI exactly how the integration works, so what it builds on top stays correct.

Run it in 5 minutes

  1. Partner account. Create a free account at https://partner.wasapflow.com/bridge/partner/register and save a card. Nothing is charged until the first number connects. After that, Bridge costs $10/month for every 3 WhatsApp numbers, and Meta bills message charges directly.
  2. Install:
    bash
    git clone https://github.com/kobaranteguh/whatsapp-crm-starter.gitcd whatsapp-crm-starternpm installcp .env.example .env
  3. Keys. Open portal → Integration and copy the Partner Key and Webhook Secret into .env.
  4. Public URL for webhooks. Deploy the app (Railway, Render, Fly, a VPS), or tunnel your local machine (cloudflared tunnel --url http://localhost:3000 or ngrok http 3000). In portal → Integration, save the webhook URL as https://<your-domain>/webhook/wasapflow.
  5. Start:
    bash
    npm start
    Open http://localhost:3000 (user admin, password = ADMIN_PASSWORD), click + Connect WhatsApp, then message that number from your phone.

Build the rest with your AI

Open the folder in your AI tool and paste one of these prompts:

Read AGENTS.md and the WasapFlow Bridge API reference. Replace lib/store.js with Postgres using Prisma, keeping the same exports. Add migrations.

Read AGENTS.md. Make this multi-tenant: users sign up, each tenant connects its own WhatsApp numbers via POST /connect/session with state = tenant id, and only sees its own inbox.

Read AGENTS.md and the Bridge docs. Add media: show incoming images and documents, and let agents send images from the composer.

Read AGENTS.md. Add a templates page: list templates with status, create new ones, and refresh on the template.status_updated webhook.

Read AGENTS.md. Add assignment and tags: assign a conversation to a staff member, tag it, and filter the inbox by tag.

Give your AI live access (optional). The WasapFlow MCP server lets it search the docs and call your Bridge account, for example to list numbers, check failed webhooks, or send a test message.

bash
claude mcp add --transport http wasapflow https://officialapi.wasapflow.com/bridge/mcp --header "x-partner-key: wf_..."
json
{ "mcpServers": { "wasapflow": { "url": "https://officialapi.wasapflow.com/bridge/mcp", "headers": { "x-partner-key": "wf_..." } } } }

Files

FileWhat it is
server.jsWebhook receiver (signature check, events), /api/*, Basic auth
lib/bridge.jsThe only module that calls Bridge (plain fetch, no SDK)
lib/store.jsJSON-file storage that you can replace with your database
public/index.htmlInbox UI
AGENTS.mdRules and recipes for AI coding tools

Links

FAQ

Do I need a Meta Business verification or app review? You don't need app review or Tech Provider status. Bridge provides both. Each business connects its own number through Meta's Embedded Signup and must follow WhatsApp's policies.

Can a business keep using WhatsApp on their phone? Yes. With Coexistence, replies typed on the phone show up in this inbox as message.echo.

Is this production-ready? The integration patterns are: signature check, deduplication, BSUID handling, multi-number, and the 24-hour window. The JSON-file storage and Basic auth are not. Swap them in for your stack (see the prompts above).

MIT licensed. © Kobaran Teguh Sdn. Bhd.

來源:README.md,提交 050e7b8

工具

16

bridge_get_started

How to integrate WasapFlow Bridge

Step-by-step plan to add the official WhatsApp Business API to the user's own CRM/SaaS with WasapFlow Bridge: account, card, keys, webhook, Connect WhatsApp button, first message. Call this first when someone wants to build or connect WhatsApp. No partner key needed.

無需輸入參數。

bridge_docs_section

Read a Bridge docs section

Return the full text of one section (with its sub-sections) of the WasapFlow Bridge docs, e.g. "Verify Incoming Webhooks", "Send Template Message", "Webhook Event Payloads", "Error Codes". No partner key needed.

輸入參數docheading必填

bridge_list_numbers

List connected WhatsApp numbers

List the WhatsApp Business Accounts (client numbers) registered to this partner, with status.

輸入參數limit

bridge_number_status

Phone number status & quality

Live status of a number from Meta: verified name, quality rating, messaging limit, name status.

輸入參數waba_id必填

bridge_send_text

Send a WhatsApp text message

Send a text message from a connected number. Free-form text only reaches people who messaged that number in the last 24 hours; otherwise use bridge_send_template. This sends a real message.

輸入參數to必填text必填waba_id必填

bridge_send_template

Send a WhatsApp template message

Send an approved template (works outside the 24-hour window). components follows the Meta Cloud API format. This sends a real message and Meta may charge for it.

輸入參數to必填name必填waba_id必填language必填components

bridge_send_marketing

Send a marketing template (Marketing Messages API)

Send an approved MARKETING template through Meta's Marketing Messages API (quality-based delivery, marketing metrics). Not onboarded yet? Meta falls back to Cloud API unless product_policy is STRICT. This sends a real message and Meta charges for it.

輸入參數to必填name必填waba_id必填language必填componentsproduct_policy

bridge_list_templates

List message templates

List the message templates of a number with their approval status.

輸入參數waba_id必填

bridge_failed_webhooks

Webhooks that failed to reach your server

Webhook events Bridge could not deliver to your webhook URL (with the error). Use when incoming messages are missing in the CRM.

輸入參數limit

bridge_retry_webhooks

Redeliver failed webhooks

Redeliver one failed webhook event (event_id) or all of them (omit event_id) after the webhook endpoint is fixed.

輸入參數event_id

bridge_usage

Bridge plan & usage

Current Bridge plan: active WhatsApp numbers, slots and the monthly Bridge fee.

無需輸入參數。

bridge_open_ticket

Open a support ticket

Open a WasapFlow support ticket. Include what happened, when (with timezone), the exact error (Meta code, fbtrace_id), what was tried and the business impact.

輸入參數message必填subject必填waba_idcategoryprioritydiagnostics

bridge_list_tickets

List support tickets

List support tickets and replies status.

輸入參數status

bridge_call_api

Call any Bridge API endpoint

Call any WasapFlow Bridge endpoint not covered by the other tools (see bridge_docs_search for paths). Irreversible endpoints need {"confirm": true} in the body. Confirm with the user before any call that sends, deletes or changes something.

輸入參數bodypath必填querymethod必填waba_id

版本歷史

2
  1. v1.0.1最新Nov 4, 2026
  2. v1.0.0Nov 4, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分