Output

​

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

• Parent workflows
• Webhook responses
• Other subflows
• External systems

​

Node Functionality

• 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

• 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

1. Use string when outputting:
   • Single pieces of text
2. Use string[] when outputting:
   • Lists of items
   • Multiple results
   • Arrays of data Example: A list of email addresses
3. 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

1. 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’
2. Chaining Subflows:
   • Pass outputs from one subflow to another
   • Create complex data processing pipelines. Example:
   Copy

   Ask AI

   Subflow1 output -> Subflow2 input
   

3. Nested Processing:
   • Use outputs in deeply nested workflows
   • Access data across multiple workflow levels