Community automations

Community automations connect your HLB communities to workflows. Member activity can start follow-ups, and group access can be granted or removed automatically. This cuts down on watching each group by hand and applies the same access logic to every qualifying contact.

A local service business with a customer community could start onboarding when someone gains access to a group, notify a moderator when someone posts, or follow up when someone signs up for a community event.

Available triggers:

• Group Access Granted and Group Access Revoked start a workflow after a member gains or loses access to a group.
• Group Joining Request Rejected runs after a pending request to join a group is declined. Requested to Join Group is designed for pending requests before access is approved.
• Group Post Created and Group Comment Created run when someone adds a post or comment. Comment workflows only run on posts that allow comments.
• Member Registered for Group Event runs when a member signs up for a community event.

The Grant Group Access and Revoke Group Access actions change a contact's access to a selected group inside a larger workflow.

To set one up, create or identify the community group first. In the Workflow Builder, add the community trigger or action you need and select the group, which every trigger requires. Then add any optional filters, such as channel, post title, post content, comment content or event title. For comment triggers, the post content filter checks the original post. Check which operator each filter uses, such as exact match or contains, add your actions, such as notifications, tags or follow-up messages, and test the workflow before publishing.

Private channel access has its own separate triggers and actions.