Output
Last updated
Last updated
The Output action in Lleverage defines what information is returned from your workflow and signals when the workflow should end. Every workflow requires at least one Output action to function correctly, making it a crucial component of your automation design.
Workflow completion indicator that signals when processing should stop
Return value definition for specifying what data the workflow produces
Support for multiple outputs in multi-step workflows
Variable integration for dynamic output content
Simple configuration through a straightforward text box interface
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
Find the Output action in either:
The "All" tab
The "Tools" tab
The "Controls" subcategory
Look for a blue icon with a left-pointing arrow
Click on the Output action to add it to your canvas
⚠️ Every workflow must have at least one Output action to function properly.
When you select the Output action, you'll see a simple text box
This text box allows you to specify what will be returned when the workflow ends
To include workflow variables:
Click in the text box to see the @ symbol at the bottom
Click the @ symbol to see available variables
Select the variable you want to include in the output
💡 You can combine text and variables in the Output action to create formatted responses.
Each Output action has a plus (+) button on the right side of the action card
Clicking this button allows you to add additional output fields
Multiple outputs are useful for multi-step workflows where different paths may produce different results
⚠️ In standard workflows, the Output action should typically be the final node without any connections leading out from it.
Workflow Branching:
You cannot have one action connected to two different Output actions directly
Each distinct pathway in your workflow should have its own Output action
A valid structure would be: Trigger → Actions → Output, and separate Actions → Output
Proper Workflow Structure:
For branching logic, use a Branch action first, then connect each branch to its own series of actions and an Output
A workflow with branches would follow this pattern:
Trigger → Actions → Branch → Actions → Output
And the other branch: Branch → Different Actions → Output
⚠️ Attempting to connect one action card to multiple Output actions directly will not work, as this violates the workflow structure rules.
Place the Output action at the end of your workflow
Configure what information should be returned when the workflow reaches this point
When the workflow execution reaches an Output action, it will:
Return the specified information
Stop processing that branch of the workflow
Consider that pathway complete
💡 Think of Output actions as the "exit points" of your workflow that determine what information is provided back to the user or system that triggered it.
Trigger → Action → Action → Output
The workflow processes linearly and returns one result
Trigger → Actions → Branch (based on condition)
If condition is true: Branch → Actions → Output A
If condition is false: Branch → Different Actions → Output B
The workflow returns different results depending on which path was taken
💡 Using multiple outputs allows your workflow to provide different responses based on conditions, inputs, or processing results.
