Events

Now that we've defined when our Automation will be triggered, let's move to the next part of an Automation, defining what happens when it's launched. Note that Event options are the same regardless of Trigger Type.

Continuing with our Adult Connection Status Change example, we will start the "Launch Workflow" event, triggering the "Member Welcome" workflow, which will set up the Person Profile for new members.

In addition to a Workflow Launch our Automation will run a "Lava Event".

This event Logs a short note for the new member.

When using Lava in Automations, you have many valuable fields to draw from to provide context:

• Entity: The entity that was added, modified or deleted.
• Person: The person that added, modified or deleted the entity.
• OriginalValues: The original values of the entity before it was modified. This is only valid if State is Modified.
• ModifiedProperties: The names of the properties that were modified on the entity. This is only valid if State is Modified.
• State: The state of the entity during the save operation.

And there you have it, we made an Automation that sets up data for new adult members, no human action needed! Now you have seen an example of Lava and Workflows, but there's more Events to choose from.

Automation Events List

Below is a complete list of Events that can be run for an Automation.

Log Message - Writes a message to the Rock Logs each time the automation runs, which helps when you're testing an automation or want a record of what it did. Enter a Category, choose a Log Level (Trace, Debug, Information, Warning, Error or Critical) and write the Message. The message can include Lava, using the same merge fields as the Lava Event. Rock only records the message when that category and level are turned on in the log settings at Admin Tools > Settings > Rock Logs. See Use Rock Logs for how logging levels work.

Send Fallback Chat Notification - Sends a system communication by email or SMS to Chat members who don't get device notifications, so urgent messages still reach them. Use it with the Chat Message trigger, since it gets the chat channel and its members from that trigger. Choose the System Communication, then adjust Notification Suppression Minutes (default 60) and Device Seen Within Days (default 45) if needed. For full setup steps, see Fallback Chat Notifications.

With a trigger and event configured and the Save button pressed, the automation runs on its own. Now you are free to lean back in your chair and put your hands behind your head.