Freshping Discord integration: how to get the alerts back

If you search for a Freshping Discord integration today, you land on pages for a tool that no longer exists. Freshworks shut Freshping down on March 6, 2026. The monitors stopped, and the alerts that used to ping your team stopped with them.

This post covers three things: what Freshping's integrations really were, how to rebuild the same alert in Discord in about ten minutes, and what to check before you pick a replacement. We make Uptrack, so we show our own setup first and say where it is not the right choice.

What happened to Freshping

Freshworks said that supporting Freshping was no longer part of its plan and ended the product. As third parties quote the notice, the no-cost tier ended on March 6, 2026, and paid plans were not renewed after that date and ran until they expired. Freshworks kept the data for 90 days after the shutdown. Users of the no-cost tier had until about June 4, 2026 to export, so that window is closed now. We could not load Freshworks' own notice. The dates come from a shutdown guide by Notifier and from a forum thread that quotes the notice. Freshworks has given no sign that Freshping is coming back.

The practical result: you have to rebuild your monitors somewhere else. The export is gone, so write down your URLs from your status page, your DNS records or your deploy notes before you forget them.

What "Freshping integrations" meant

Freshping had no public integration page that we could find. Third-party guides describe three ways to get an alert out: email, Slack, and a webhook field under Settings, Integrations. Automation marketplaces such as Zapier also list Microsoft Teams and Discord among the places a Freshping alert could go.

That matters because the phrase "Freshping Discord integration" suggests a built-in button. We found no sign of one. Teams that had Freshping alerts in Discord almost certainly used the webhook field or an automation tool in between. If that was you, you only need the same thing again: a monitor, a rule that says "alert after a failed check", and a Discord channel that can receive it.

Option 1: Discord alerts with Uptrack, step by step

The free plan checks 5 monitors every 30 seconds from one location (Nuremberg). It includes email plus one chat channel: Discord, Slack or Telegram. The free plan needs a work email address. Paid plans accept any email address.

1. Create a free account and add your first monitor. Use the URL you used in Freshping.
2. Open Alerts in the dashboard and press Connect Discord. Uptrack sends you to Discord, where you pick the server and the channel. Discord creates an incoming webhook for that channel, and Uptrack stores it as an alert channel. You never copy a URL.
3. Prefer to do it by hand? In Discord, open the channel settings, then Integrations, then Webhooks, and create a new webhook. Copy its URL. In Uptrack, add an alert channel of type Discord and paste the URL. It must start with https://discord.com/api/webhooks/. Discord's intro to webhooks shows the menus, which can change.
4. Attach the channel to your monitors. A down alert and a recovery alert both go to it.

The alert is a Discord embed, not a plain line of text. Down alerts are red, recoveries are green, and a degraded warning is yellow. The fields show the monitor name, the URL, the status, when it started, how many checks failed and, when we know it, the reason: a TLS failure, a 503, a timeout. A link opens the incident. A recovery reads "is back UP" with the time it resolved.

If you later delete the webhook in Discord, Discord answers that it is unknown. Uptrack stops retrying, disables that channel after repeated fatal failures, and emails the account owner, so a deleted channel does not fail in silence.

Option 2: any monitoring tool with a webhook

You can keep another tool and still read its alerts in Discord. The catch is the message shape. Discord's execute webhook endpoint wants a JSON body with at least one of content, embeds, components, a file or a poll. A monitoring tool that posts its own JSON, with fields like monitor and status, will be rejected or show nothing useful.

So there are two routes:

• Use a tool that has a Discord channel type, as above. This is the simplest, and nothing sits between your monitor and the channel.
• Put a relay in between. An automation tool or a ten-line script receives the tool's webhook and posts to Discord. A minimal post looks like this:

curl -X POST "$DISCORD_WEBHOOK_URL" \
  -H "Content-Type: application/json" \
  -d '{"content": "api.example.com is DOWN (503)"}'

Know the limits before you build on it. A message body is capped at 2,000 characters, one message can carry up to 10 embeds, and a webhook can send 30 messages per minute. A flapping monitor behind a relay can hit that last limit during a real outage, which is when you most need the alerts. Alert confirmation, where several failed checks are needed before a message goes out, protects both your channel and your sleep.

How the free options compare

All numbers come from each vendor's public pricing page, checked on October 12, 2026. We have not tested the Discord alerts of the other tools, so open their integration lists before you move. Our own UptimeRobot comparison and the Freshping alternatives page go deeper.

Freshping's own free plan monitored 50 URLs at 1-minute intervals, as third-party listings describe it. None of the options above matches both numbers on a free plan. Pick the one that fits what you give up more easily: monitor count or check speed.

Move your monitors without losing a day

1. List every URL you monitored. Include health endpoints, not only the home page.
2. Create the monitors in the new tool at the same interval, or faster. Note which ones need a keyword check, not only a status code.
3. Connect Discord and attach the channel to every monitor.
4. Test the whole path once. Point a temporary monitor at a URL that returns 404 on purpose, wait for the alert, then delete the monitor. You will see the real message format and learn whether the channel works.
5. Decide who reads the Discord channel at night. A channel nobody watches is a log, not an alert.

When Uptrack is not for you

• You need many free monitors. UptimeRobot's free plan has 50 and HetrixTools has 15. Ours has 5.
• You need SMS or phone-call alerts on the free plan. Webhook, SMS and phone alerts are on Pro.
• You want more than one chat channel on the free plan. Free has one: Discord, Slack or Telegram. Use email for the second route.
• You signed up with an address on a free mail provider and want the free plan. The free plan needs a work email address. You can add a work email address to your account in Settings, or choose a paid plan, which accepts any email address.

FAQ