{"id":259,"date":"2026-06-30T11:39:12","date_gmt":"2026-06-30T11:39:12","guid":{"rendered":"https:\/\/peoplewisher.com\/blog\/?p=259"},"modified":"2026-06-30T11:39:13","modified_gmt":"2026-06-30T11:39:13","slug":"birthday-announcements-slack-teams","status":"publish","type":"post","link":"https:\/\/peoplewisher.com\/blog\/birthday-announcements-slack-teams\/","title":{"rendered":"How to Automate Team Birthday Announcements in Slack and Teams"},"content":{"rendered":"\n

A tactical guide to internal culture automation, getting birthday and anniversary announcements posting automatically into your team’s Slack or Microsoft Teams channels via webhooks and API.<\/p>\n\n\n\n

Why automate birthday announcements specifically in Slack or Teams<\/h2>\n\n\n\n

Most teams already live in Slack or Teams for daily communication, which makes it the natural place for birthday recognition to actually be seen far more reliably than an email that might go unread in a busy inbox. A birthday announcement posted in a public team channel also does something an individual message can’t: it invites colleagues to add their own reactions, emoji, and replies, turning a single automated message into a small moment of team connection.<\/p>\n\n\n\n

The goal of this kind of automation isn’t to replace personal recognition it’s to make sure the recognition happens consistently, every time, without relying on someone remembering to post it manually.<\/p>\n\n\n\n

Two ways to set this up<\/h2>\n\n\n\n

There are two general approaches, depending on your technical resources:<\/p>\n\n\n\n

Option A: Build it yourself<\/strong> using a webhook and a script or no-code automation tool (Zapier, Pabbly Connect, or a custom script).<\/p>\n\n\n\n

Option B: Connect a dedicated birthday automation platform<\/strong> that already handles the date logic and just needs a webhook URL to post into.<\/p>\n\n\n\n

Most HR and People teams find Option B faster to set up and easier to maintain, since the date-checking, timezone handling, and message formatting logic is already built, you’re just plugging in the destination. This guide covers both.<\/p>\n\n\n\n

Option A: DIY setup with a webhook<\/h2>\n\n\n\n

Step 1: Create an incoming webhook in Slack or Teams<\/h3>\n\n\n\n

In Slack, go to your workspace’s App settings and create an “Incoming Webhook” for the channel you want announcements posted to, this gives you a unique URL that accepts POST requests with a JSON payload. In Microsoft Teams, you create a similar “Incoming Webhook” connector from the target channel’s connector settings.<\/p>\n\n\n\n

Step 2: Store employee birthdays in a structured source<\/h3>\n\n\n\n

This can be a spreadsheet, a database, or your HRIS export, what matters is that it has a consistent date format and is kept current as employees join or leave.<\/p>\n\n\n\n

Step 3: Write a daily script or automation that checks dates<\/h3>\n\n\n\n

Using a no-code tool like Zapier or Pabbly Connect, or a custom script (commonly Google Apps Script if your data lives in Sheets), build a daily trigger that checks whether today’s date matches any employee’s birthday or anniversary, and if so, sends a formatted POST request to your webhook URL.<\/p>\n\n\n\n

Step 4: Format the message payload<\/h3>\n\n\n\n

Slack and Teams both expect a JSON payload with the message text and optional formatting (Slack supports “blocks” for richer formatting, including images and buttons; Teams uses “MessageCard” or Adaptive Card format). A simple example for Slack:<\/p>\n\n\n\n

{\n  \"text\": \"\ud83c\udf89 It's *Jordan's* birthday today! Drop a wish in the thread \ud83c\udf82\"\n}\n<\/code><\/pre>\n\n\n\n
Step 5: Test and monitor<\/h3>\n\n\n\n
Run a manual test by temporarily setting a test date to today’s date, confirm the message posts correctly, and then monitor the first few real sends closely, date logic bugs (especially around leap years or month\/day ordering) are a common source of silent failures.<\/p>\n\n\n\n
Limitation of the DIY approach:<\/strong> this requires ongoing maintenance, doesn’t easily support employee opt-out preferences, and breaks silently if the underlying script or Zap fails without anyone noticing, which means a missed announcement is often only caught after the fact.<\/p>\n\n\n\n
Option B: Using a dedicated birthday automation platform<\/h2>\n\n\n\n
PeopleWisher<\/a> and similar dedicated tools handle the date-checking and scheduling logic natively, so the setup is reduced to a few steps:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
    \n
  1. Import employee data<\/strong> (name, birthday, hire date) via CSV or API\/HRIS sync<\/li>\n\n\n\n
  2. Connect your Slack or Teams webhook URL<\/strong> in the platform’s integration settings<\/li>\n\n\n\n
  3. Write your announcement template<\/strong>, with placeholders for name and any custom message<\/li>\n\n\n\n
  4. Set per-employee opt-out preferences<\/strong>, so employees who don’t want a public announcement are automatically excluded from the channel post while still receiving a private message if desired<\/li>\n\n\n\n
  5. Activate<\/strong>, the platform handles daily checking, timezone considerations for distributed teams, and reliable delivery with monitoring<\/li>\n<\/ol>\n\n\n\n
    This approach trades a small amount of setup flexibility for significantly less ongoing maintenance and built-in handling of edge cases (leave of absence, opt-outs, milestone years) that a DIY script typically doesn’t account for.<\/p>\n\n\n\n
    DIY vs dedicated platform comparison<\/h2>\n\n\n\n
    Factor<\/th>DIY (Zapier\/script + webhook)<\/th>Dedicated platform (PeopleWisher)<\/th><\/tr><\/thead>
    Setup time<\/td>Several hours, technical<\/td>Minutes<\/td><\/tr>
    Ongoing maintenance<\/td>Required scripts can break silently<\/td>Minimal<\/td><\/tr>
    Employee opt-out support<\/td>Manual, easy to miss<\/td>Built-in<\/td><\/tr>
    Milestone year detection<\/td>Manual logic required<\/td>Automatic<\/td><\/tr>
    Multi-channel (email + Slack)<\/td>Requires separate setup per channel<\/td>Single workflow<\/td><\/tr>
    Cost<\/td>Often free, but time-intensive<\/td>Free tier available, paid plans scale<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    Writing announcements that feel genuine, not robotic<\/h2>\n\n\n\n
    A few practical tips for the announcement copy itself:<\/p>\n\n\n\n