Gumloop home page
Search...
⌘K
Ask AI
Support
Hub
Hub
Search...
Navigation
Flow Basics
Output
Documentation
API Reference
Community
Tutorials
Get Started
Introduction
Core Concepts
Nodes
Flow Basics
Input
Output
Current Automation Info
Current Datetime
Filter
Router
Error Shield
Join Paths
Using AI
MCP
Web Scraping
Text Manipulation
Browser Extension
File Operations
Advanced
Data Enrichment
JSON
PDF
List Operations
Notifications
Audio Processing
Integrations
Custom Node Builder
Common Errors
Type Mismatch Errors
List Size Mismatch Errors
Join List Items vs Loop Mode
On this page
Node Inputs
Required Fields
Optional Fields
Node Output
Node Functionality
When To Use
Output Types Explained
Subflow Power Features
Flow Basics
Output
This document explains the Output node, which lets you name and pass data out of your workflows.
Node Inputs
Required Fields
Output
: The value or data you want to pass out of the workflow
Output Name
: A name to identify this output (default: “output”)
Optional Fields
Output Type
: Sets the expected data format
string
: For single values like text
string[]
: For lists of values (arrays) like URLs or email addresses
any
: For when you’re unsure or want to accept any type
Node Output
The Output node packages your data for use in:
Parent workflows
Webhook responses
Other subflows
External systems
Node Functionality
The Output node acts as an exit point for your workflow data. It:
Names your outputs for easy reference
Ensures data type consistency
Makes data available to parent workflows
Creates clean endpoints for webhook responses
Multiple outputs
can now be configured within a single output node
When To Use
Use the Output node to:
End Workflows
: Mark the final result of your workflow
Connect Subflows
: Pass data between nested workflows
Create Webhooks
: Return data to external systems
Output Types Explained
Use
string
when outputting:
Single pieces of text
Use
string[]
when outputting:
Lists of items
Multiple results
Arrays of data Example: A list of email addresses
Use
any
when:
You’re unsure of the data type
The output could vary
You’re still testing Example: Mixed data from an API
Subflow Power Features
Passing Data Up
:
Outputs from subflows become available in parent workflows
Name outputs clearly for easy reference
Example
:
Subflow outputs: “customer_name”, “customer_email”
Parent flow can use both these outputs when you drag the subflow from the ‘Subflow library’
Chaining Subflows
:
Pass outputs from one subflow to another
Create complex data processing pipelines. Example:
Copy
Ask AI
Subflow1 output -> Subflow2 input
Nested Processing
:
Use outputs in deeply nested workflows
Access data across multiple workflow levels
In summary, the Output node is your key to managing data flow between workflows, external systems, and nested automations.
Input
Current Automation Info
Assistant
Responses are generated using AI and may contain mistakes.