WasapFlow Bridge

com.wasapflowPublished by wasapflow.comOfficial publisherv1.0.1Updated Nov 4, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

WasapFlow Bridge gives an assistant the official WhatsApp Business API: docs lookup, number status, sending messages and templates, and webhook troubleshooting.

What you can do
  • Read integration docs and step-by-step onboarding plans, including full doc sections
  • List registered WhatsApp numbers, their live Meta status, templates and Bridge plan usage
  • Create short-lived Embedded Signup connect links for businesses to link their numbers
  • Send real text, template and marketing messages from a connected number
  • Inspect and redeliver failed webhook events, and open or list support tickets
  • Call other Bridge endpoints directly, with confirmation required for irreversible ones
When to use it
Useful when building or maintaining a CRM or SaaS on the official WhatsApp Business API through WasapFlow, or when an assistant needs to check number status, send a test message, or debug missing incoming messages.
Requirements
Remote streamable HTTP endpoint; no local install. Live API tools need a partner key sent in the x-partner-key header, obtained from the WasapFlow partner portal; docs and getting-started tools work without it. A partner account with a card on file is needed for actual numbers.
Before you install
Sending tools deliver real WhatsApp messages, and Meta may charge for template and marketing messages; Bridge itself is billed per three numbers per month. The partner key is a secret and should not be echoed back. Some tools change or delete data, and the generic API tool can reach irreversible endpoints, so confirm before such calls.

Installation

In SourceWeft

  1. Open WasapFlow Bridge in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.wasapflow%2Fbridge/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "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.

Source: README.md at commit 050e7b8

Tools

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.

Takes no parameters.

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.

Parametersdocheadingrequired

bridge_list_numbers

List connected WhatsApp numbers

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

Parameterslimit

bridge_number_status

Phone number status & quality

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

Parameterswaba_idrequired

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.

Parameterstorequiredtextrequiredwaba_idrequired

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.

Parameterstorequirednamerequiredwaba_idrequiredlanguagerequiredcomponents

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.

Parameterstorequirednamerequiredwaba_idrequiredlanguagerequiredcomponentsproduct_policy

bridge_list_templates

List message templates

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

Parameterswaba_idrequired

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.

Parameterslimit

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.

Parametersevent_id

bridge_usage

Bridge plan & usage

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

Takes no parameters.

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.

Parametersmessagerequiredsubjectrequiredwaba_idcategoryprioritydiagnostics

bridge_list_tickets

List support tickets

List support tickets and replies status.

Parametersstatus

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.

Parametersbodypathrequiredquerymethodrequiredwaba_id

Version history

2
  1. v1.0.1LatestNov 4, 2026
  2. v1.0.0Nov 4, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts