Discord Integration & Webhooks

Pairing your 7 Days to Die server with a Discord guild keeps your community engaged when players aren't logged in. Two integration patterns cover almost every use case: one-way Discord webhooks for posting server events into a channel, and two-way chat bridging via a server manager for in-game ↔ Discord conversation. This guide covers both, the tools that support each, and the channel layout that scales.

Webhook vs. Chat Bridge — Which One?

Discord WebhookChat Bridge
DirectionServer → Discord (one-way)Server ↔ Discord (two-way)
What it sendsServer-generated events: player joins, deaths, restarts, custom alertsLive chat messages between game and channel
Setup difficultyTrivial — generate URL in Discord, paste into the tool that sends to itRequires a server-management tool with built-in bridge support (CSMM, similar)
Discord sideNo bot user neededBot user needed (the tool runs the bot)
Use caseStatus feed, "important events" channel, automated alertsActive community chat — players who are at work can keep up with the in-game banter

Setting Up a Discord Webhook

Discord webhooks are a built-in Discord feature. You don't need a bot, OAuth, or extra software on the Discord side — just a URL that posts to a specific channel.

  1. Open Discord: Server Settings → Integrations → Webhooks → New Webhook.
  2. Pick the target channel and a display name (e.g., "7D2D Server Bot"). Optionally upload an avatar.
  3. Click Copy Webhook URL. Treat this URL as a secret — anyone with it can post to your channel.
  4. Paste the URL into the tool that will send events. The exact location depends on the tool — see "Tools that send webhooks" below.

To test outside any tool, you can post a message directly with curl:

curl -X POST -H "Content-Type: application/json" \
  -d '{"content":"Hello from 7D2D test."}' \
  https://discord.com/api/webhooks/<your-webhook-id>/<your-token>

If the message lands in your channel, the URL works. If you get a 401 or 404, the URL is wrong or has been deleted.

Tools That Send Webhooks (or Bridge Chat)

The dedicated server doesn't natively post to Discord — you need a layer that watches the server log or hooks the chat system, formats messages, and POSTs to the webhook (or runs a bot for bidirectional bridging).

  • CSMM (Catalysm's Server Manager) — open-source, self-hosted web manager for 7D2D. Supports both Discord webhooks (event notifications, custom log-string detection) and full bidirectional chat bridging via a Discord bot. The most feature-complete option that's actively maintained. GPL-3.0.
  • Hosting-panel built-ins — many hosts (GTXGaming, Nitrado, BisectHosting, etc.) expose a Discord webhook field in their panel for "post X event to my channel." Easiest if you're already on a managed host.
  • Custom scripts — if you have telnet access (port 8081), you can tail the server log over the telnet socket and POST anything you want to Discord. A 30-line Python or Node script handles this. See Server Log Masterclass for the log levels you'd want to forward.

Older third-party tools and mods exist (and you'll see them named in legacy guides), but for V2.6 servers in 2026, CSMM or your hosting panel are the maintained paths. Verify any older "Discord chat bridge" mod is updated for V2.6 before installing — many compatibility-broke during the 2.0 → 2.6 transition.

Recommended Discord Channel Layout

For anything beyond a casual server, splitting events into purpose-specific channels makes them readable. A common layout:

ChannelWhat goes there
#server-statusRestarts, planned downtime, "server is back up" notices. High-signal, low-volume.
#in-game-chatTwo-way chat bridge between game and Discord (if running CSMM or similar).
#player-eventsJoins, leaves, deaths, level-ups, blood-moon-survivor announcements. Higher volume — keep it separate so it doesn't bury status updates.
#admin-log (private)Admin-only. Bans, kicks, command execution, anti-cheat triggers, chunk-corruption warnings. Restrict permissions so players can't see it.
#tickets or #helpPlayer support requests. CSMM has a built-in support-ticket system that posts to a channel.

Webhook Security

  • Don't commit webhook URLs to git. Treat them like API keys. If a URL leaks, regenerate it in Discord and update your tool.
  • Don't accept arbitrary input from in-game players into a webhook without sanitization — Discord renders mentions, links, and limited markdown, and a player could spam mentions to entire roles.
  • Rate-limit your sender. Discord's webhook rate limit is generous but not infinite (per-channel and per-account). A misbehaving log forwarder can hit it during a Blood Moon and lose messages.
  • Hide admin-event channels. The admin-log channel should be readable only by admin roles — players don't need to see kick reasons or anti-cheat triggers.