Workflow Output

Define what the customer receives when the workflow finishes.

Overview#

Workflow Output is the finish line. It takes the final result from upstream blocks and presents it in the run modal with the right view , text, markdown, image, HTML, or JSON.

Every shippable workflow should end with a clear output block so customers know exactly what they paid for.

Workflow Preview

Workflow Output

Read-only builder graph

Ports#

Input , Result: Connect the final value you want the customer to see. Usually sits at the end of the main flow or a branch.

Inspector#

Output Name: A customer-facing label for the result, such as "Generated Content" or "Processed Data."
Output Format: Auto (recommended) lets the run modal pick the best renderer. Force JSON, Text, or HTML only when you need a fixed presentation.

Tips#

Name the output after what the customer gets, not how it was made.
Prefer Auto unless you have a strong reason to lock the format.
Use JSON for structured data, Text for plain answers, HTML when formatting matters.
Do not expose internal debug structure unless the product is meant to show it.

Workflow Studio

More blocks

Workflow Input

Ask the customer one clear question and turn their answer into data your workflow can use.

Workflow Form

Collect several run-modal fields in one grouped form, each with a stable key for downstream steps.

Merge

Combine several upstream values into one payload for the next step.

Block reference

Workflow Output

Define what the customer receives when the workflow finishes.

Overview#

Workflow Output is the finish line. It takes the final result from upstream blocks and presents it in the run modal with the right view , text, markdown, image, HTML, or JSON.

Every shippable workflow should end with a clear output block so customers know exactly what they paid for.

Workflow Preview

Workflow Output

Read-only builder graph

Ports#

Input , Result: Connect the final value you want the customer to see. Usually sits at the end of the main flow or a branch.

Inspector#

Output Name: A customer-facing label for the result, such as "Generated Content" or "Processed Data."
Output Format: Auto (recommended) lets the run modal pick the best renderer. Force JSON, Text, or HTML only when you need a fixed presentation.

Tips#

Name the output after what the customer gets, not how it was made.
Prefer Auto unless you have a strong reason to lock the format.
Use JSON for structured data, Text for plain answers, HTML when formatting matters.
Do not expose internal debug structure unless the product is meant to show it.