Documentation is being updated. Some sections may not reflect the latest features.
Looking for step-by-step guides? Explore Tutorials →

Sub-workflow Node

Call other workflows from within your workflow.

Overview

The Sub-workflow node allows you to organize complex logic into reusable workflows. Call any workflow and pass data between them using input mappings.

Configuration

Field Description Required
Workflow Select the workflow to call Yes
Input Mappings Map variables to the sub-workflow's input parameters No
Output Variable Variable name to store the sub-workflow's output No

Input Mappings

Pass data to the sub-workflow by mapping your variables to its expected inputs. Each mapping consists of:

Field Description
Parameter Name The input parameter expected by the sub-workflow
Value Variable or expression to pass (e.g., {{user_id}})

Example Mappings

Parameter: user_id → {{current_user.id}}
Parameter: query → {{search_term}}
Parameter: options → {{config.settings}}

How It Works

  1. Select a workflow from your workspace
  2. Define input mappings to pass data
  3. The sub-workflow executes with the provided inputs
  4. Results are stored in your output variable

Accessing Nested Properties

You can pass nested object properties:

{{user.profile.name}}
{{response.data.items}}
{{config.api.endpoint}}

Use Cases

  • Reusable Logic - Create common operations once, use everywhere
  • Modular Design - Break complex workflows into manageable pieces
  • Team Collaboration - Share workflows across team members
  • Version Control - Update sub-workflows without modifying parent workflows

Best Practices

  • Use descriptive workflow names
  • Document expected input parameters
  • Keep sub-workflows focused on single responsibilities
  • Test sub-workflows independently before integrating
AI AssistantPowered by Ubex
Beta
Ask me anything about Ubex workflows, nodes, or the API.