This trigger fires when a user comment is added to a project and is especially useful for notification, moderation, and bot-command style automations. It does not cover task history entries or generic Note activity elsewhere in Rock.
This trigger is especially useful when comments themselves are part of the workflow rather than just conversation. Administrators often use it for lightweight bot commands, moderation patterns, or communication workflows that begin when somebody says the right thing in the right project.
The key setting is Text Match Mode. If you choose None, every comment matches. The other modes let you watch for a text fragment, a prefix, or a regular expression pattern. Regex is the most powerful option and is what makes slash-command style automations possible, such as /close or /assign @jane.
When you use Regex mode, named capture groups become merge fields for downstream events. That lets one comment both trigger the automation and carry the parameter values the workflow needs. The Validate button is there to help you test the pattern before saving so a typo does not silently make the automation useless.
Merge Fields
Entity is the project the comment was added to.CommentText is the full body of the comment.CommentPersonAlias is the commenter when one is known.ProjectType is the project's type.RegexGroup_* values are created for any named capture groups in the regex pattern when Regex mode is used.
Important
This trigger observes comments added through the plugin's own paths, such as the comment UI, the Add Project Comment workflow action, or the shared plugin helper. Comments created by unrelated Note code paths are not observed.