Notifications Guide

Learn how Streamlinx notifications work, when they're sent, and how to customize them for your Discord server.

How Notifications Work

Streamlinx continuously monitors your tracked streamers and sends Discord notifications when their streaming status changes.

Monitoring Process

1. Checking: Every 60 seconds, Streamlinx checks all tracked streamers on their platforms
2. Detection: Compares current status with previous status to detect changes
3. Event: When a change is detected, an event is published to the notification system
4. Delivery: Notifications are sent to the configured Discord channels

Notification Types

Live Notifications

Sent when a streamer goes live (starts streaming):

Trigger: Stream status changes from offline to live

Content Includes:

• Streamer name and avatar
• Stream title
• Game/category being played
• Direct link to stream
• Platform indicator (Twitch/YouTube/Kick)
• Current viewer count
• Role mention (if configured)

Example:

🔴 @Streamers pokimane is now live!
 
🎮 Valorant
"ranked grind to radiant | !newvid"
 
👥 12,453 viewers
 
🔗 https://twitch.tv/pokimane

Offline Notifications

Sent when a streamer goes offline (ends stream):

Trigger: Stream status changes from live to offline

Content Includes:

• Streamer name and avatar
• Message that stream has ended
• Stream duration
• Platform indicator

Example:

⚫ pokimane's stream has ended
 
⏱️ Duration: 4 hours 23 minutes
 
Thanks for watching!

Update Notifications

Sent when stream information changes while live:

Trigger: Stream title or game/category changes during a live stream

Content Includes:

• Streamer name
• New stream title
• New game/category
• "Stream updated" indicator

Example:

🔄 pokimane updated their stream
 
🎮 Just Chatting (was: Valorant)
"chilling and answering questions | !newvid"

Notification Channels

How Notifications Are Sent

When you add a streamer, you specify which Discord channel should receive notifications for that streamer. Each streamer can be assigned to a different channel, allowing you to organize notifications however you prefer.

Configuring Notification Channels

Via Discord Bot: When adding a streamer, specify the channel:

/streamer add twitch username:shroud channel:#twitch-streams

Via Web Portal:

1. Login at streamlinx.io
2. Select your server
3. When adding a streamer, select the notification channel from the dropdown

Per-Streamer Channel Routing

You can organize notifications across multiple Discord channels by routing each streamer individually:

By Platform:

• #twitch-streams - Twitch streamers
• #youtube-streams - YouTube streamers
• #kick-streams - Kick streamers

By Game:

• #valorant-streams - Streamers playing Valorant
• #minecraft-streams - Streamers playing Minecraft

By Priority:

• #vip-streams - Your most important streamers
• #partner-streams - Partner streamers only

Notification Customization

Role Mentions

Tag a role when notifications are sent to alert your community. Configure role mentions via the web portal:

1. Use /portal to access the web portal
2. Navigate to your server's streamers page
3. Click on a streamer to edit their settings
4. Configure the role to mention in the "Role Mention" field

Per-Streamer Configuration: Premium users can set different roles for different streamers.

Custom Message Templates

Customize the text content of notifications using templates via the web portal (available for all users):

1. Use /portal to access the web portal
2. Navigate to your server's streamers page
3. Click on a streamer to edit their settings
4. Customize the online/offline message templates
5. Use the live preview to see how it will look

Available Variables:

Template Limits:

• Maximum 2000 characters (Discord limit)
• Must include at least {url} or {streamer}
• HTML/Markdown not supported in templates

Custom Identity (Premium)

Make notifications appear with custom names and avatars. Configure via the web portal:

1. Use /portal to access the web portal
2. Navigate to your server's settings
3. Configure custom username and avatar

Options:

• Custom Name: Replace "Streamlinx" with any text

  • Use streamer name: {streamer} Stream Alert
  • Use server name: YourServer Streams
  • Static text: Live Now!

• Custom Avatar: Set a custom image

  • Use streamer avatar: {streamer_avatar}
  • Use server icon: {server_icon}
  • Custom image link: https://example.com/icon.png

Example Configuration:

Name: "{streamer} is Live!"
Avatar: {streamer_avatar}

Result: Each notification appears as if it came from the streamer themselves.

Notification Settings

Auto-Delete

Live notifications are automatically deleted when the stream ends. This is enabled by default and requires no configuration.

How it Works:

• The bot automatically deletes the original "streamer is live" message when they go offline
• An offline notification is sent instead
• Keeps your notification channel clean and clutter-free

Requirements:

• Bot must have "Manage Messages" permission in the notification channel
• Original message must still exist (not manually deleted)

Embed Colors

Notification embeds use platform-specific colors by default:

