Melonly Triggers start workflows when something happens inside Melonly.
They can react to moderation logs, infractions, Melonly roles, sessions, shifts, breaks, and activity waves.This page explains what starts each Melonly trigger and what data it provides to the rest of the workflow.
Starts the workflow when a Melonly role is added to a user.This trigger runs regardless of whether the role change was made manually, by a workflow, or by another Melonly system.Output
User: The full Discord/Melonly user object affected by the role change.
Role: The Melonly role name as a string.
Moderator: The full Discord/Melonly user object that made the change, when available. This is not guaranteed for automated changes.
Use it when
A workflow should run after a Melonly role is added.
You want to send a message or trigger another action after the role change.
Melonly Role Removed
Starts the workflow when a Melonly role is removed from a user.This trigger runs regardless of whether the role change was made manually, by a workflow, or by another Melonly system.Output
User: The full Discord/Melonly user object affected by the role change.
Role: The Melonly role name as a string.
Moderator: The full Discord/Melonly user object that made the change, when available. This is not guaranteed for automated changes.
Use it when
A workflow should run after a Melonly role is removed.
You want to send a message or trigger another action after the role change.
Starts the workflow when a session is started.This trigger runs regardless of whether the session was started manually or by a workflow.Output
Id: The session ID as a string.
Playercount: The ER:LC player count at the moment the session started as a number.
Moderator: The full Discord/Melonly user object who started the session, when available. This is not guaranteed for automated events.
Aop: The session area of patrol as a string.
Use it when
A workflow should announce, log, or react to a session starting.
Session Vote Started
Starts the workflow when a session vote is started.Output
Id: The session vote ID as a string.
Votes Required: The number of votes required as a number.
Playercount: The current ER:LC player count at the moment the vote started as a number.
Moderator: The full Discord/Melonly user object who started the vote, when available. This is not guaranteed for automated events.
Aop: The session area of patrol as a string.
Use it when
A workflow should announce or react to a session vote starting.
Session Boosted
Starts the workflow when a session boost is triggered in Melonly.Output
Id: The session ID as a string.
Playercount: The current ER:LC player count at the moment the session was boosted as a number.
Moderator: The full Discord/Melonly user object who boosted the session, when available. This is not guaranteed for automated events.
Aop: The session area of patrol as a string.
Use it when
A workflow should log or react to a session boost.
Session Ended
Starts the workflow when a session ends.This trigger runs regardless of whether the session was ended manually, through shutdown, or by a workflow.Output
Id: The session ID as a string.
Duration: The completed session duration in whole seconds.
Moderator: The full Discord/Melonly user object who ended the session, when available. This is not guaranteed for automated events.
Aop: The session area of patrol as a string.
Use it when
A workflow should announce, log, or process a completed session.
Melonly triggers use events from moderation, staff management, sessions, and other dashboard systems.When using Melonly triggers, consider:
Outputs: Purple outputs are strings, blue outputs are numbers, yellow outputs are full Roblox objects, and green outputs are full Discord/Melonly user objects.
Current Data: Edited triggers provide the values stored after the edit.
Automatic and Manual Events: Some events, such as role changes, session changes, and activity waves, can be triggered manually, by workflows, or automatically by Melonly.
