output-workflow-result

Included with Lifetime

$97 forever

Get the result of an Output SDK workflow execution. Use when retrieving the output of a completed workflow, getting the return value, or checking what a workflow produced after async execution.

Backend & APIs

What this skill does


# Get Workflow Execution Result

## Overview

This skill retrieves the result (return value) of a completed workflow execution. Use it after a workflow started with `npx output workflow start` has completed, or to retrieve results from historical runs.

## When to Use This Skill

- Getting output from an asynchronously started workflow
- Retrieving results from a completed workflow
- Checking what a workflow produced
- Processing workflow output in scripts
- Comparing results between runs

## Prerequisites

- The workflow must have completed (status: COMPLETED)
- You need the workflow ID
- For FAILED workflows, use `npx output workflow debug` instead

## Instructions

### Get Result

```bash
npx output workflow result <workflowId>
```

The result is the return value of the workflow function, typically JSON.

### Check Status First

Before getting results, verify the workflow completed:

```bash
npx output workflow status <workflowId>
# Should show: COMPLETED

npx output workflow result <workflowId>
```

## Understanding Results

### Success Results

A successful workflow returns the value from its `fn` function:

```typescript
// Workflow code
export default workflow( {
  fn: async input => {
    return { processed: true, count: 42 };
  }
} );
```

```bash
# Result output
npx output workflow result abc123
# { "processed": true, "count": 42 }
```

### Error Results

If you try to get the result of a failed workflow:
- You'll get an error message
- Use `npx output workflow debug` instead to see what went wrong

### No Result (void workflows)

Some workflows don't return a value:
```bash
npx output workflow result abc123
# null
```

## Examples

**Scenario**: Get result after async start

```bash
# Start workflow
npx output workflow start calculate '{"values": [1, 2, 3]}'
# Output: Workflow ID: calc-abc123

# Wait for completion
npx output workflow status calc-abc123
# Status: COMPLETED

# Get the result
npx output workflow result calc-abc123
# { "sum": 6, "average": 2 }
```

**Scenario**: Process result with jq

```bash
# Extract specific field
npx output workflow result abc123 | jq '.total'

# Format for display
npx output workflow result abc123 | jq '.'

# Save to file
npx output workflow result abc123 > result.json
```

**Scenario**: Compare results between runs

```bash
# Get results from two runs
npx output workflow result run-1-abc > result1.json
npx output workflow result run-2-xyz > result2.json

# Compare
diff result1.json result2.json
```

**Scenario**: Use in a script

```bash
WORKFLOW_ID="abc123"

# Wait for completion
while [[ $(npx output workflow status $WORKFLOW_ID) == *"RUNNING"* ]]; do
  sleep 5
done

# Check if completed successfully
if [[ $(npx output workflow status $WORKFLOW_ID) == *"COMPLETED"* ]]; then
  RESULT=$(npx output workflow result $WORKFLOW_ID)
  echo "Workflow result: $RESULT"
else
  echo "Workflow did not complete successfully"
  npx output workflow debug $WORKFLOW_ID
fi
```

## Handling Different Result Types

### JSON Objects
```bash
npx output workflow result abc123
# { "key": "value", "nested": { "data": true } }
```

### Arrays
```bash
npx output workflow result abc123
# [1, 2, 3, 4, 5]
```

### Primitive Values
```bash
npx output workflow result abc123
# 42

npx output workflow result abc123
# "success"

npx output workflow result abc123
# true
```

### Large Results

For large results, redirect to a file:
```bash
npx output workflow result abc123 > large-result.json
```

## Error Handling

### "Workflow not found"
- Check the workflow ID is correct
- Use `npx output workflow runs list` to find valid IDs

### "Workflow not completed"
- Check status: `npx output workflow status <id>`
- Wait for COMPLETED status before getting result
- If RUNNING, wait and try again
- If FAILED, use `npx output workflow debug`

### "No result available"
- The workflow may return void/undefined
- Check the workflow code to see what it returns

## Related Commands

- `npx output workflow status <id>` - Check if workflow completed
- `npx output workflow debug <id>` - Debug failed workflows
- `npx output workflow run <name>` - Run and get result in one step
- `npx output workflow runs list` - Find workflow IDs

Files: 1

Size: 4.4 KB

Complexity: 13/100

Category: Backend & APIs

Source: https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-workflow-result

Related in Backend & APIs

jfrog

Included

Interact with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.

Backend & APIsscripts

cupynumeric-migration-readiness

Included

Pre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.

Backend & APIsscripts

alibabacloud-data-agent-skill

Included

Invoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".

Backend & APIsscripts

token-optimizer

Included

Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.

Backend & APIsscripts

resend-cli

Included

Use this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.

Backend & APIsscripts

alibabacloud-odps-maxframe-coding

Included

Use this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.

Backend & APIsscripts