Get Flow workspace context

Resolve authenticated identity, organization and the granted active Flow workspace.

Outcome

Resolve authenticated identity, organization and the granted active Flow workspace.

Before you start

Verify authenticated identity, environment and the approved organization context before preparing an action.
The published application permission is workspace:read. Discover and bind the exact granted Flow workspace. Supplied ids do not grant access.
Session callers need read workspace access. Auth-introspected API keys must bind that workspace and satisfy workspace:read. The application permission and workspace boundary are separate checks.

Discover the target

topolo whoami --json
topolo actions get app_topolo_flow.workspace.bootstrap --detail --json
topolo resources topolo-flow --json
topolo workspaces list topolo-flow --json

Set FLOW_WORKSPACE_ID to the exact id returned by granted workspace discovery.

Request

GET /api/bootstrap

Inspect and test this action. Save the exact input object as payload.json; resource context is supplied separately.

Input fields

Use an empty input object. Identity and resource context are separate from action input.

View the full input schema through the action reference or CLI/MCP discovery.

Effects

Reads canonical Auth workspace grants; does not create a Flow workspace mirror or flow.

Interpret the response

Read $.workspaceId for the returned workspace identifier. An empty collection does not discover a target.

Compare workspaceId and organization.id to the exact credential and granted workspace.

View the complete success schema. Success examples below preserve the actual exported Worker responses; errors have their original refusal shapes. CLI/MCP add their transport envelope, and --detail requests the full CLI response.

Worked examples

Captured from the actual exported Flow Worker with both local SQLite D1 stores and all committed migrations, synthetic Auth identity/grants and simulated Nexus, archive and Workflow-acceptance transports. Fixture credentials and identifiers authorize no live operation. No live provider invocation, credential storage, notification delivery, metering acceptance, durable Workflow execution, deployment, backup erasure or production completion is established by these captures. Refused examples explain boundaries and must not be executed as successful workflows.

Successful request

Actual exported Worker response with both local SQLite D1 databases and all committed migrations; synthetic Auth/grants and simulated Nexus/archive transport. No live credentials, provider calls, delivery, deployment or durable Workflow execution proof. Scenario: workspace.bootstrap.

Input · payload.json:

{}

CLI:

topolo actions validate app_topolo_flow.workspace.bootstrap --data @payload.json --json
topolo actions plan app_topolo_flow.workspace.bootstrap --resource-type workspace --resource-id "$FLOW_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_flow.workspace.bootstrap --resource-type workspace --resource-id "$FLOW_WORKSPACE_ID" --data @payload.json --detail --json

MCP tool and arguments:

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_flow.workspace.bootstrap",
    "input": {},
    "resourceType": "workspace",
    "resourceId": "<id returned by granted resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "user": {
    "id": "usr_flow_fixture",
    "email": "operator@example.test",
    "orgId": "org_flow_fixture",
    "role": "member",
    "permissions": [
      "*"
    ],
    "organization": {
      "id": "org_flow_fixture",
      "slug": "flow-fixture",
      "name": "Synthetic fixture"
    },
    "orgSlug": "flow-fixture",
    "activeContextType": "organization",
    "activeContextId": "org_flow_fixture"
  },
  "organization": {
    "id": "org_flow_fixture",
    "slug": "flow-fixture",
    "name": "Synthetic fixture"
  },
  "workspaceId": "ws_flow_fixture"
}

HTTP 200. Compare workspaceId and organization.id to the exact credential and granted workspace.

Refused request · HTTP 401

Input · payload.json:

{}

CLI:

topolo actions validate app_topolo_flow.workspace.bootstrap --data @payload.json --json
topolo actions plan app_topolo_flow.workspace.bootstrap --resource-type workspace --resource-id "$FLOW_WORKSPACE_ID" --data @payload.json --json

Captured local response · HTTP 401:

{
  "error": "Authentication token required"
}

HTTP 401. The handler refused this request. Resolve the exact cause before retrying; invalid input can be refused by CLI validation before reaching the handler.

Verify the result

Compare workspaceId and organization.id to the exact credential and granted workspace.

Errors and recovery

Authentication token required (HTTP 401): Authenticate normally in the approved environment and organization, verify identity, then rediscover the action and its granted resource before retrying.
organization_required (HTTP 403): Authenticate into the specifically approved organization. Do not guess a different organization or bypass the refusal.
action_permission_required (HTTP 403): The credential lacks the exact published application permission. Stop and obtain authorized access; changing target ids cannot grant it.
workspace_required (HTTP 400): Discover an explicitly granted Flow workspace and bind its exact resource id.

Preserve the exact status, response, request id and resource context. Runtime input validation, authentication and platform resource resolution can refuse a request before the handler. Dynamic dependency messages are not stable provider error codes.

Recovery boundary

Refresh authentication or select an explicitly granted workspace; do not manufacture a workspace id.

List flows: Read the workspace automation graphs, statuses and retained run counters.
Browse callable actions: Read the caller-scoped cross-application catalog used by the Flow node palette.

Evidence

Captured from the actual exported Flow Worker with both local SQLite D1 stores and all committed migrations, synthetic Auth identity/grants and simulated Nexus, archive and Workflow-acceptance transports. Fixture credentials and identifiers authorize no live operation. No live provider invocation, credential storage, notification delivery, metering acceptance, durable Workflow execution, deployment, backup erasure or production completion is established by these captures. Original scenario labels and response digests are retained in the source fixtures.