application public active Verified 2026-04-16

Topolo Messaging

First-party WhatsApp Business messaging application for multi-number brand workspaces, shared inboxes, campaigns, automations, provider webhooks, and cross-application integration boundaries.

Documentation Map

What It Is

First-party WhatsApp Business messaging application for multi-number brand workspaces, shared inboxes, campaigns, automations, provider webhooks, and cross-application integration boundaries.

Architecture

Owners: platform-experience, messaging-platform

Source repos: PlatformApplications/TopoloMessaging

Dependencies: topolo-auth, topolo-bugfix

Repo shape

  • PlatformApplications/TopoloMessaging/dispatch.wrangler.toml
  • PlatformApplications/TopoloMessaging/functions/
  • PlatformApplications/TopoloMessaging/index.html
  • PlatformApplications/TopoloMessaging/migrations/
  • PlatformApplications/TopoloMessaging/package-lock.json
  • PlatformApplications/TopoloMessaging/package.json
  • PlatformApplications/TopoloMessaging/postcss.config.cjs
  • PlatformApplications/TopoloMessaging/src/
  • PlatformApplications/TopoloMessaging/tailwind.config.js
  • PlatformApplications/TopoloMessaging/topolo.cloudcontrol.json
  • PlatformApplications/TopoloMessaging/tsconfig.json
  • PlatformApplications/TopoloMessaging/tsconfig.node.json
  • PlatformApplications/TopoloMessaging/vite.config.ts
  • PlatformApplications/TopoloMessaging/wrangler.toml

Runtime Surfaces

Hosts:

https://messages.topolo.app
topolo-messaging

Config: PlatformApplications/TopoloMessaging/wrangler.toml

Main: src/worker.ts

Routes: workers.dev or asset-only surface

API Reference

Coverage: curated

Source: PlatformApplications/TopoloMessaging/functions/api/messaging/[[path]].ts

Source exists in repo: yes

Topolo Messaging is a Worker-with-assets application using shared Topolo UI Kit shell, launcher, Auth, command-palette, loading, and BugFix surfaces. It owns a Messaging D1 schema for workspaces, WhatsApp numbers, inboxes, contacts, conversations, messages, campaign drafts, automation definitions, outbound jobs, and webhook events. The app exposes /api/messaging/* for signed workspace operations, /api/auth/* as the same-origin Auth gateway, and /api/messaging/whatsapp/webhook for Meta webhook verification and signed event ingestion. Provider dispatch is queued through Cloudflare Queues; live WhatsApp Cloud API credentials must be provisioned as Worker secrets before outbound jobs move from provider_unconfigured to provider-sent states.

App API page: /reference/apps/topolo-messaging

This system currently relies on a curated or README-derived contract surface instead of a source-controlled OpenAPI spec.

Auth and Permissions

Depends on Topolo Auth: yes

Service IDs:

srv_topolo_messaging

API key scopes

automations.manage

Create and manage WhatsApp automation definitions

Resource pattern: none

campaigns.manage

Create and manage WhatsApp campaign drafts and send plans

Resource pattern: none

inbox.read

Read WhatsApp inboxes, numbers, conversations, campaigns, and automations

Resource pattern: none

messages.send

Create outbound WhatsApp message jobs

Resource pattern: none

numbers.read

Read WhatsApp Business number configuration

Resource pattern: none

Service permissions

automations:manage, campaigns:manage, context:read, inbox:read, inbox:write, messages:send, numbers:manage

Data Ownership

d1

Binding: MESSAGING_DB

Target: ed144d7f-dd7d-4e49-a645-54c0ba61be7b

Environment: default

Source: PlatformApplications/TopoloMessaging/wrangler.toml

Queues / Cron / Workflows

Queue bindings:

  • MESSAGING_OUTBOUND_QUEUE -> topolo-messaging-prod-outbound
  • MESSAGING_WEBHOOK_QUEUE -> topolo-messaging-prod-webhooks

Cron triggers

No cron triggers were detected.

Workflow signals

  • MESSAGING_OUTBOUND_QUEUE -> topolo-messaging-prod-outbound
  • MESSAGING_WEBHOOK_QUEUE -> topolo-messaging-prod-webhooks

Environment Variables and Bindings

Environment variables:

AUTH_API_URL

All wrangler bindings

  • MESSAGING_DB (d1) -> ed144d7f-dd7d-4e49-a645-54c0ba61be7b
  • MESSAGING_OUTBOUND_QUEUE (queue) -> topolo-messaging-prod-outbound
  • MESSAGING_WEBHOOK_QUEUE (queue) -> topolo-messaging-prod-webhooks

Deployments

Deployment environments: default only or not declared

Routes: workers.dev or Pages-only delivery

Observability enabled: yes

Wrangler surfaces

  • PlatformApplications/TopoloMessaging/wrangler.toml -> topolo-messaging (assets dist)

Build and deploy commands

  • build — PlatformApplications/TopoloMessaging/package.json :: tsc && vite build --mode production
  • build:worker — PlatformApplications/TopoloMessaging/package.json :: wrangler deploy --dry-run --outdir .wrangler/deploy-build
  • build:dispatch-worker — PlatformApplications/TopoloMessaging/package.json :: wrangler deploy --config dispatch.wrangler.toml --dry-run --outdir .wrangler/dispatch-deploy-build
  • preview — PlatformApplications/TopoloMessaging/package.json :: vite preview

Failure Modes

  • Neither OpenAPI nor README-derived interface detail was found.

Debugging Runbooks

Start with these entrypoints:

  • PlatformApplications/TopoloMessaging/wrangler.toml
  • PlatformApplications/TopoloMessaging/functions/api/messaging/[[path]].ts
  • PlatformApplications/TopoloMessaging/package.json

Change Log / Verification

Lifecycle: active

Last verified: 2026-04-16

Any code change to this system is expected to update the canonical docs in PlatformApplications/TopoloDocs and refresh the verification date.