Discord integration
Invite the bot, bind a channel, and get reports and alerts where your team already is.
PulseNode v5.0.2Paper · Spigot1.21 – 1.21.x
Reports by email are easy to miss. The Discord bot puts them in the channel your staff already have open.
Setup
Invite the bot
From the dashboard, Server → Integrations → Connect Discord. This opens Discord's own authorisation screen for your server.
The bot needs permission to view the channel and send messages in it. Nothing else.
Pick a channel
Back in the dashboard, choose which channel receives this server's reports and alerts.
The binding is per PulseNode server, so a network can send
survivalandlobbyto different channels — or both to the same one, tagged by server name.Choose what gets posted
Under Server → Alerts, decide which events go to Discord and which stay email-only. Reports and critical alerts are the sensible default; everything else quickly becomes noise.
What gets posted
| Event | When |
|---|---|
| Report | Weekly, or daily on Business |
| Critical TPS | When TPS drops below critical-tps |
| Server offline | When the plugin stops posting for longer than the grace period |
| Server back online | When it resumes |
| Security event | Dangerous commands, connection floods, failed logins (plan-dependent) |
Alerts are rate-limited to your plan's maxAlertsPerDay — 10 on Free, unlimited on Pro and
Business. The cap exists so that a server flapping at 3am does not produce 400 messages.
Channel choice
Use a staff-only channel
Alerts name players, and security events include IP addresses. That is not information for a public channel.
A practical setup on a network:
#pulsenode-reports— weekly and daily reports, quiet, readable#pulsenode-alerts— critical TPS and offline alerts, staff-pingable- security events routed to alerts, or to a third private channel if your moderation team is larger than your ops team
Offline detection
The dashboard notices when a server stops posting. What counts as "offline" is a grace period of a few intervals, not a single missed post — a dropped request or a brief network blip should not page anybody.
This is genuinely useful for scheduled restarts too: a restart that takes longer than usual shows up as an offline alert followed by a recovery, with the duration between them.
Removing the integration
Disconnect under Server → Integrations, or remove the bot from your Discord server. Reports fall back to email only; nothing else changes and no data is lost.
Troubleshooting
Nothing arrives. Check that the bot can actually see the channel — a private channel needs the bot's role added explicitly, and Discord will not warn you about it.
Reports arrive but alerts do not. Alerts are configured separately under Server → Alerts, and on the free plan the daily cap of 10 may already be spent.
Duplicate messages. Two PulseNode servers are bound to the same channel and both are posting. That is supported and often intentional — check the server name in the message header before assuming it is a bug.