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:

• Saves today’s date to a MembershipDate Person Attribute
• Logs a short note to a MembershipNote Person Attribute

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.

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.