Quick overview

• Command: /alerts <subcommand>

• Purpose: Subscribe channels to creator updates per platform, customize message templates, test alerts, and enable or disable platform-wide alerting.

• Platforms supported (examples): Twitter / X, YouTube, TikTok, Instagram, Threads — these platform choices are exposed in the dashboard builder.

How alerts work (short)

• You add an alert to track a username or URL for a particular platform and target a destination channel. When the tracked account posts (or the feed detects a new item), GR Rocket posts a templated alert to the configured channel.

• You can set a per-platform template with placeholders (for example {user}, {platform}, {url}) and test the template with /alerts test before enabling production posting.

• The dashboard mirrors the commands with a visual builder (stage → preview → push) so staff can preview formatting and attachments before going live.

Command reference

Each command below includes Purpose, Syntax / options, Examples, Who can run it, and Notes / tips.

/alerts add <platform> <username/url> <channel>

Purpose — Track a creator/page on the given platform and post alerts to the specified channel when new content appears.
Syntax

/alerts add platform:<platform> username:"CreatorName or URL" channel:#alerts

Example

/alerts add platform:youtube username:"Gamerogue" channel:#social

Who can run it — Staff/managers with Command Permissions for alerts.
Notes / tips

• The platform choice is typically a dropdown (YouTube/X/TikTok/Instagram/Threads). Use the dashboard or the command to add creators. The dashboard builder also shows a preview of the alert template.

• For URLs accept full profile URLs where applicable (the command will parse what it needs). Use /alerts test after adding to verify format and delivery.

/alerts remove <platform> <username/url>

Purpose — Stop tracking a creator on the given platform.
Syntax

/alerts remove platform:<platform> username:"CreatorNameOrUrl"

Example

/alerts remove platform:twitter username:"@Gamerogue"

Who can run it — Staff/managers.
Notes / tips

• Removing the subscription stops further alerts for that creator. The dashboard keeps an active list so you can confirm removal visually.

/alerts list

Purpose — Show all currently tracked accounts and their configured destination channels.
Syntax

/alerts list

Example

/alerts list

Who can run it — Staff.
Notes / tips

• Useful for audits and to find which channel a creator’s alerts target. The dashboard Active Alerts Manager also shows the same list and quick controls.

/alerts test <platform> <username>

Purpose — Send a sample/test alert for the specified account so you can validate template formatting and channel rendering.
Syntax

/alerts test platform:<platform> username:"CreatorName"

Example

/alerts test platform:youtube username:"Gamerogue"

Who can run it — Staff.
Notes / tips

• Always run /alerts test after setting or changing a platform template to confirm placeholders, embeds, and image rendering before enabling alerts to post real events. The command helps catch broken templates and validate webhook/permissions.

/alerts setmessage <platform> <template>

Purpose — Define or update the default message template used for alerts on a specific platform. Templates support placeholders (see below).
Syntax

/alerts setmessage platform:<platform> message:"{user} just posted: {url}"

Example

/alerts setmessage platform:twitter message:"{user} just posted on X: {url}"

Who can run it — Staff/managers.
Notes / tips

• Templates typically support {user}, {platform}, {url} and sometimes additional platform-specific tokens. Use /alerts test to preview how the template resolves. The dashboard also includes a per-platform template editor.

/alerts enable <platform> & /alerts disable <platform>

Purpose — Globally enable or disable posting of alerts for a whole platform across the server. Useful to temporarily pause all Twitter or YouTube alerts during incidents or maintenance.
Syntax

/alerts enable platform:<platform>
/alerts disable platform:<platform>

Example

/alerts enable platform:youtube
/alerts disable platform:twitter

Who can run it — Server staff/managers.
Notes / tips

• Use disable when you need to pause a platform’s flood of alerts (e.g., during a major live event) and enable to resume. This toggles platform-level posting without removing individual subscriptions.

Template placeholders

Common placeholders supported by platform templates include:

• {user} — the creator/channel name (or handle).

• {platform} — the platform name (YouTube, X, TikTok, etc.).

• {url} — the direct link to the new post/content.

(Exact supported placeholders may vary by implementation and platform; the dashboard’s template editor and /alerts setmessage helpfully show what tokens are available when editing.)

Permissions & bot requirements

Bot requirements

• Send Messages and Embed Links in the destination channel (to post rich alerts).

• If the bot posts images or attaches thumbnails, make sure it can upload files.

• If you use webhooks or external integrations the bot may require additional networking permissions, but for most setups Send/Embed/Attach rights are sufficient.

Staff / Command Permissions

• Grant only trusted staff access to add/remove alerts. Use the Dashboard → Command Permissions to control who may manage alerts (Manager or custom role recommended).

Workflows & best practices

• Staging → Test → Enable: Use the dashboard builder or /alerts setmessage to create a template; then run /alerts test before enabling to ensure it renders well across desktop and mobile.

• Group alerts by channel: Send creator updates for related creators (e.g., a game dev team) to a single channel so staff can review collectively.

• Use per-platform templates: Tailor wording by platform (e.g., “New video” vs “New Tweet/X”); include platform icon or short prefix for clarity.

• Pause during surges: If a creator produces many updates or an external event causes many posts, use /alerts disable <platform> temporarily.

Troubleshooting checklist

• Alerts not posting

  • Run /alerts test to confirm the bot can post a sample; check the channel the alert targets.

  • Verify the bot has Send Messages and Embed Links permissions for the destination channel.

• Template placeholders not resolving

  • Confirm you used supported placeholders ({user}, {platform}, {url}) and that the platform template is set (/alerts setmessage).

• Platform disabled

  • If a platform has been globally disabled, re-enable it with /alerts enable platform:<platform>.

• Invalid username or URL

  • Use a full profile URL (if supported) or the exact platform handle. If unsure, add and then run /alerts test to validate.

• Rate limits or missed posts

  • Very high-volume creators may cause many alerts; consider batching, limiting, or using /alerts disable during surges.

Quick cheat-sheet

/alerts add platform:<platform> username:"CreatorNameOrURL" channel:#alerts
/alerts remove platform:<platform> username:"CreatorNameOrURL"
/alerts list
/alerts test platform:<platform> username:"CreatorName"
/alerts setmessage platform:<platform> message:"{user} just posted: {url}"
/alerts enable platform:<platform>
/alerts disable platform:<platform>