Get broadcast progress

Read delivery progress: the broadcast status, total recipients, counts per recipient status, processed (sent_intended + skipped + failed), progress 0-1, and how many recipients were skipped for each reason.

Outcome

Before you start

Verify identity and pin the intended organization and environment before discovering the action.
Discover a granted Nurture workspace. The application permission is workspace:read; required workspace access is read. A permission alone does not supply a workspace grant.
Organization and workspace come from verified context. Select resourceType/resourceId separately from action input; body fields cannot grant a different organization or workspace. The first authorized product action can initialize an identity-only workspace mirror.

Discover the target

topolo whoami --json
topolo actions get app_topolo_nurture.broadcasts.stats --detail --json
topolo resources topolo-nurture --json
topolo workspaces list topolo-nurture --json
topolo actions get app_topolo_nurture.broadcasts.list --detail --json

id: broadcasts record id in the selected workspace.

Request

GET /api/broadcasts/{id}/stats

Save action input as payload.json. The reviewed plan separates path identifiers, query fields and HTTP body. Set NURTURE_WORKSPACE_ID from granted resource discovery; it is separate from action input.

Inspect and test this action in the signed action console. A test response still requires the verification below.

Input fields

Field	Required	Type	Constraints
`id`	Required	string	broadcasts record id in the selected workspace. {"minLength":1,"maxLength":64}

Exact input schema:

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 64
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false
}

Effects

Reads progress counters without changing state.

Interpret the response

The returned identifier path is $.broadcastId for broadcast. Empty lists do not discover a target.

Confirm processed + pending + sending + cancelled equals total.

Exact success schema:

{
  "type": "object",
  "required": [
    "broadcastId",
    "status",
    "total",
    "byStatus",
    "processed",
    "progress",
    "skippedReasons"
  ],
  "properties": {
    "broadcastId": {
      "type": "string"
    },
    "status": {
      "type": "string",
      "enum": [
        "draft",
        "pending_approval",
        "approved",
        "scheduled",
        "sending",
        "sent",
        "cancelled",
        "failed",
        "archived"
      ]
    },
    "launchedAt": {
      "type": [
        "string",
        "null"
      ]
    },
    "completedAt": {
      "type": [
        "string",
        "null"
      ]
    },
    "total": {
      "type": "integer"
    },
    "processed": {
      "type": "integer"
    },
    "progress": {
      "type": "number"
    },
    "byStatus": {
      "type": "object"
    },
    "skippedReasons": {
      "type": "object"
    }
  }
}

Worked examples

Actual dispatcher and migration-created SQLite or Worker handlers; identity/workspace and external service dependencies are simulated. Fixture identifiers and timestamps are synthetic. These responses establish no live authorization, paid generation, credential provisioning or message delivery. Replace synthetic identifiers using credential-scoped discovery. A local success is not evidence of a deployed effect, configured provider or delivered message.

Successful request

Actual dispatcher and migration-created SQLite; verified identity/workspace and external CRM, Engage, Notify, Consent, Nexus, Brand, Generator, Voice and delivery dependencies are simulated. No live authorization, paid generation or external delivery is established.

Input · payload.json:

{
  "id": "bc_1c98f7632c7149afaea7457b966df1a9"
}

CLI:

topolo actions validate app_topolo_nurture.broadcasts.stats --data @payload.json --json
topolo actions plan app_topolo_nurture.broadcasts.stats --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.broadcasts.stats --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json

MCP tool and arguments:

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_nurture.broadcasts.stats",
    "input": {
      "id": "bc_1c98f7632c7149afaea7457b966df1a9"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "broadcastId": "bc_1c98f7632c7149afaea7457b966df1a9",
  "status": "cancelled",
  "launchedAt": null,
  "completedAt": null,
  "total": 0,
  "byStatus": {
    "pending": 0,
    "sending": 0,
    "sent_intended": 0,
    "skipped": 0,
    "failed": 0,
    "cancelled": 0
  },
  "processed": 0,
  "skippedReasons": {},
  "progress": 0
}

HTTP 200. Confirm processed + pending + sending + cancelled equals total.

Another supported request

Input · payload.json:

{
  "id": "bc_9194b079231e4246b56ba9a260d4b399"
}

CLI:

topolo actions validate app_topolo_nurture.broadcasts.stats --data @payload.json --json
topolo actions plan app_topolo_nurture.broadcasts.stats --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.broadcasts.stats --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json

MCP tool and arguments:

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_nurture.broadcasts.stats",
    "input": {
      "id": "bc_9194b079231e4246b56ba9a260d4b399"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "broadcastId": "bc_9194b079231e4246b56ba9a260d4b399",
  "status": "sending",
  "launchedAt": "2026-10-01T09:00:00.000Z",
  "completedAt": null,
  "total": 39,
  "byStatus": {
    "pending": 21,
    "sending": 0,
    "sent_intended": 17,
    "skipped": 1,
    "failed": 0,
    "cancelled": 0
  },
  "processed": 18,
  "skippedReasons": {
    "not_subscribed": 1
  },
  "progress": 0.46153846153846156
}

HTTP 200. Confirm processed + pending + sending + cancelled equals total.

Refused request · not_found

Input · payload.json:

{
  "id": "bc_missing"
}

CLI:

topolo actions validate app_topolo_nurture.broadcasts.stats --data @payload.json --json
topolo actions plan app_topolo_nurture.broadcasts.stats --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json

Captured local response · HTTP 404:

{
  "error": {
    "code": "not_found",
    "message": "Broadcast was not found in this workspace."
  }
}

HTTP 404. Preserve the refusal details and do not claim success.

Verify the result

Confirm processed + pending + sending + cancelled equals total.

Errors and recovery

organization_required (HTTP 403): Select an organization available to the verified caller before choosing a Nurture workspace.
permission_denied (HTTP 403): Grant the credential the required Nurture workspace permission.
workspace_required (HTTP 409): Create a Nurture workspace, or pass the workspace resource context.
invalid_input (HTTP 422): Correct the fields named in error.details using inputSchema, then retry.
not_found (HTTP 404): List broadcasts to find a valid id in this workspace.

Auth or gateway failures may precede this handler. Preserve the exact response shape, error string/code, request id and credential context; no synthetic fixture establishes live credential access.

Recovery boundary

This action does not change service state.

List broadcast recipients: Page through a launched broadcast's audience snapshot by contact id: each recipient's zone, due time, status (pending, sending, sent_intended, skipped, failed, cancelled), attempts, reservation id and skip or failure reasons. Pass nextCursor as cursor for the next page.
Cancel broadcast: Cancel a broadcast that is awaiting approval, approved, scheduled or sending. Every recipient not yet processed is marked cancelled and never sent; recipients already processed keep their outcome (their consumed reservations still count toward caps). Cancelling is final.

Evidence

Actual dispatcher and migration-created SQLite or Worker handlers; identity/workspace and external service dependencies are simulated. Fixture identifiers and timestamps are synthetic. These responses establish no live authorization, paid generation, credential provisioning or message delivery. Test scenario and capture digests are retained with each fixture.

Get broadcast progress

Outcome

Before you start

Discover the target

Request

Input fields

Effects

Interpret the response

Worked examples

Successful request

Another supported request

Refused request · not_found

Verify the result

Errors and recovery

Recovery boundary

Related actions

Evidence