Workflows

Agent capability parity

See what humans, CLI agents, MCP clients, and API workers can do through the same governed GTM Brain boundary.

GTM Brain exposes one governed product contract through the UI, CLI, MCP, and authenticated HTTP API. The transport changes; tenant scope, campaign scope, schemas, policy, approval, idempotency, audit, adapter delivery, and recovery do not. The live get_catalog or gtm catalog --json response is always authoritative for one connected registration.

Parity does not mean identical presentation

The UI may provide rich editors, while the CLI uses typed JSON and MCP exposes tools. A capability is considered in parity only when each supported transport reaches the same projection or governed action. Security administration, secret entry, and other deliberate exceptions are listed below rather than being silently omitted.

Covered agent surface

  • Workspace health and activity
  • Account context and knowledge search
  • Knowledge authoring
  • ICP mutation lifecycle
  • Company and people import/update/suppression
  • List authoring and export
  • Campaign authoring, readiness, lifecycle, and launch
  • Artifact drafting, review, decision, publication, and archival
  • Proof and bounded messaging skill requests
  • Versioned messaging-policy authoring and lifecycle
  • Pending approval discovery and exact draft decisions
  • Reply classification and drafting
  • Meeting outcome recording
  • Provider reply-delivery reconciliation
  • Approved paused Instantly activation through campaign pass only; no direct provider bind, pause, or connect
  • Operation list, status, wait, and watch
  • Tenant-scoped ICP, company, person, list, campaign, artifact, messaging-policy, provider, conversation, and meeting projections with exact name resolution
  • Campaign-scoped artifact discovery
  • Immediate durable handoff with --no-wait

Enforced surface contract

Capability familyKindUIAPIMCPCLIAgentsWorkers
workspace.readreadRequiredRequiredRequiredRequiredRequiredNot applicable
strategy.icpmixedRequiredRequiredRequiredRequiredRequiredRequired
records.managemixedRequiredRequiredRequiredRequiredRequiredRequired
campaign.operatemixedRequiredRequiredRequiredRequiredRequiredRequired
communications.managemixedRequiredRequiredRequiredRequiredRequiredRequired
providers.operatemixedRequiredRequiredRequiredRequiredRequiredRequired
agents.administermixedRequiredRequiredRequiredRequiredRequiredRequired
operations.observereadRequiredRequiredRequiredRequiredRequiredNot applicable

Workers are the durable execution surface for mutations, not another interactive transport. Read-only capabilities therefore require UI, API, MCP, CLI, and agent evidence; mutation and mixed capabilities also require worker evidence.

Deliberate exceptions

CapabilityMissing surfacesCommandsClassificationOwnerExpiresTrackingWhy it is not exposed
Provider-backed company and person searchapi, mcp, cli, agentscompanies search, people searchapi-gapGTM Brain record projections2026-12-15Issuethe external catalog does not yet expose a privacy-safe provider search resource
Governed list membership readsapi, mcp, cli, agentslists membersapi-gapGTM Brain record projections2026-12-15Issuethe external catalog does not yet have a lifecycle- and suppression-aware membership projection
Provider credential entryapi, mcp, cli, agents, workersproviders connectui-onlyGTM Brain integrations2026-12-15Issuerequires a secure interactive exchange; secrets are forbidden in CLI arguments and durable inputs
Authentication, billing, organization membership, and external-agent registration administrationmcp, cli, agents, workersagents list, agents show, agents connect, agents scope, agents pause, agents resume, agents removeui-onlyGTM Brain application shell2026-12-15Issuecontrol-plane administration is outside a campaign-scoped external registration
Rich artifact editingcliui-onlyGTM Brain artifacts2026-12-15Issuethe CLI supports versioned JSON artifact mutations but not browser-native rich editing
Provider-native Instantly campaign projectionsapi, mcp, cli, agentsinstantly campaigns, instantly show, instantly check, instantly syncapi-gapGTM Brain projections2026-12-15Issueprovider-native campaign state does not yet have a durable tenant projection
Company deletion, campaign clone, list deletion, provider disconnect, and Instantly bind/pauseapi, mcp, cli, agents, workerscompanies delete, lists delete, campaigns clone, providers disconnect, instantly bind, instantly pauseaction-contract-gapGTM Brain integrations2026-12-15Issueno certified external governed action contract currently exists
Workflow cancellationui, api, mcp, cli, agents, workersauthorization-gapGTM Brain runtime2026-12-15Issuecancellation must first bind the originating registration to the exact workflow and record a governed outcome
Operation-ID-only retryapi, mcp, cli, agents, workersrecovery-contract-gapGTM Brain runtime2026-12-15Issuethe operation projection cannot reconstruct original mutation parameters; unknown submissions retry only with the same idempotency key and input
Single approval detail, inbox classify/send aliases, and meeting schedule/update/cancelapi, mcp, cli, agents, workersapprovals show, inbox classify, inbox send, meetings schedule, meetings update, meetings cancelapi-gapGTM Brain operational projections2026-12-15Issueno matching privacy-safe read or certified external governed action currently exists

Machine contract

  • Parity manifest schema: 2
  • CLI contract: 3
  • Projection contract: 1
  • Runtime authority: live-external-action-catalog
  • Manifest last certified against the CLI registry and external catalog: 2026-09-01
  • Maximum exception lifetime: 120 days
  • Release rule: Every capability must carry evidence for every required surface or a reviewed, tracked, unexpired exception.

Use gtm commands --json to discover the installed CLI surface, gtm capabilities --json to compare it with the current registration, and gtm catalog --json to inspect the authority granted right now. An unavailable command includes its classification and reason; agents must not substitute a different action or bypass the gateway.

Campaign operating sequence

For a new campaign, use this order and stop whenever the catalog, readiness result, or approval state requires a person:

  1. Read the live catalog and workspace context.
  2. Inspect existing ICPs; create a versioned ICP only when the campaign needs a different audience.
  3. Import or update the companies and people supported by the granted record actions. Provider search remains unavailable until it appears in the live catalog.
  4. Save and activate the campaign's messaging policy, then save the campaign definition with its exact ICP and policy references.
  5. Create the brief, audience, sequence, proof, and copy artifacts returned by the catalog. Persist useful work instead of leaving it only in chat.
  6. Run campaign readiness and a dry run. Resolve missing evidence without changing unrelated campaigns.
  7. Request the governed launch. Prospect-visible delivery and Instantly activation wait for the exact authorization and human approval returned by GTM Brain.
  8. Follow the durable operation to a terminal result and report campaign names first, with IDs only in receipts or when names are ambiguous.

An ICP is versioned campaign context, not a tenant-wide replacement switch. Creating or activating one does not delete, retire, or rebind existing campaigns. A connected agent may act on only the campaigns and actions in its current grant, whether that grant names one campaign or several.

On this page