Topolo Messages

Public overview of Topolo Messages in the Topolo application suite.

publicverified 2026-08-01messagesapplication

What It Is

Topolo Messages is part of the Topolo business application suite. It is a channel-agnostic business messaging surface: manage conversations, contacts, campaigns, templates, and automations in one place, with external channels (such as WhatsApp) connected behind it.

Architecture

Topolo Messages runs on Topolo's platform and signs you in through Topolo Auth. Your conversations and campaigns are scoped to your organization. External channels are connected to your workspace and appear through the same messaging surface.

Provider callbacks terminate at Topolo Nexus. Nexus owns the provider credential, external identity and status, and supplies a stable connection reference to Messages. Messages accepts only a signed, short-lived relay whose tenant, app, resource, connection, and body context all match; it does not expose a second provider-ingress path. The channel connection flow registers the environment-specific Messages relay target with Nexus and fails closed if that target is not configured.

Workspace Management

The shared Topolo workspace control reads and manages app-scoped workspace identity through Topolo Auth: authenticated users can list, create, rename, choose a default, and delete an eligible workspace. Workspace IDs and slugs remain stable and exactly one default is explicit. The selected platform workspace scopes this application's app-owned records; the app retains only domain-specific deletion guards for default or non-empty workspaces.

Runtime Surfaces

The workspace is live at https://messages.topolo.app.

API Reference

Topolo Messages exposes its capabilities as Topolo actions — managing conversations and contacts, building and launching campaigns, creating templates and automations, and connecting channel numbers — available through the Topolo SDK, CLI, and MCP surfaces. Its semantic-search action searches only within the caller's verified workspace and keeps plaintext message bodies out of the vector index.

Auth and Permissions

Access requires a Topolo account. Sign in through Topolo Auth to reach your organization's messaging workspace.

Data Ownership

Topolo Messages owns your conversations, contacts, campaigns, templates, and automations, scoped to your organization. Connected channels remain owned by their providers; Nexus reads their status and Messages stores only the stable Nexus reference plus its own inbox labels and defaults. Restricted message content uses context-bound application-layer encryption. Messages reads through primary, previous, and available Secrets Store key copies during rotation, and a scheduled decrypt canary detects both missing durable-store availability and key drift using row identities without exposing message content or ciphertext. Workspace- and protection-domain-scoped data keys carry explicit epochs and are wrapped by the Messages root key. Exact staging API version 1b2900be-917d-4a55-8316-339bad6431b4 proved its durable Secrets Store key available and decrypted 101 sampled protected rows with no exceptions. The current runtime accepts only tp2; the retired envelope reader and rewrite job are no longer shipped. Workspace owners can export their Messages data or erase its content, and aged operational records move to private archive storage under defined retention windows.

Mobile Experience

The checked-in mobile experience contract is approved in native_capability mode. Its fallback route is /conversations, its offline policy is read_through_cache, and it requires organization context.

Published permissions: inbox:read, campaigns:manage.

  • /conversations uses /api/messages/conversations with the record.list template and messages.conversations.list data source.
  • /conversations/:id uses /api/messages/conversations/:id with the record.detail template and messages.conversations.detail data source.
  • /contacts uses /api/messages/contacts with the record.list template and messages.contacts.list data source.
  • /contacts/:id uses /api/messages/contacts/:id with the record.detail template and messages.contacts.detail data source.
  • /campaigns uses /api/messages/campaigns with the record.list template and messages.campaigns.list data source.
  • /campaigns/:id uses /api/messages/campaigns/:id with the record.detail template and messages.campaigns.detail data source.
  • /templates uses /api/messages/templates with the record.list template and messages.templates.list data source.
  • /templates/:id uses /api/messages/templates/:id with the record.detail template and messages.templates.detail data source.

The native clients consume this manifest as an explicit rendering contract. A web mode record intentionally opens the product web experience; native_capability publishes the listed native routes and actions. Do not infer unlisted native behavior.

Deployments

