Get Discord notifications when a team member sets a new fastest lap or breaks an existing team record. Lap record alerts are available on all teams (free and Pro).
Overview
Lap records are computed automatically when a member imports or uploads a session. If the session beats an existing team record (and passes your filters), MyLMU can post a rich embed to your Discord channel.
This is independent of the Sessions tab — records track imports, not manual shares. See Lap records for how records are calculated.
Setup
- Open Dashboard → Teams → [team] → Settings
- Scroll to Discord Integration
- Enable Discord Enabled (lap record alerts)
- Paste your Webhook URL
- Choose Session Mode and Session Type filters
- Choose Discord Record Mode (what types of records trigger a post)
- Click Save Discord Settings
Only owners and admins can configure webhooks.
Creating the webhook
In Discord: Channel settings → Integrations → Webhooks → New Webhook. Copy the URL and paste it into Settings. You can use the same channel as session results or a dedicated #lap-records channel — each alert type has its own URL field.
Session filters
Control which imported sessions can trigger lap record notifications:
| Filter | Options | Default |
|---|---|---|
| Session mode | Offline, Online | Both enabled |
| Session type | Race, Qualifying, Practice | Race only |
These filters should match (or be stricter than) your lap record filters in Settings — they use the same underlying session data.
If a session does not match the selected modes or types, no record check runs for Discord and no notification is sent.
Discord record mode
Choose which record types post to Discord when a new fastest lap is set:
| Mode | Posts when | Still tracked in app? |
|---|---|---|
| Both | New Track + Car or Track + Class record | ✓ |
| Track + Car | New fastest lap for a specific car | ✓ (class records still tracked, not posted) |
| Track + Class | New fastest lap for a car class (e.g. Hypercar, LMP2) | ✓ (car records still tracked, not posted) |
Use Both for maximum celebration. Use Track + Car or Track + Class if your Discord channel should only highlight one record type.
When alerts fire
All of the following must be true:
- The member is an accepted team member (or team owner)
- The session is newly processed after import/upload (browser import or Sync Agent)
- The session passes session mode and session type filters
- A new or improved team lap record is written (car and/or class, per wet/dry)
- Discord Enabled is on and a valid webhook URL is saved
- The record type matches Discord Record Mode
What does not trigger alerts
- Sessions imported before the member joined the team (no retroactive backfill)
- Sessions that do not beat an existing record
- Sessions filtered out by mode/type settings
- Record types excluded by Discord record mode (still visible on Lap Records tab)
- Duplicate processing — each record is notified at most once
Wet vs dry
Dry and wet laps are tracked separately. Discord titles include Wet when the record was set on wet tyres.
Discord message format
Posts appear from MyLMU Bot as a rich embed:
| Part | Content |
|---|---|
| Title | 🏆 New record or ⚡ Record broken (car or class, wet/dry) |
| Description | Driver (with country flag), track (with flag), record type |
| Fields | Car, lap time, session type (Online/Offline), tyre condition (Dry/Wet), previous record (if broken), team + session links |
| Thumbnail | Car brand logo when available |
| Footer | Powered by MyLMU |
Embed links open the team dashboard and the source session detail page.
Lap records vs session result alerts
| Lap record alert | Session result alert | |
|---|---|---|
| Trigger | New fastest lap only | Every new imported session |
| Volume | Low — highlights only | High — full activity feed |
| Best for | PB announcements | "Who raced today?" |
Many teams enable both, pointing lap records at a #records channel and session results at #race-results.
Available on all teams
Lap record Discord alerts do not require Pro. Any team owner can configure them.
Event email/Discord and calendar subscribe are separate Pro-gated features — see Event alerts.
Troubleshooting
| Issue | Likely cause |
|---|---|
| No message after a fast lap | Filters exclude the session; record mode excludes car/class; webhook disabled |
| Record on tab but no Discord | Discord record mode may exclude that record type; check wet/dry tab |
| Old sessions never alert | Records only evaluated at import time after joining the team |
| Webhook errors | Invalid or deleted Discord webhook — recreate in Discord and update Settings |