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:
Dependencies: topolo-auth, topolo-bugfix, applications-packages
Repo shape
No repo surface entries were detected from the registered repo paths.
Runtime Surfaces
Hosts:
https://messages.topolo.app https://messages.stg.topolo.us No wrangler surface was discovered under the registered repo paths.
API Reference
Coverage: curated
Source: PlatformApplications/TopoloMessaging/functions/api/messaging/[[path]].ts
Source exists in repo: no
Topolo Messaging is a Worker-with-assets application using shared Topolo UI Kit shell, launcher, Auth, command-palette, loading, and BugFix surfaces. Browser login and callback-code redemption are owned by the shared Topolo Auth client after the app resolves the Auth-owned service slug topolo-messaging at runtime, with embedded password-login success completed through Messaging app navigation after shared Auth token persistence. Messaging owns a 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. Auth API-key scopes for the resolved Messaging service id mirror all seven Messaging permissions and are synced to production D1.
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_avvCARb8AleC API key scopes
Create and manage WhatsApp automation definitions
Resource pattern: workspace/{workspace_id}/automation/{automation_id}
Create and manage WhatsApp campaign drafts and send plans
Resource pattern: workspace/{workspace_id}/campaign/{campaign_id}
Look up Auth-owned user and organization context from Messaging
Resource pattern: none
View WhatsApp inboxes, conversations, numbers, campaigns, and automations
Resource pattern: none
Manage inbox conversation state and assignments
Resource pattern: none
Create outbound WhatsApp message jobs
Resource pattern: workspace/{workspace_id}/number/{number_id}
Register and manage WhatsApp Business phone numbers
Resource pattern: workspace/{workspace_id}/number/{number_id}
Service permissions
automations:manage, campaigns:manage, context:read, inbox:read, inbox:write, messages:send, numbers:manage
Data Ownership
No storage bindings were derived from wrangler configuration.
Queues / Cron / Workflows
Queue bindings:
No queue bindings were detected.
Cron triggers
No cron triggers were detected.
Workflow signals
No explicit queue/workflow script or cron signal was discovered.
Environment Variables and Bindings
Environment variables:
No environment variables were derived from wrangler configuration.
All wrangler bindings
No bindings were derived from wrangler configuration.
Deployments
Deployment environments: default only or not declared
Routes: workers.dev fallback or no explicit route declared
Observability enabled: no explicit setting found
Failure Modes
- No wrangler.toml surface was discovered under the registered repo paths.
- The registered contract source is missing: PlatformApplications/TopoloMessaging/functions/api/messaging/[[path]].ts
- Neither OpenAPI nor README-derived interface detail was found.
Debugging Runbooks
Start with these entrypoints:
- PlatformApplications/TopoloMessaging/functions/api/messaging/[[path]].ts
Change Log / Verification
Lifecycle: active
Last verified: 2026-05-14
Any code change to this system is expected to update the canonical docs in PlatformApplications/TopoloDocs and refresh the verification date.