Triggers
Triggers are the starting points of any workflow in Lleverage. They determine how your workflow is initiated and what form it will take when published. Triggers define the entry point for your automat
Last updated
Triggers are the starting points of any workflow in Lleverage. They determine how your workflow is initiated and what form it will take when published. Triggers define the entry point for your automat
Last updated
Form: Collects input through a traditional form interface
Chat: Creates a conversational interface for your workflow
API Call: Starts with a request from your application
Schedule: Runs on a recurring schedule or at specific times
Integration: Triggers based on events from external applications
💡 You can have multiple triggers for multi-step workflows, but your primary trigger determines the publishing state of your workflow.
Open the canvas in the Workflow Studio
Locate the box that says "What starts this workflow? Select an action trigger"
Click on the box to see the available trigger options
Select your preferred trigger type (Form, Chat, API Call, Schedule, or Integration)
Configure the settings specific to your selected trigger
Look for the icon in the top right corner of your trigger action (arrows pointing right and left)
Click on this icon to open the trigger selection menu
Choose from the five available trigger types to replace your current trigger
Configure your new trigger as needed
💡 Switching triggers allows you to easily change how your workflow starts without rebuilding your entire automation.
Select "Form" as your trigger type
Click "Add Field" to create a new input field
Enter a label for your field in the text box
Select the field type by clicking the icon on the right (options include Text, Number, Toggle, File, List, and Object)
Check the "Required" box if users must complete this field
Add additional fields as needed by repeating steps 2-5
Use the delete icon (right side) to remove unwanted fields
⚠️ Required fields must be filled out by users before the form can be submitted.
Select "Chat" as your trigger type
No additional configuration is needed for basic setup
This trigger creates a conversational interface that will save chat memory
💡 Chat triggers are ideal for creating chatbot experiences within your workflow.
Select "API Call" as your trigger type
Click "Add Field" to create input parameters for your API
Enter field names and select appropriate data types
Under "Authentication," select either "Lleverage API Token" (recommended) or "None"
⚠️ If you publish with Lleverage API Token enabled, you'll need to specify this in your embedded code using your organization's settings.
Select "Schedule" as your trigger type
Choose between "Specific Time" or "Intervals"
For Specific Time:
Set the hour and minute
Select AM or PM
Choose the date
For Intervals, select a frequency:
Every 5, 10, 15, or 30 minutes
Every 1, 2, 4, 6, or 12 hours
💡 Scheduled triggers allow your workflow to run automatically without manual intervention.
Select "Integration" as your trigger type
In the "Search App" field, type or scroll to find your provider (e.g., Gmail)
Select the provider from the list
Choose an action that will trigger your workflow (e.g., "New Sent Email")
Complete the authentication by selecting "Online Authentication"
Configure any optional properties provided by the integration
⚠️ Understanding variables is important when working with Forms and API Calls, as they create output variables that can be used throughout your workflow.
Each trigger has a natural language description at the top of its action to help you understand its function
Your choice of trigger determines what your workflow will become when published:
Form triggers publish as forms
Chat triggers publish as chat interfaces
API Call triggers publish as API endpoints
Schedule triggers publish as scheduled tasks
Integration triggers publish as integration-driven automations
Triggers can be enabled or disabled to prevent unforeseen workflow runs
💡 For more information about variables and how they work with triggers, visit the Variables section in the documentation.
