Skip to main content
A weekly devlog, a monthly recap, a countdown to launch. Write the message once, set a cadence, and let it post itself. Every recurring schedule runs for a fixed number of sends and then finishes.

​
What you need first

  • A Discord server connected under Integrations.
  • A plan that includes recurring announcements. On Free and Indie every announcement is one-time.

​
The playbook

1

Create a recurring announcement

Open Announcements in the sidebar and click New announcement. Choose the Recurring card, click Continue, and name it.
2

Set the opening schedule

Choose how often it Repeats, the day and Time of day, the Timezone, and the Number of sends. Click Save Draft.

Setting a recurrence

Every schedule setting, and the plan bounds.
3

Write the message

On the Compose tab, write the Content, set the Appearance and Links, and pick the Channel on the Audience card. This one message is what posts each time.

Composing the message

Every field in the composer.
4

Adjust the schedule if needed

On the About tab, open the Schedule to fine-tune the cadence or the number of sends before you commit.
5

Publish it

Click Publish. Read the first-send time and the number of sends it reserves, then confirm.

Publishing an announcement

How recurring sends are reserved up front.

​
How you know it worked

  • The announcement badge reads Published.
  • The Messages tab shows the next send in blue and the upcoming occurrences in amber.
  • After the last send, the badge moves to Completed.

Setting a recurrence

The reference for cadence and send counts.

Stop a recurring announcement

Playbook: pause to edit, or let it finish.

Track your announcement messages

Playbook: retry a failure, skip an occurrence.

Plans and limits

Recurring availability, cadence, and caps by plan.