Topolo Messages is available in production at https://messages.topolo.app.

The staging deployment at https://messages.stg.topolo.us was reverified on 2026-08-01 across its web, API, and dispatch Workers. Provider identity and status columns are absent from the sender table, the signed relay persists stable Nexus context, and both the Messages and Nexus public health endpoints are healthy.

Failure Modes

If a connected channel is disconnected, sends to that channel pause until it is reconnected rather than failing silently.

Debugging

If messages are not delivering, confirm the channel number is connected from the workspace settings.

Use It

Open TopoloMessages for the human product surface. The system handbook records its current hosts, ownership, Auth scopes, storage, deployment, failure modes, and machine artifact.

Discover the credential-scoped automation surface before making an API call:

topolo services --query topolo-messages --json
topolo actions --service topolo-messages --json
topolo actions capabilities --service topolo-messages --json

Choose an action, inspect it with topolo actions get <action-id> --json, then validate and plan a published example. The Agent Actions reference exposes the same public schemas, effects, examples, verification, and recovery guidance.

Example workflow:

  1. Confirm the active identity and organization with topolo whoami --json.
  2. Discover TopoloMessages and select one published action rather than guessing a route.
  3. Inspect its input/output schemas and published example.
  4. Validate and plan the exact payload; obtain confirmation for a mutation.
  5. Execute and perform every published verification step.

Change Log / Verification

  • Deployed the no-compatibility tp2 cutover on 2026-08-01 at exact source 455c50f1d4fd842bfc0db64eade249c56e3dfab0. The next scheduled run reported a healthy 101-row canary with durable-store continuity and no legacy migration event. Both staging organizations passed their own semantic search and received 403 on the other organization's exact workspace, with request IDs preserved.

  • Deployed the registered Nexus relay target and reverified end-to-end staging ingress on 2026-08-01 at Messages source 8cd3ffebfd23261e0bd1464d3b23083ffd35ffd8 and Nexus source 84fe731656363b303a7d3d8f924107f9f0d1bfab. A correctly signed event reached the expected workspace and was processed by the webhook queue; invalid signatures and unknown phone-number routes failed closed.

  • Deployed and reverified stable Nexus connection ownership on staging on 2026-08-01 at Messages source 409ba6047985ecf22ec490038329aaed31b820bc and Nexus source 98670312d18757d2232e454cee827222f0a39b76.

  • Inspected staging source 4b6bac511da584dfd34acd5ad2e7ad3517d38ca4 on 2026-07-31 for hierarchical envelope keys and workspace-scoped semantic search. The runtime proof that remained open at that snapshot is closed by source 455c50f1d4fd842bfc0db64eade249c56e3dfab0 above.

  • Closed that runtime gap on 2026-08-01: scheduled maintenance and the decrypt canary were healthy on 101 protected rows, and a two-organization semantic-search probe returned owner 200 with request-ID roundtrip while denying the other organization 403 on the exact same workspace.

  • Verified the fail-closed key-lifecycle canary on 2026-07-30 against exact staging source 4a2792fb8e9610c11e0680d8ceb19b0e88616cf9; the runtime correctly withheld a healthy lifecycle result while the durable store key was unavailable.

  • Added store-backed key continuity and a scheduled identity-only decrypt-drift canary for protected message content on 2026-07-28.

  • Verified the native_capability mobile experience contract and its 8 published route(s) against apps/TopoloMessages origin/staging 3f6338f8ef4a on 2026-07-27.

  • Consolidated the retired WhatsApp-specific documentation identity into this channel-agnostic canonical Messages page and verified the three-target staging deployment on 2026-07-22.

  • Converged provider ingress on Nexus and verified the signed replay-bounded Messages relay on 2026-07-22.

  • Added application-layer content protection, defined retention, and workspace export/erasure controls on 2026-07-24.

  • Verified Auth-projected workspace isolation and the complete live export/erasure lifecycle on 2026-07-24.

  • Published overview on 2026-07-20.