Recurring Birthday Reminders in Slack: What Works Each Year?

Slack documents repeating reminders for days and weeks, but annual birthdays need a checked fallback. Compare one-off reminders, a recurring calendar event, and a birthday app.

By Kelasa team · October 28, 2026

A birthday comes around once a year. Slack's published reminder examples cover daily, weekly and monthly repeats, but the current reminder help page does not document an annual /remind pattern. Don't rely on every year without checking what Slack actually schedules in your workspace. For a dependable annual date, use a calendar event set to repeat yearly, or maintain one-off Slack reminders and renew them after each birthday.[1][2][3]

Why a recurring birthday reminder is different

A weekly reminder can say “review the birthday list” every Monday; it cannot by itself know whose birthday falls on which date. A personal reminder nudges the coordinator, while a channel reminder posts its description to the channel. Neither stores consent preferences or maintains a roster of birthdays for you.[1] If you only need a one-time prompt, our step-by-step Slack birthday reminder guide covers the basic /remind flow.

Before choosing a method, ask teammates whether they want their birthday shared. A private month-and-day list may be sufficient; avoid collecting birth years unless your process actually requires them. Assign an owner who will remove dates when someone opts out or leaves.

What Slack says about repeating reminders

Slack documents day-based repeats such as every Monday; its reminder examples also show every weekday, every two weeks and the first day of every month.[1][2] These are examples of supported phrasing, not confirmation of yearly recurrence. We have not tested an annual command in a Slack workspace, and the cited Slack documentation does not establish that it works.

If you experiment with a yearly phrase, treat it as an experiment: inspect Slackbot's confirmation and /remind list, and verify the next occurrence before depending on it. A phrase being accepted is not enough if it resolves to the wrong year or date. Slack says reminders without a specified time default to 9 a.m. in your Slack time zone; specify a time and check the result if timing matters.[1]

Option 1: Use one-off Slack reminders

For a handful of consenting teammates, create a personal reminder for the next birthday date, then replace it after it fires. For example, adapt this illustrative command to your teammate and date:

/remind me "Prepare Alex's birthday greeting" on March 14 at 9am

Read the confirmation to ensure Slack interpreted the year and time as intended. Put a separate yearly calendar appointment on your own calendar to renew the Slack reminder if this is the process you choose. Keep the actual birthday list access-restricted and don't post a name to a shared channel without permission. This is a manual method: when the owner changes, somebody must hand over the list and outstanding reminders.

Option 2: Use a yearly calendar event

Google's recurring-event instructions describe opening Google Calendar on a computer, creating an event, choosing Does not repeat, selecting the repeat frequency, and saving it.[3] Set up a private event for each opted-in birthday and choose a yearly repeat in the calendar's available options. Add an advance notification if you want time to prepare a greeting. Check the next occurrence, especially for a February 29 birthday: agree on whether to celebrate it on February 28, March 1, or only on leap years.

You can also connect Google Calendar for Slack, which documents personal event notifications and configurable channel notifications.[4] This requires installing and configuring a separate calendar app; it is not a native Slack birthday recurrence feature. Keep the calendar private by default, review which event details a channel notification would expose, and test the notification settings in your own workspace before relying on them. A calendar notification is a prompt, not a personalized birthday message.

Option 3: Evaluate a dedicated birthday app

An app may suit a team that wants a recurring celebration process without a coordinator recreating reminders. Compare its date collection, opt-out handling, destination channel, time zone, and duplicate-post safeguards against your actual requirements. Do not assume that every birthday app handles weekend birthdays or leap days in the way your team prefers.

Kelasa's BirthdayBot overview describes a daily celebration digest in Slack. That page is an overview, not a promise of a specific annual /remind command or a particular weekend-shifting policy. Confirm the current setup and controls before changing your team's workflow. For ideas on keeping celebrations welcome rather than obligatory, read our guide to celebrating birthdays in Slack.

Avoid missed or duplicate greetings

Keep one source of truth: Record each consenting person's month and day, the chosen announcement channel, and who owns the process.
Check time zones: Decide which team's local date determines the celebration. Slack's default reminder time follows the setter's Slack time zone.[1]
Write down a weekend policy: Celebrate on the date itself, the preceding Friday, or the next workday; don't mix policies without telling the team.
Track what was sent: If a calendar prompt and a Slack reminder both fire, designate one person to send the greeting and mark it done.
Recheck changes: Review the next scheduled date after a calendar edit, a Slack time-zone change, or a coordinator handoff.

FAQ

Can I use `/remind ... every year` for a birthday?

The Slack sources cited here do not document that syntax. We have not verified it hands-on. If you try it, inspect both the confirmation and next occurrence; use a yearly calendar event or one-off reminder as a fallback.[1][2][3]

Does a recurring Slack reminder send a birthday greeting automatically?

A personal reminder prompts you to act. A channel reminder posts the text you entered to that channel, but does not maintain a birthday list or decide whether someone has opted in.[1]

What if the birthday is February 29?

Choose an explicit non-leap-year policy with the person concerned and verify the next scheduled occurrence in whichever tool you use. Do not assume a calendar or bot will pick your team's preferred substitute date.