GOWA

Go WhatsApp — Built for Efficient Memory Use

Support GOWA

Does GOWA save you development time or power your business? Help sustain the project through GitHub Sponsors.

Sponsorship helps make time for:

• Investigating bugs and keeping up with WhatsApp and whatsmeow changes.
• Improving regression tests, documentation, and integration examples.
• Reviewing contributions and preparing releases.

Monthly sponsorship helps make ongoing maintenance more sustainable. Individuals and teams are welcome.

Sponsor GOWA on GitHub →

Not ready to sponsor? Reproducible bug reports, documentation improvements, and sharing GOWA also help.

---

ARM, AMD64, and MCP Support

Download:

• Release
• Docker Hub
• GitHub Container Registry

Documentation

Read the detailed GOWA documentation for setup, authentication, device management, webhooks, examples, and the API reference. The documentation tracks merged main, including changes after v9.7.0. Check the release notes and GET /app/info when using a pinned binary or container tag.

• Experimental interactive messages covers native-flow buttons, location requests, and image carousels. POST /send/interactive is immediate-only and REST-only; recipient compatibility varies.
• Webhook payloads describes event schemas and signing.
• Chatwoot, MCP OAuth, Neon, and media storage provide integration and operations guides.
• OpenAPI defines the machine-readable REST contract, including /send/interactive.

n8n Community Node

• n8n package
• Go to Settings → Community Nodes, enter @aldinokemal2104/n8n-nodes-gowa, and select Install.

Breaking Changes

• v6

  • REST mode requires <binary> rest instead of <binary>.
    • Example: ./whatsapp rest instead of ./whatsapp.
  • MCP mode required <binary> mcp.
    • Example: ./whatsapp mcp.

• v7

  • Starting with version 7.x, binaries are built with GoReleaser and can be downloaded from the latest release.

• v8

  • Multi-device support: You can now connect and manage multiple WhatsApp accounts simultaneously in a single server instance.

  • New Device Management API: New endpoints under /devices manage multiple devices.

  • Device scoping required: All device-scoped REST API calls now require either:

    • X-Device-Id header, or
    • device_id query parameter.
    • If only one device is registered, it is used as the default.

  • WebSocket device selection: Connect to /ws?device_id=<id> for the device middleware. The current WebSocket hub broadcasts dashboard events to all authenticated subscribers. This parameter does not isolate events between accounts; use per-device webhooks for application integrations.

  • Remote UI support: CORS allows the Authorization and X-Device-Id headers, so a standalone web UI (for example, gowa-ui) hosted on another origin can call the API directly. GET /app/info exposes the version and media size limits. Because browsers cannot set headers on WebSocket connections, pass /ws?device_id=<id>&authorization=<base64(user:pass)> when Basic Auth is enabled (use TLS—the credential is visible in the URL).

  • Webhook payload changes: All webhook payloads now include a top-level device_id field identifying which device received the event:

    {
      "event": "message",
      "device_id": "[email protected]",
      "payload": { ... }
    }
    

以上为 README 的开头部分。其余内容请阅读原文。 查看完整 README ↗