Conditions
Conditions are logic blocks that decide whether a workflow should continue or take a different path.They evaluate data, compare values, and check permissions to determine if an action should run. Conditions help you build smarter workflows that respond dynamically to your server, players, or data.
How Conditions Work
A condition checks if something is true or false.If the condition passes, the workflow continues, if not, it stops or follows an alternate route. For example:
- Checking if a player is a moderator before running an action
- Comparing two numbers to see if one is greater than the other
- Verifying if a user has a specific Discord or Melonly role
- Matching a session status before continuing
Conditions
Below is a complete list of all currently available condition types. Each condition evaluates data and returns a true or false result.
Conditions Overview
Working With Conditions
Conditions are the logic backbone of workflows.They let you control when actions run and how data moves through your automation. When designing workflows, consider:
- Data Sources – Conditions can use data from triggers, actions, or variables.
- Chaining – Combine multiple conditions to create complex logic.
- Fallbacks – Use alternate paths when conditions fail.
- Testing – Always test conditions to ensure they behave as expected.
Example Workflow Flow
- A trigger starts when a player joins your ER:LC server.
- A condition checks if the player is a moderator.
- If true, the workflow sends a Discord message.
- If false, it ends without running any actions.
Need help?
Still have questions? Join our Discord server for support.