• Twitch: Purple (#9146FF)
• YouTube: Red (#FF0000)
• Kick: Green (#53FC18)

Notification Cooldowns (Premium)

Prevent notification spam by setting cooldown periods between notifications for the same streamer.

Why Use Cooldowns?

• Streamer has connection issues causing multiple "going live" events
• Streamer restarts stream for technical reasons
• Reduce notification spam during unstable streams

How It Works:

1. When a notification is sent, a cooldown timer starts
2. During the cooldown period, no new notifications are sent for that streamer
3. After the cooldown expires, notifications resume normally

Configuration Levels:

Cooldown Range: 1 minute to 24 hours (1-1440 minutes)

Example Scenarios:

• 5 minute cooldown: Streamer goes live, connection drops after 2 minutes, reconnects. No duplicate notification sent.
• 30 minute cooldown: Streamer takes a break mid-stream. When they return, no new notification is sent.
• No cooldown: Every stream start triggers a notification (default behavior for Free tier)

Configuration via Web Portal:

1. Use /portal to access the web portal
2. Navigate to your server's settings page for guild-wide cooldown
3. Or edit individual streamers to set per-streamer cooldowns

Notification Filter Rules (Premium)

Control when notifications are sent based on stream content using filter rules.

Filter Types:

• Title Match: Filter based on stream title content
• Game/Category Match: Filter based on game or category

Match Modes:

• Matches: Only send notification if the pattern is found
• Does Not Match: Only send notification if the pattern is NOT found

Examples:

• Only notify for "Tournament" streams → Title matches "Tournament"
• Skip "Just Chatting" notifications → Game does not match "Just Chatting"
• Only notify for specific games → Game matches "Valorant|League of Legends"

Limits: Up to 5 filter rules per streamer

Configuration:

1. Use /portal to access the web portal
2. Navigate to your server's streamers page
3. Click on a streamer to edit their settings
4. Add filter rules in the "Notification Filters" section

Notification Behavior

Duplicate Prevention

Streamlinx prevents duplicate notifications:

• If a streamer is already marked as live, no new notification is sent
• If a stream ends and immediately restarts (platform glitch), only one offline/live pair is sent
• Update notifications are rate-limited to 1 per 5 minutes

Failed Notifications

If a notification fails to send:

Common Causes:

• Bot missing permissions in notification channel
• Notification channel deleted
• Discord is experiencing issues
• Message content violates Discord ToS

Handling:

• Failed notifications are logged for debugging
• No automatic retry (to prevent spam)
• Check bot permissions if notifications stop working

Fix Permissions:

1. Go to channel settings
2. Find the Streamlinx bot in permissions
3. Ensure these permissions are enabled:
   • Send Messages
   • Embed Links
   • Manage Webhooks (if using custom name/avatar)
   • Manage Messages (if using auto-delete)

Rate Limits

To comply with Discord's rate limits:

• Maximum 5 notifications per second per channel
• If exceeded, notifications are queued and sent with delay
• During high activity (many streams going live), expect slight delays

Platform-Specific Behavior

All platforms share the same core notification features (live/offline/update notifications, viewer count, game/category). The key differences are detection speed and specific platform limitations.

Twitch

Detection Speed: Near-instant (typically under 30 seconds)

Unique Features:

• VOD link button in offline notifications (when available)
• Game box art thumbnails in embeds

Embed Color: Purple (#9146FF)

YouTube

Detection Speed: 2-5 minutes (YouTube platform limitation)

Limitations:

• No VOD links in offline notifications
• Premieres are not treated as live streams (by design)

Embed Color: Red (#FF0000)

Kick

Detection Speed: Near-instant (typically under 30 seconds)

Limitations:

• No VOD links (Kick doesn't make past broadcasts available)

Embed Color: Green (#53FC18)

Troubleshooting

Notifications Not Sending

Check These:

1. Bot Permissions: Ensure bot has "Send Messages" and "Embed Links" in notification channel
2. Channel Exists: Verify notification channel hasn't been deleted
3. Streamer Status: Confirm streamer is actually live (check platform directly)
4. Platform Status: Twitch/YouTube/Kick may be experiencing issues (check status pages)

Debug Steps:

1. Use /portal to access the web portal
2. Check that streamers are configured on the streamers page
3. Use /subscription to check your current tier and limits

Delayed Notifications

Possible Causes:

1. Platform Delays: Twitch/YouTube/Kick may be experiencing delays
2. Connection Refresh: Platform connections occasionally need renewal (automatic)
3. High Activity: Too many notifications at once

Solutions:

• Wait 2-3 minutes for notifications to arrive
• Check Twitch Status, YouTube Status, or Kick Status
• Contact support if delays persist beyond 5 minutes

Duplicate Notifications

If you receive multiple notifications for the same stream:

Causes:

• Multiple servers tracking the same streamer
• Bot was restarted during stream detection
• Primary and backup monitoring both triggered (rare)

Solutions:

• This is rare and usually self-corrects
• If persistent, contact support

Missing Update Notifications

Update notifications are intentionally rate-limited:

• Only one update per 5 minutes per streamer
• Prevents spam when streamers frequently change titles
• Not all stream updates may trigger notifications

Best Practices

Organize by Channel

Use multiple notification channels to keep things organized:

#twitch-streams - Twitch streamers only
#youtube-streams - YouTube streamers only
#vip-streamers - Your most important streamers

Use Role Mentions Wisely

• Don't ping @everyone (annoying)
• Create a dedicated role like @Stream Alerts that users can opt into
• Consider different roles for different channels

Keep Templates Clean

• Don't make templates too long (hard to read)
• Include essential info: streamer, game, link
• Use emojis sparingly
• Test templates before deploying

Enable Auto-Delete

For active communities with many streamers:

• Keeps notification channels clean
• Prevents channel clutter
• Users can still see live streams in real-time

Need Help?

• Check Troubleshooting for common issues
• Join Discord support server for help
• Email support: support@streamlinx.io
• Run /help in your Discord server