Notify your Discord channel whenever a team member imports or uploads a new session. Session result alerts are available on all teams (free and Pro).
Overview
Session result alerts are an activity feed for your team — every qualifying import can post to Discord with position, track, car, and session details. Unlike lap record alerts, they fire for every new session that passes your filters, not only when someone sets a PB.
Setup
- Open Dashboard → Teams → [team] → Settings
- Scroll to Discord Integration → Race Results Notifications
- Enable Discord Enabled for session results
- Paste a Webhook URL (separate from lap record and event webhooks)
- Choose Session Mode and Session Type filters
- Click Save Discord Settings
Use a different webhook URL than lap records if you want results in a separate channel (e.g. #race-results vs #lap-records).
Session filters
| Filter | Options | Default |
|---|---|---|
| Session mode | Offline, Online | Both enabled |
| Session type | Race, Qualifying, Practice | Race only |
Only sessions matching all selected filters trigger a Discord post.
Example: Enable Online + Race only to avoid spam from offline practice or qualifying — or enable all types for a complete feed.
When alerts fire
Alerts trigger when:
- A team member's session is newly inserted after import or upload
- The member is in the team (accepted membership or owner)
- Session result Discord is enabled with a valid webhook
- The session passes mode/type filters
Supported import paths:
- Browser upload / import on mylmu.app
- Sync Agent automatic import
- Any automatic import path that adds a new session to the member's history
Each session is notified once — retries and duplicates are skipped.
What does not trigger alerts
| Source | Discord alert? |
|---|---|
| Auto-import / upload | ✓ |
| Manual Trophy Room entry (owner adds result by hand) | ✗ |
| Re-processing an already-notified session | ✗ |
| Sessions filtered out by mode/type | ✗ |
Manual Trophy Room entries appear on the team Sessions tab but do not send Discord webhooks.
Relationship to shared sessions
Session result alerts fire on import, not on Share to team. A member can trigger a Discord post without sharing the session to the team library — and vice versa.
See Sharing sessions and Shared sessions tab.
Discord message format
Posts appear from MyLMU Bot as a rich embed:
| Part | Content |
|---|---|
| Title | Position emoji + session result (e.g. P1, P3, DNF) |
| Description | Driver name(s), finish position, event name |
| Fields | Car, position, category/class, track, session type, tyres (dry/wet), date, grid position (races), best lap, race time (races), team + session links |
| Color | Gold / silver / bronze / blue / red by finish position |
Event name format: {track} - {session type} (e.g. Spa - Race).
Links open the team dashboard and the member's session detail page.
vs lap record alerts
| Alert | Fires when | Volume |
|---|---|---|
| Session results | Any new imported session (per filters) | Every race night |
| Lap records | New or broken team fastest lap only | Occasional PBs |
Recommended setup:
- Session results → general activity channel
- Lap records → records/PB channel (or same channel if you prefer one feed)
Available on all teams
Session result Discord alerts do not require Pro.
Troubleshooting
| Issue | Likely cause |
|---|---|
| Import but no Discord | Webhook disabled; wrong mode/type filter; invalid webhook URL |
| Trophy Room entry silent | By design — only auto-detected imports trigger alerts |
| Too many messages | Narrow filters (e.g. Race + Online only) or use lap records instead |
| Member not in team yet | Only current members' imports count |