---
title: Notification Events and Merge Tags Reference
description: "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…"
url: "https://brightleafdigital.io/docs/notification-events-and-merge-tags-reference/"
updated: "2026-10-18"
category: GravityOps Forum / Settings Reference Gravityops Forum
---

# 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 `` 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:

- ``: Email list of resolved subscribers.
- ``: Topic title for the current event context.
- ``: Mapped content field value from the submitted entry.
- ``: Direct URL to the topic.
- `Click here to see the new post`: HTML anchor link to the topic.
- `Guest`: Display name of the entry author (or `Guest` if unavailable).

## 5. BCC Normalization

If a notification's **To** field contains ``, the plugin normalizes recipients to:

- `to = {admin_email}`
- `bcc =`

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.