Get task output by ID
Retrieve a specific task output by its unique identifier.
Fetch a single task output record with complete output data, summary, tags, and metadata. Used for inspecting individual task results, debugging, and retrieving output for downstream processing.
Resource Identification
Task outputs are uniquely identified by UUID (id field). To find task outputs by
other criteria (flow execution, task name), use GET /flow-executions/{id} or
GET /task-outputs (list all).
What You'll Get
- summary: Structured task output summary for display
- output: Full output data produced by task
- tags: Associated metadata tags
- status: Task execution state when output was created
- Timestamps: created_at, updated_at for audit trail
- Organization context: organization_id for multi-tenant isolation
Common Use Cases
- Inspect task output for debugging or validation
- Retrieve output data for manual review or corrections
- Audit task execution history
- Display detailed task results in UI
Related Endpoints
GET /task-outputs- List all task outputsGET /flow-executions/{id}- View parent flow execution with all outputsGET /task-executions/{id}- View full task execution details
Header Parameters
Path Parameters
Unique identifier of the task output to retrieve. UUID assigned when task output was created. Task outputs are scoped to organization; attempting to access another organization's output returns 404.
Response
Response Attributes
ID of the parent flow execution containing this task. Establishes the execution hierarchy and organization scope.
Unique identifier for this task output. Auto-generated UUID assigned at creation time. Used for direct resource access via GET /task-outputs/{id}.
Identifier of the actor who last modified this task output. Tracks who made the last change for auditing purposes. Defaults to 'system' for worker-initiated changes.
Values:
- 'system': System-automated changes (workers, background jobs)
- User ID: UUID string of the user who made the change (e.g., '123e4567-e89b-12d3-a456-426614174000')
- Integration type: For service accounts/integrations (e.g., 'integration', 'service-account')
ID of the organization owning this task output. Inherited from parent flow execution. Used for Row-Level Security (RLS) and multi-tenant isolation.
Execution status when output was created. Valid values: 'queued', 'running', 'completed', 'failed', 'deleted', 'stale'. Typically 'completed' for successful task outputs.
Status meanings:
- queued: Task scheduled but not started
- running: Task actively executing
- completed: Task finished successfully
- failed: Task encountered error (may have partial output)
- deleted: Soft-deleted, excluded from queries (preserves audit trail)
- stale: Output data is outdated (needs refresh)
Structured summary of task output for UI display and querying. Typically a dictionary with standardized keys for rendering.
Common patterns:
- Document processing: {'pages': 10, 'word_count': 5000}
- API calls: {'status_code': 200, 'response_time_ms': 450}
- Data validation: {'valid_rows': 950, 'invalid_rows': 50}
Name of the task that produced this output. Case-sensitive identifier matching flow definition YAML. Used to associate output with specific workflow task.
Response Attributes
Standard error detail structure.
This model matches the error format returned by the centralized exception handlers in app/api/errors/handlers.py.
Show child attributes
Response Attributes
Standard error detail structure.
This model matches the error format returned by the centralized exception handlers in app/api/errors/handlers.py.
Show child attributes
Response Attributes
Standard error detail structure.
This model matches the error format returned by the centralized exception handlers in app/api/errors/handlers.py.
Show child attributes
Response Attributes
Standard error detail structure.
This model matches the error format returned by the centralized exception handlers in app/api/errors/handlers.py.