Do I need to invite a bot?

No - Discord channel webhooks are sufficient. No bot install, no Manage Server permission needed.

Can I @mention a role on regressions?

Yes. Add the role mention to the message template and Discord will ping the role when the embed posts.

Are messages rate-limited?

Discord rate-limits webhooks at 30 messages/minute per channel. Lastest batches build updates so this is rarely hit.

Can I send to multiple channels?

Yes - one webhook per target channel, plus routing rules per repo / status.

Can I edit the embed?

Use a Custom Webhook (see /integrations/webhooks) to send your own Discord embed payload.

Notifications

Indie-stack-friendly Discord alerts for visual regressions

Most indie and OSS teams live on Discord. Lastest posts build results to any Discord channel via webhook - same routing model as Slack, no bot install, no OAuth, no server admin required.

Try Lastest free →Read the docs

What you get

Three things this integration does - and what they mean for your team.

Webhook, no bot

Discord channel webhooks. No bot user, no Manage Server permission, no OAuth - paste the URL, hit save, done.

Rich embeds

Verdict color (green / amber / red), passed / failed counts, branch, SHA, build link. Mention roles like <@&qa> on regressions only.

Per-server routing

Different repos can post to different Discord servers and channels. One Lastest instance can fan out to as many Discord webhooks as you need.

How it works

Data flow, configuration, and result routing - visualised.

Diagram 1 · Webhook flow

Build event → Discord embed

Same dispatcher as Slack: build.completed → routing rule match → POST to Discord webhook → embed posted in channel.

Diagram 2 · Embed anatomy

What the message actually contains

Color-coded title, status counts, branch, SHA, build URL, optional role mention. Markdown rendered natively.

Diagram 3 · Multi-server fanout

One Lastest, many Discord servers

Per-repo rules map to per-channel webhooks. The OSS server gets one feed, the day-job server gets another.

Configure

Drop-in config for Discord

Sample Discord embed Lastest sends on build completion

{
  "username": "Lastest",
  "embeds": [{
    "title": "Build #842 - safe to merge",
    "url": "https://your-lastest/builds/842",
    "color": 5814783,
    "fields": [
      { "name": "Repo", "value": "my-app", "inline": true },
      { "name": "Branch", "value": "feat/checkout", "inline": true },
      { "name": "SHA", "value": "abc1234", "inline": true },
      { "name": "Tests", "value": "8 passed · 0 review · 0 failed" }
    ]
  }]
}

Frequently asked questions about Lastest + Discord

Do I need to invite a bot?: No - Discord channel webhooks are sufficient. No bot install, no Manage Server permission needed.
Can I @mention a role on regressions?: Yes. Add the role mention to the message template and Discord will ping the role when the embed posts.
Are messages rate-limited?: Discord rate-limits webhooks at 30 messages/minute per channel. Lastest batches build updates so this is rarely hit.
Can I send to multiple channels?: Yes - one webhook per target channel, plus routing rules per repo / status.
Can I edit the embed?: Use a Custom Webhook (see /integrations/webhooks) to send your own Discord embed payload.

Other integrations