Subworkflows

Subworkflows in Lleverage allow you to use existing workflows within other workflows, creating modular, reusable components that enhance efficiency and organization. This powerful feature helps you avoid duplicating work and creates logical groupings of functionality.

Key Features

• Workflow reusability for common processes and tools

• Modular design that simplifies complex automations

• Organizational structure for grouping related functions

• Consistent execution of standardized processes

• Easy maintenance through centralized updates

How to Add Subworkflows

1. Open the Add Action menu using one of three methods:

   • Click the "Add Action" button in the top left corner

   • Click on a connection circle on an existing action card

   • Click and drag from one node to create a connection

2. Find Subworkflows in either:

   • The "Subworkflows" tab

   • The "Subworkflows" subcategory in other tabs

3. Select from available published workflows in your project

4. Click on your chosen Subworkflow to add it to your canvas

💡 You can only add Subworkflows that you have access to within your project.

Adding Subworkflow through the Add Modal

Understanding Subworkflow Cards

1. Subworkflow cards have a distinct appearance:

   • They display as a "stat card" shape, different from standard action cards

   • They include the workflow name and description

   • They show a branch icon by default (if no custom icon was specified)

2. The card header contains:

   • Variable output in the top left corner

   • The same action controls as other action cards

   • Connection points on left and right sides

3. The card body shows:

   • A description (generated automatically if none was specified in the original workflow)

   • Configuration fields that match the trigger inputs of the referenced workflow

⚠️ When selecting a Subworkflow card, you only select the top card portion, not the entire visual representation.

Subworkflow Card

How to Configure Subworkflows

1. When you add a Subworkflow, the configuration area will match the trigger inputs of the original workflow

2. Fill in these fields just as you would for a standard trigger

3. You can rename the Subworkflow node in your canvas if desired

4. Connect the Subworkflow to other actions using the standard connection points

💡 The configuration options for a Subworkflow are determined by what inputs were defined in the original workflow's trigger.

How to Edit Subworkflows

1. To edit a Subworkflow from your main workflow:

   • Select the Subworkflow card on your canvas

   • Click the three-dot menu in the top right corner

   • Select "Edit" (pencil icon) from the options menu

2. This will navigate you to that workflow for editing:

   • The breadcrumbs at the top will show your location

   • You can make changes to the Subworkflow if you have access

   • To return to your main workflow, use the breadcrumbs navigation

3. Important publishing considerations:

   • Any changes you make to a Subworkflow must be published for them to take effect in your main workflow

   • Unpublished changes will be saved as drafts but won't affect the current published version

   • The publishing process follows the same workflow as other Lleverage components

⚠️ Remember that changes to a Subworkflow may affect all workflows that use it, not just your current main workflow.

Subworkflow Breadcrumbs

How Subworkflows Execute

1. When your main workflow runs and reaches a Subworkflow:

   • The main workflow pauses execution

   • The Subworkflow runs with the inputs you've provided

   • Once the Subworkflow completes, the main workflow resumes

   • The Subworkflow's output becomes available to subsequent actions

2. This execution pattern creates a nested structure:

   • Main workflow → Subworkflow → Main workflow continues

⚠️ If a Subworkflow encounters an error, it may affect the execution of the main workflow depending on your error handling configuration.

Important Subworkflow Considerations

1. Access Controls:

   • You can only add Subworkflows that you have access to in your project

   • You can see Subworkflows added by others in shared workflows, but cannot add them yourself unless you have access

   • You can only edit Subworkflows if you have edit access to them

2. Workflow States:

   • Only published workflows can be used as Subworkflows

   • Changes to the original workflow will affect all instances where it's used as a Subworkflow

   • Draft changes don't affect the published version used by other workflows

3. Design Principles:

   • Create Subworkflows for processes that are used repeatedly

   • Design Subworkflows to be modular and focused on specific tasks

   • Ensure Subworkflows have clear input requirements and outputs

4. Visual Representation:

   • The distinct card shape makes it easy to identify Subworkflows in your canvas

   • The branch icon is the default, but can be customized in the original workflow

💡 Think of Subworkflows as functions or methods in programming - reusable components that perform specific tasks and can be called from multiple places.

Benefits of Using Subworkflows

1. Reduced Duplication: Build a process once and use it in multiple workflows

2. Easier Maintenance: Update one Subworkflow to affect all instances where it's used

3. Better Organization: Group related actions into logical units

4. Simplified Complexity: Break down complex workflows into manageable components

5. Standardization: Ensure consistent execution of critical processes

💡 Using Subworkflows effectively can significantly reduce the time needed to build complex automations while improving their reliability and maintainability.