Outcome
List all tasks for the authorized workspace, ordered by due time and then creation time. Persisted rows include nullable notification and completion timestamps; the request can create the identity mirror.
Before you start
- Verify the authenticated identity, exact environment and pinned approved organization context before preparing an action.
- The published application permission is workspace:read. Discover a granted Success workspace and bind that exact resource. Supplied identifiers do not grant access.
- Authorize the documented mirror, notification, metering, privacy or archival effects before CLI --confirm or MCP confirm:true. A GET request can initialize a local mirror.
Discover the target
topolo whoami --json
topolo actions get app_topolo_success.playbook_tasks.list --detail --json
topolo resources topolo-success --json
topolo workspaces list topolo-success --json
- Select the exact granted workspace id as SUCCESS_WORKSPACE_ID. Fixture ids authorize no live operation.
Request
GET /api/playbook-tasks
Save action input as payload.json. Inspect the plan for the exact path, query and body. Set SUCCESS_WORKSPACE_ID from granted resource discovery.
Inspect and test this action in the signed action console, then perform the verification below.
Input fields
Supply an empty input object; credential and resource context are separate.
Exact input schema:
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {},
"additionalProperties": false
}
Effects
- After static permission and platform workspace authorization, the route inserts the local identity-only workspace mirror if absent; even GET listing is a potential write.
- Returns all workspace tasks without pagination, ordered due_at ascending then created_at ascending; includes due_notification_queued_at and completed_at.
Interpret the response
Use response path $.tasks[].id for success_playbook_task. An empty list does not discover a target.
Use tasks[].id, account_id, due_at and status from the response. No task-complete or task-delete action is currently published.
The success schema below was checked against captured handler responses. Delegated Auth profile fields and sanitized notification payload fields can vary; exact outer envelopes and SQL row fields are source-reviewed. Error examples retain their actual refusal shapes.
Success schema:
{
"type": "object",
"properties": {
"tasks": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Source-defined string field."
},
"organization_id": {
"type": "string",
"description": "Source-defined string field."
},
"workspace_id": {
"type": "string",
"description": "Source-defined string field."
},
"created_at": {
"type": "string",
"description": "Source-defined string field."
},
"updated_at": {
"type": "string",
"description": "Source-defined string field."
},
"account_id": {
"type": "string",
"description": "Source-defined string field."
},
"title": {
"type": "string",
"description": "Source-defined string field."
},
"recipient_user_id": {
"type": "string",
"description": "Source-defined string field."
},
"due_at": {
"type": "string",
"description": "Source-defined string field."
},
"status": {
"type": "string",
"enum": [
"pending",
"completed"
]
},
"due_notification_queued_at": {
"anyOf": [
{
"type": "string",
"description": "Source-defined string field."
},
{
"type": "null"
}
]
},
"completed_at": {
"anyOf": [
{
"type": "string",
"description": "Source-defined string field."
},
{
"type": "null"
}
]
}
},
"required": [
"id",
"organization_id",
"workspace_id",
"created_at",
"updated_at",
"account_id",
"title",
"recipient_user_id",
"due_at",
"status",
"due_notification_queued_at",
"completed_at"
],
"additionalProperties": false
}
}
},
"required": [
"tasks"
],
"additionalProperties": false
}
Worked examples
Actual exported Worker responses captured with real local SQLite D1 and all committed migrations, synthetic Auth identity/grants, simulated Notify/Nexus and canonical archive transport. Fixture ids are examples only. No live notification delivery, metering acceptance, privacy erasure, workspace archive or deployment is established by these tests. Refused examples demonstrate boundaries and must not be executed as successful workflows.
Successful request
Actual exported Worker response with real local SQLite D1, synthetic Auth/grants and simulated Notify/Nexus/archive transport; no live delivery or deployment proof. Captured scenario: persisted task list includes nullable schedule fields.
Input · payload.json:
{}
CLI:
topolo actions validate app_topolo_success.playbook_tasks.list --data @payload.json --json
topolo actions plan app_topolo_success.playbook_tasks.list --resource-type workspace --resource-id "$SUCCESS_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_success.playbook_tasks.list --resource-type workspace --resource-id "$SUCCESS_WORKSPACE_ID" --data @payload.json --confirm --json
MCP tool and arguments:
{
"tool": "topolo_call_action",
"arguments": {
"actionId": "app_topolo_success.playbook_tasks.list",
"input": {},
"resourceType": "workspace",
"resourceId": "<identifier returned by granted resource discovery>",
"confirm": true
}
}
Captured local response · HTTP 200:
{
"tasks": [
{
"id": "successtask_ec822197-6dc7-4890-82af-353d4e2b238d",
"account_id": "successacct_7054c378-7a67-4c4f-aad1-fa6464e35cd5",
"organization_id": "org_success_fixture",
"workspace_id": "ws_success_fixture",
"title": "Review adoption",
"recipient_user_id": "usr_success_fixture",
"due_at": "2027-03-01T12:00:00Z",
"status": "pending",
"due_notification_queued_at": null,
"completed_at": null,
"created_at": "2026-10-04T05:10:03.891Z",
"updated_at": "2026-10-04T05:10:03.891Z"
}
]
}
HTTP 200. Use tasks[].id, account_id, due_at and status from the response. No task-complete or task-delete action is currently published.
Another supported request
Actual exported Worker response with real local SQLite D1, synthetic Auth/grants and simulated Notify/Nexus/archive transport; no live delivery or deployment proof. Captured scenario: empty task list.
Input · payload.json:
{}
CLI:
topolo actions validate app_topolo_success.playbook_tasks.list --data @payload.json --json
topolo actions plan app_topolo_success.playbook_tasks.list --resource-type workspace --resource-id "$SUCCESS_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_success.playbook_tasks.list --resource-type workspace --resource-id "$SUCCESS_WORKSPACE_ID" --data @payload.json --confirm --json
MCP tool and arguments:
{
"tool": "topolo_call_action",
"arguments": {
"actionId": "app_topolo_success.playbook_tasks.list",
"input": {},
"resourceType": "workspace",
"resourceId": "<identifier returned by granted resource discovery>",
"confirm": true
}
}
Captured local response · HTTP 200:
{
"tasks": []
}
HTTP 200. Use tasks[].id, account_id, due_at and status from the response. No task-complete or task-delete action is currently published.
Verify the result
- Use tasks[].id, account_id, due_at and status from the response. No task-complete or task-delete action is currently published.
Errors and recovery
invalid_action_input(HTTP 400): Correct only the input paths reported by the runtime or CLI validator; retain action id and exact context.action_permission_required(HTTP 403): The verified credential lacks the action permission. Stop this action and request the appropriate authorized grant; an identifier or organization ownership does not grant it.organization_required(HTTP 403): Verify the authorized organization context; personal scope cannot operate on organization-owned Success data.workspace_required(HTTP 400): Discover an authorized app-scoped workspace and pass its resource binding. API keys without a workspace resource are refused.workspaces_unavailable(HTTP 503): Preserve the request id and report unavailable platform grants or database binding; do not invent a default workspace.
Auth, action-input validation and platform resource resolution can refuse a request before its handler. Retain the exact error, request id and context; requesting another context is not a legitimate way to bypass a refusal.
Recovery boundary
No task changes occur; any newly initialized mirror has no standalone undo action.
Related actions
- Create Success playbook task: Create a pending task for an authorized account with a required ISO due time. Immediate creation does not complete the task or send its due reminder; scheduled processing handles due events later.
Evidence
Actual exported Worker responses captured with real local SQLite D1 and all committed migrations, synthetic Auth identity/grants, simulated Notify/Nexus and canonical archive transport. Fixture ids are examples only. No live notification delivery, metering acceptance, privacy erasure, workspace archive or deployment is established by these tests. Capture digests and test scenarios are retained in the source fixture records.