Topolo Campaigns

What It Is

Topolo Campaigns coordinates measurable campaigns that connect physical or digital codes to offers and customer journeys. It keeps campaign batches, code placements, engagement events, and redemptions together while linking to resources owned by other Topolo applications.

Architecture

The application uses the shared Topolo landing page, shared login page, auth callback handling, and shared Topolo shell from the outset.

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 planned production host is https://campaigns.topolo.app, with public entry at /, sign-in at /login, and callback completion at /auth/callback.

API Reference

The authenticated API exposes Campaigns workspaces, offers, campaigns, code batches, placements, journey events, redemptions, dashboards, and typed links to app-local resources. Its action catalog is discoverable by Topolo CLI and MCP clients with the permissions of the current credential.

Auth and Permissions

Signed browser and API requests use Topolo Auth through the topolo-campaigns service slug. Organizations can grant access to selected Campaigns workspaces, including simultaneous access to several resources where the client supports it.

Data Ownership

Campaigns owns its own organization- and workspace-scoped records. Quro series, Web sites, Forms forms, CRM workspaces, Chat channels, Calendar event types, and Notify events remain owned by their respective applications and are connected by explicit resource links rather than a universal workspace ID.

Deployments

The planned production host is https://campaigns.topolo.app. Staging mirrors the scaffold at https://campaigns.stg.topolo.us.

Failure Modes

• service registration and app routing can drift while the product is still planned
• a linked resource is removed in its owning application without updating the Campaigns integration

Debugging

• use the matching internal handbook for operational details
• verify the system registry entry before deployment or service-registration changes

Use It

Open Topolo Campaigns 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-campaigns --json
topolo actions --service topolo-campaigns --json
topolo actions capabilities --service topolo-campaigns --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 Topolo Campaigns 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

• Reconciled this page against apps/TopoloCampaigns origin/staging 7097990bc15e on 2026-07-24 after reviewing every docs-relevant commit since its previous verification watermark. Dependency-only currency commits were checked by the fleet production-dependency gate and did not change this page's product contract.

• Added workspace-scoped orchestration and credential-discoverable actions on 2026-07-14.

• Scaffold generated on 2026-07-13; first-party scaffolding now uses restricted topolo-platform apps scaffold.