Hermes BibleUnofficial Docs
← All docs Docs / Messaging Platforms

WhatsApp Business (Cloud API)

WhatsApp Business Cloud API Setup Hermes can connect to WhatsApp through Meta's official WhatsApp Business Cloud API. This is the production grade path: no Node

Messaging Platforms
Section
Messaging Platforms
Source
hermesbible.com/docs/user-guide/messaging/whatsapp-cloud

WhatsApp Business Cloud API Setup Hermes can connect to WhatsApp through Meta's official WhatsApp Business Cloud API. This is the production grade path: no Node

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Quick start
  2. Prerequisites
  3. Creating the Meta app
  4. Permanent token (production)
  5. Exposing Hermes to the internet
  6. Cloudflare Tunnel (recommended)
  7. ngrok
  8. Your own domain + reverse proxy
  9. Configuring the webhook on Meta's side
  10. Recipient whitelist (Meta-side)
  11. Allowlist (Hermes-side)
  12. Polishing your bot's WhatsApp profile
  13. Configuration reference
  14. Features

Section map

Quick start

Maps quick start to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Prerequisites

Maps prerequisites to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Creating the Meta app

Maps creating the meta app to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Permanent token (production)

Maps permanent token (production) to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Exposing Hermes to the internet

Maps exposing hermes to the internet to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Cloudflare Tunnel (recommended)

Maps cloudflare tunnel (recommended) to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

ngrok

Maps ngrok to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Your own domain + reverse proxy

Maps your own domain + reverse proxy to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Messaging Platforms doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Quick start, Prerequisites, Creating the Meta app, Permanent token (production), Exposing Hermes to the internet. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: whatsapp, business, cloud, setup, connect. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitMessaging Platforms documentation

Use when you need orientation for whatsapp business (cloud api) before applying exact upstream commands.

Verify firstQuick start

Open the source anchor for Quick start and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Messaging Platforms, then open the linked source page for exact current syntax.
  2. Start with the source section for Quick start; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Prerequisites if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Credentials

Treat every token, OAuth grant, secret manager entry, and API key as production-sensitive. Verify least privilege and revocation before reuse.

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

External messages

Keep human review before sending public posts, customer messages, trading instructions, or team notifications.

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page