Action Cards
Action Cards are the fundamental building blocks of workflows in Lleverage. Each card represents a step in your automation process and contains configuration options specific to that action type. Understanding how to work with Action Cards is essential for creating effective workflows.
Key Features
Consistent header structure across different action types
Variable outputs displayed in the top left corner
Interactive controls for testing and configuration
Natural language descriptions that update automatically
Connection points for linking actions together
Action Card Anatomy
Every Action Card includes these standard elements:
Header section
Variable name in the top left (representing the action's output)
Expand/collapse chevron in the top right
Run button (play icon) to test the specific action
Three-dot menu for additional options
Body section
Natural language description that updates based on configuration
Action-specific configuration fields
Connection points on left and right sides
💡 Trigger cards are slightly different as they don't have play buttons or option menus, but they do include arrows to switch trigger types.
How to Work with Action Cards
How to Select an Action Card
Click on an Action Card to select it.
The selected card will display a purple border (the "purple glow" in Lleverage) and a deeper shadow effect.
Selection is required for certain operations such as using Co-Pilot.
💡 Double-clicking a card will center it on your screen, making it easier to focus on a specific action.
How to Move Action Cards
Select the Action Card you want to move.
Click and hold the card to drag it to a new position.
Release the card to place it in the new location.
The connections will automatically adjust to follow the card.
💡 Moving cards helps you organise your workflow visually to better represent the logical flow.
How to Resize Action Cards
Hover over the right edge of the card until you see the resize cursor.
Click and drag left or right to adjust the width.
Release when the card reaches your desired size.
⚠️ Action Cards have a minimum width for accessibility purposes, so you cannot make them too narrow.
How to Test an Action Card
First, run the workflow once. The play button will only appear on non-trigger Action Cards after the workflow has been run.
Click the play button on the Action Card you want to test.
The action will execute using the current workflow variables that are available.
Values will flow into and out of the card as they would during a normal run.
The output will appear in the Output Panel, allowing you to check results.
💡 Testing individual actions helps identify and resolve issues before they affect the entire workflow.
How to Expand or Collapse an Action Card
Click the chevron in the top right corner of the card.
When collapsed, the card shows only its header and natural language description.
When expanded, the card shows all configuration options.
Use collapse to save space when working with complex workflows.
Input Expansion and Height
Currently it is not possible to expand the overall height of an Action Card, but certain inputs can be expanded individually.
Hover over the bottom-right corner of an input field.
If an arrow icon appears (diagonal from top right to bottom left), click it to expand the input.
This gives you an expanded view of the input, which is most common in prompts and code boxes.
Many inputs also support auto-expanding height to fit content.
💡 If you notice an input that does not expand properly, please let the Lleverage UK team know and we will aim to fix it.
Important Action Card Considerations
The natural language description updates automatically based on your configuration.
Selected cards with the purple glow receive focus for Co-Pilot suggestions.
Each action type has different configuration options in the body section.
Card connections establish the sequence of execution in your workflow.
Cards can be rearranged at any time to change your workflow structure.
⚠️ Workflows execute from left to right following the connections between cards. The arrangement and connections determine the execution path.
Last updated