Notification Events and Merge Tags Reference

GravityOps Forum adds notification events and merge tags for forum activity on Premium plans.

1. Custom Notification Events #

Two custom events are available for form notifications:

• gofrm_new_topic: Fired for new topic creation.
• gofrm_new_reply: Fired for new reply creation.

2. Default Notification Fallback #

If no notification is configured for one of the forum events, the plugin creates a default notification payload at runtime.

Default behavior includes:

• Subject based on topic vs reply context.
• Subscriber recipients routed through BCC.
• Topic URL and post-author details in the message body.

3. Subscriber Recipient Strategy #

When {gofrm_subscribers} is present:

• The plugin resolves subscriber emails and injects them as a comma-separated list.
• The current post author is removed from the recipient list.

For replies, recipient gathering can include both:

• Topic subscribers
• Forum subscribers

User-follow subscriptions are also included when present.

4. Merge Tags #

Supported merge tags:

• {gofrm_subscribers}: Email list of resolved subscribers.
• {topic_title}: Topic title for the current event context.
• {post_content}: Mapped content field value from the submitted entry.
• {topic_url}: Direct URL to the topic.
• {topic_link}: HTML anchor link to the topic.
• {post_author}: Display name of the entry author (or Guest if unavailable).

5. BCC Normalization #

If a notification’s To field contains {gofrm_subscribers}, the plugin normalizes recipients to:

• to = {admin_email}
• bcc = {gofrm_subscribers}

This avoids exposing subscriber addresses to each recipient.

6. Operational Notes #

• Merge-tag replacement runs only when one or more supported tags are found.
• Topic URL resolution uses the forum slug + topic ID route.