Alerts
Which alerts
In Settings → Alerts tick the kinds you want: Failed, Missed, Late, Odd data and Back to OK. A recovery email says how long the job was broken.
Email, chat apps and webhook
Alerts go to your email and to the extra addresses of each job (Edit → Also alert, at most 10). Each extra address first gets an email with a confirmation link and receives alerts only after it is confirmed; until then the job page shows it as pending. In Settings → Alerts → Channels → Also send to … you can add Slack, Microsoft Teams, Discord, Google Chat, ntfy and a generic webhook (we POST a small JSON). They get the same alerts as your email: right away or once a day, reminders, and “machine seems down”. Only https addresses on the public internet are accepted. If one of them fails, the others still get the alert.
To check them all, click Send test alert under Settings → Alerts → Channels: a message marked “[TaskBeacon] Test alert” goes to your email and every channel, and the page says which ones got it (at most 5 tests an hour).
Slack
Slack receives alerts through an incoming webhook of a small Slack app of your own. Go to api.slack.com/apps, create an app (From scratch) in your workspace, open Incoming Webhooks and turn on Activate Incoming Webhooks. Press Add New Webhook (Slack calls it Add New Webhook to Workspace), pick the channel and allow it. Copy the webhook URL (https://hooks.slack.com/services/…) and paste it in Settings → Alerts → Slack. Each alert arrives as a message with the subject in bold.
Microsoft Teams
Teams receives alerts through its Workflows app (the old Office 365 connectors were retired in 2026). In Teams open the channel's … menu → Workflows, pick the template Send webhook alerts to a channel, save it and copy the webhook link. Paste it in Settings → Alerts → Teams. Each alert arrives as a card with a button to the job.
Discord
In Discord: Server Settings → Integrations → Create Webhook (pick the channel) → Copy Webhook URL, and paste it in Settings → Alerts → Discord. Alerts arrive as a message from that webhook, without @mentions.
Google Chat
Incoming webhooks need a Google Workspace Business or Enterprise account whose admin allows them (not a personal Gmail account). In the space open its menu (the arrow next to its name) → Apps & integrations → Add webhooks, name it, copy its address and paste it in Settings → Alerts → Google Chat.
ntfy (push to your phone)
ntfy is a free, open-source push service. Install the ntfy app, subscribe to a topic with a long, hard-to-guess
name and paste https://ntfy.sh/<topic> (or only the topic name) in Settings → Alerts → ntfy. Problems arrive with high
priority, recoveries with normal priority; tapping one opens the job. Topics on ntfy.sh are public to anyone who knows the name; with your own ntfy server use its address instead.
Webhook (JSON)
For your own code, Zapier, Make or n8n: paste an https address in Settings → Alerts → Webhook. On every alert we send a
POST with Content-Type: application/json. A status change looks like this:
{"status": "failed", "old_status": "ok", "at": "2026-11-08T06:02:11.512+00:00",
"url": "https://taskbeacon.io/jobs/42/", "job": "Sales report", "job_id": 42,
"subject": "[TaskBeacon] Sales report failed"}
status: the new status (failed,missed,late,odd,ok;newfor a job that never pinged);old_status: the one before.at: when the alert was sent, ISO 8601 in UTC.url: the job's page.subject: the email subject.- Reminders have
"reminder": true; the “keeps changing status” alert has"flapping": trueandchanges; the one-time “has not pinged yet” alert has"never_pinged": true. These have noold_status. - A whole machine:
{"machine": "SRV-01", "status": "down", "jobs": [names], "at": …, "subject": …}. - Once a day:
{"alerts": [{"job": …, "status": …, "at": …}], "subject": …}. - The test alert from Settings:
{"test": true, "status": "test", "at": …, "url": …, "subject": "[TaskBeacon] Test alert"}.
Any 2xx answer counts as delivered; redirects are not followed.
What a Failed alert shows
The error the script sent, its exit code (or Stata's r() code), and the last lines of output when the code
sends them (the code from the Code tab does that for Python, R, Stata, Node.js, PowerShell and Batch). The same lines are on the job page,
under the Fail event.
Limits that protect your inbox
When a job keeps switching between broken and OK (6 changes in an hour), you get one “keeps changing status” alert and no more alerts for that job for an hour. An account sends at most 200 alert emails a day; when that is reached you get one notice and the other channels (Slack, Teams, Discord …) keep working.
Right away or once a day
Choose Right away (with an optional reminder every N hours while the job stays broken; on Free at most every 6 hours, see Pricing) or Once a day at a set time, which sends one email only when something happened.
Don't send alerts turns alerts off completely: no email, chat or webhook, right away or once a day, and no reminders. Status changes are still recorded in History, and the kinds you ticked are kept, so choosing Right away again brings them back. The regular report is set separately.
One job without alerts: open the job, press Edit and untick Send alerts for this job. The job is still watched, changes status and shows in History and the reports, but sends no email, chat message or webhook, and no reminders. Jobs and the job page mark it with “alerts off” so it is not forgotten.
The regular report
A summary of all jobs on the days you tick (tick all seven for every day), weekly or monthly, even when all is fine.
No-alert days
Holidays: in Settings → Alerts → No-alert days add a period and press Save changes. Nothing is planned, nothing counts as Missed and no alerts go out.
A whole machine goes quiet
When every job of one machine is missed or late at once, you get one alert for the machine instead of one per job. A job with alerts off is not listed in it and never starts one.
Use cases: Task Scheduler can't send email any more: get an alert when a task fails · Find out when a scheduled job didn't run at all · SQL Server Agent job failure alerts without Database Mail · Power BI refresh failure notifications for the whole team · Get an alert when a file doesn't arrive in SharePoint by 8:00 · Get an alert before an SSL certificate or domain expires · Get an alert when a website is down or slow. More questions: FAQ.