Built in 3 commands

Announcements: Set it up

In short

Turn on Announcements, send a first post, schedule one, repeat it, set pings and fix a broken channel.

Pick a channel, write the message and choose when it posts.

1. Turn on Announcements

Open the dashboard, pick the server, then switch on the Scheduled Announcements card on the Services page.

Permissions you and the bot need
  • The bot needs View Channel and Send Messages in every channel it posts to, plus Embed Links for an announcement with embeds.
  • Creating and changing announcements needs Edit on Scheduled Announcements in your dashboard role. Owners have it. Managers have it by default. View is enough to look.
Optional: one-click setup
  • The Setup button on the Announcements page opens the Setup page, where Run Setup does a one-click setup.
  • It looks for an existing #announcements, #announcement or #news channel. An existing channel is left untouched.
  • When none exists, it creates #announcements, readable by everyone and writable only by the bot. It posts a short guide there and pins it when the bot has Pin Messages.
  • You can still pick any channel per announcement.

2. Send one right now

In Discord, run /announce now with a channel and a message. The bot confirms privately and posts the text within about 30 seconds. See /announce now.

Who gets pinged

Role and user mentions ping; @everyone and @here do not. A role is pinged only when it is mentionable or the bot has Mention @everyone, @here and All Roles.

Post a saved announcement now

On the dashboard, Fire now next to a waiting or failed announcement queues it for the next check, so it posts within about 30 seconds. It first asks "Post this announcement now?".

3. Schedule one from the dashboard

On the Announcements page, click + New Announcement, fill in the form and click Schedule.

The form, field by field

You can also click a day on the calendar to start with 09:00 on that date. The form has:

  • Internal label (optional): shown in the dashboard list, never posted.
  • Channel: a text or announcement channel. If the list cannot load, paste the channel ID.
  • Timezone: starts as your Server Timezone (see step 4). Invalid names are rejected.
  • Message: required, up to 2000 characters; Discord markdown works. A Discord preview on the right updates as you type and shows when it fires.
  • Recurrence: "Once (specific date/time)" plus "Send at (in the timezone above)".
  • Embeds (advanced, optional): raw Discord embed JSON, one object or a list of up to 10.

A new announcement is refused while 100 announcements are Pending. Paused ones do not count.

4. Repeat it, in your server's timezone

In Recurrence, pick "Every day", "Weekly (pick weekdays)" or "Monthly (pick day of month)" and set "Time of day (HH:MM, 24-hour)". The Timezone field starts as your Server Timezone.

Repeat rules
  • For monthly, pick a day or "Last day of month". Days past a month's length fall back to its last day.
  • A weekly one saved with no weekday checked runs on Mondays.
  • Two optional bounds: "End date" and "Max occurrences".
  • The first post is the next matching time after you save.
  • If the bot was offline at a slot, that post goes out once when it is back, then the schedule continues.
How the timezone works
  • The Timezone field is pre-filled with the Server timezone from the Server settings tab of the Bot Settings page (UTC until you set one).
  • 09:00 in that zone stays 09:00 through daylight-saving changes.
  • Each announcement keeps the zone it was saved with. Changing the Server Timezone later does not move existing announcements.
  • To switch one, click Edit and change its Timezone. Before you click Save changes, check "Send at" on a one-time announcement or "End date" on a repeating one.

5. Ping roles

In the Message box, write the role as a role mention (<@&ROLE_ID>) and keep "Allow role mentions" checked under Mentions. The preview shows the role's name and colour.

The two Mentions boxes
  • "Allow role mentions" is on by default. With it off, the role name appears but nobody is pinged.
  • "Allow @everyone / @here" is off by default, so a scheduled post cannot mass-ping by accident.
  • User mentions always notify.
Discord's own rule
  • A role is pinged only when it is mentionable or the bot has Mention @everyone, @here and All Roles.
  • @everyone and @here ping only when the bot has that permission in the channel.
  • The Setup check warns about both.

6. Pause, resume or cancel

On the Announcements page, use Pause, Resume or Cancel next to an entry.

What each button does
  • Pause keeps an announcement for later.
  • Resume re-plans a repeating one from now, while a one-time one keeps its date.
  • Cancel asks "Cancel this announcement? This cannot be undone." and ends a repeating series.
The lists on the page

The page groups entries in five lists:

  • Pending: Edit, Fire now, Pause and Cancel.
  • Paused: Edit, Resume and Cancel. It lists up to 100 entries.
  • Recently completed, Cancelled and Failed list up to 25 each.
From Discord

/announce list shows up to 15 waiting announcements, soonest first, each with its number. /announce cancel takes that number.

7. Fix a channel that broke

If an entry shows a CHANNEL DELETED or NO ACCESS tag, click Edit, pick a new channel and save.

Before you save a failed one

Saving the edit re-arms a failed one at its "Send at" time, right away if that time has passed, so check it before you save.

What happens to the post
  • Before each post the bot looks the channel up. If the channel is gone or the bot cannot see it, the post is skipped and the entry gets the tag.
  • A one-time announcement moves to Failed; a repeating one keeps its schedule and skips the broken slot.
  • If the bot can see the channel but cannot post in it, the post is sent and Discord refuses it. The NO ACCESS tag appears afterwards.
Where you are told

While a Pending, Paused or Failed entry carries a tag, a banner says "Some announcements cannot be delivered. The channel was deleted or the bot lost access. Edit the announcement and pick a new channel." The server's owner and managers also get a dashboard notification.

More fixes are on the troubleshooting page.

Was this page helpful?
YourBot docs Reference tables are generated from the code that is running. Ask in Discord