Get a Demo Get Started

Comment & Mention Notifications

Get Started

Ship this workflow

Pick how you want to build it.

Try it in the dashboard Fastest Go to Workflows → New Workflow → Use sample workflow in your workspace, and select this workflow. Try it
Build with the SuprSend Agent Try the agent
Build with SuprSend MCP Set up MCP

When to use this workflow

    A direct mention is buried among routine comments. The comment that actually needs the user reads the same as every other one.

    A busy thread sends a separate ping for every reply. An active conversation fires one notification per reply, fast.

    A user's own comment pings them about it. Commenting in a thread they are part of notifies them of their own action.

    Comments on resources a user does not own create noise. Activity that has nothing to do with the user still reaches them.

How it works

1

A comment is posted

Someone comments, replies, or @-mentions a user (COMMENT_CREATED), and the workflow starts.

Trigger
2

Self-comments are skipped

If the user who commented is the user who would be notified, the run exits without sending.

BranchExit
3

Mentions send immediately

A direct @-mention notifies the user right away, with no batching.

BranchMulti-Channel
4

Replies to your comment are grouped

A reply to a comment the user wrote is grouped by thread over a 15-minute window and sent as one notification.

BranchBatchMulti-Channel
5

Comments on your resources are grouped

A new comment on something the user owns is grouped by thread over a 30-minute window into an activity summary.

BranchBatchMulti-Channel

Best practices

    Match each batch window to how fast the activity moves

    Replies arrive in quick bursts, so a short window like 15 minutes groups them. Comments on a resource arrive slowly, so 30 minutes works. Tune each batch to your pace.

    Group each batch by its thread

    One notification then covers one conversation. Without it, unrelated threads merge into a confusing summary.

    Show the comment text and a thread link in each digest

    A bare "3 new comments" makes the user go hunting. Show what was said and link straight to the thread.

Common mistakes to avoid

    Treating every comment as a mention

    Routine replies then interrupt like an @-mention, and the urgent ones stop standing out.

    Notifying a user about comments that aren't theirs

    A user should hear only about mentions, replies to them, and comments on what they own.

    Using one template for all three notifications

    A mention is urgent, a reply less so, a comment on your resource least. One template gives them all the same weight.

What users receive

The actual notifications this workflow sends, on each channel.

Comment on My Resource

Email
Comment on My Resource — Email
In-app inbox
Comment on My Resource — In-app inbox
Slack
Comment on My Resource — Slack

What good looks like

Primary signal Replies acted on

Comments get answered

Mentions and replies get opened and responded to faster once the right user is notified.

Fatigue signal Opt-outs

Rising opt-outs on comment alerts

When users start switching off comment notifications, busy threads are pinging them more than the conversation needs.

Support

Frequently Asked Questions

Quick answers about setting up and running this workflow.

A direct @-mention sends immediately, because the user is called out by name. A reply to the user's own comment is grouped by conversation over 15 minutes. A comment on a resource the user owns is grouped over 30 minutes into an activity summary. The further the activity is from the user, the more it is grouped.

Comment notifications can go out on in-app inbox, email, Slack, Microsoft Teams, and mobile or web push. Each user only gets the channels they have enabled, and any they have turned off in their preferences are skipped automatically.

Yes. The immediate-versus-grouped split is set by the Branch conditions, and the grouping windows are set on each Batch node (15 minutes for replies, 30 for resource comments by default). Adjust them in the workflow editor, or ask the SuprSend MCP to change them for you.

Yes. By default this workflow sends on all of a user's channels in parallel. To send one channel at a time and stop as soon as the message is seen, swap the send for Smart Channel Routing. It tries the user's channels in order and only moves to the next if the message goes unseen, so they are not pinged everywhere at once. Ask the SuprSend MCP to set it up.

Trigger it with a payload shaped like the COMMENT_CREATED event: a recipient, an actor, and a notification_type of mention, reply, or comment. You can do this from the Test button in the workflow editor, by asking the SuprSend Agent in the dashboard, or through the API, CLI, or MCP.

Ship Comment & Mention Notifications in under 5 minutes.

Try directly in SuprSend

Fastest

Sign up and test the workflow directly in the dashboard.

Get Started

Build with the SuprSend Agent

Copy the prompt, paste it into the Agent in your SuprSend dashboard, and the workflow gets built for you.

Try the agent

Build it with SuprSend MCP

Set up SuprSend MCP in Claude Code, Cursor or Windsurf, copy the prompt, and the workflow builds itself in your workspace.

Set up MCP