Core Docs - Engagement - Tips for Creating Triggered Workflows

Rock Version: v20.0
Last Modified: 2026-05-01 1:40 PM

When workflows are started from the group member triggers, they will pass in a few attributes for your convenience (as long as the attributes are defined). These include:

Be Persistent
Make sure the triggered workflow is Automatically Persisted. This will ensure it works correctly and as intended.  

Whenever possible, the workflow will also pass in the Group Member model as the entity of the workflow. You can access the group member properties and attributes by using the Attribute Set From Entity action combined with Lava like the following:

{{ Entity | Attribute:'HasBook' }}
{{ Entity.GroupMemberStatus }}
{{ Entity.GroupRole.Name }}
{{ Entity.PersonId | PersonById | Property:'PrimaryAlias' | Property:'Guid' }}

When Group Member Won't Be Passed
Some member workflow triggers won't pass the group member as the entity. For instance, for the Member Removed from Group and Alternate Placement workflow types there won't be a group member left to pass when these events are launched