ORCFLO Documentation

Overview

The Output component is the endpoint of your workflow, defining what results are returned and how they're formatted. It collects data from previous steps and presents it in a structured, usable format.

Whether you need to display results to users, send them to external services, or store them for later use, the Output component provides the flexibility to format your workflow results exactly as needed.

Output Formats

Choose the format that best matches your downstream requirements.

Format	Description	Best For
Plain Text	Simple text output for human-readable results	Generated content, summaries
JSON	Structured data with nested objects and arrays	API integrations, programmatic use
CSV	Tabular data format	Spreadsheets, data analysis
Markdown	Formatted text with headers, lists, styling	Documentation, content publishing

Configuration

Configure your Output component with these settings.

Output Name

A descriptive name for this output. This appears in the execution results and helps identify what the output represents.

Format

Select the output format based on how the results will be used downstream.

Display

The output node automatically displays the results from connected upstream nodes. Results are formatted according to the selected output format.

Collecting Results

The Output node automatically collects results from connected upstream nodes. Data flows through your workflow and is displayed when it reaches the Output.

What Gets Displayed

AI Model outputs	Full response text from AI nodes
Decision results	Which path was taken
Tool outputs	Results from tool executions
Aggregated data	Combined results from multiple steps

Multiple Outputs

A workflow can have multiple Output components to capture results from different branches or stages of your workflow.

Formatting Options

The Output component automatically formats results based on the selected format type. Data from upstream nodes is structured according to your chosen format.

JSON Output

Results are automatically structured as JSON with relevant fields from the workflow.

json

{
  "title": "Generated Blog Post Title",
  "summary": "A concise summary of the content...",
  "keywords": ["ai", "automation", "workflow"],
  "metadata": {
    "created_at": "2026-01-04T10:30:00Z",
    "source": "content-generation-workflow"
  }
}

CSV Output

Tabular data is formatted with headers and rows for easy export.

text

Name,Category,Score,Notes
Product Analysis,Research,95,Comprehensive review completed
Market Report,Analytics,88,Includes competitor analysis

Use Cases

Common output configurations for different workflows.

Generated content: articles, reports, summaries
API responses: structured JSON for integrations
Data exports: CSV files for analysis tools
Email content: formatted messages for automation
Documentation: markdown for publishing
Audit logs: structured records of processing
Notifications: formatted alerts and updates
Reports: combined results with metadata

Best Practices

Match format to destination: Use JSON for APIs, CSV for spreadsheets, Markdown for documentation.
Include metadata when useful: Add timestamps, source info, and execution IDs for traceability.
Validate output structure: For JSON outputs, ensure the structure matches what consumers expect.
Handle missing data gracefully: Consider what happens if a referenced step produces empty output.

Output Usage

Output results are displayed in the execution panel and can be downloaded in your chosen format for further use.

Key Takeaways

Output components define the final results of your workflow
Choose the format (JSON, CSV, text, markdown) based on how results will be used
Data flows automatically from connected upstream nodes to the Output
Multiple outputs can generate different formats from the same execution
Include relevant metadata for traceability and debugging

Output Component