---
title: "Send recurring reminders"
description: "Timesheets every Friday to one country, a yearly compliance nudge with a button people must click, and a monthly newsletter in a channel: automations on a timetable that enrol the right people each run, without anyone pressing send."
sidebar:
  order: 5
area: use-cases
appPath: /flows/home
lastVerified: 2026-11-15
version: "2026-10-23"
audience: admin
related:
  - flows/automations/configure-a-recurring-trigger
  - flows/automations/set-the-audience
  - directory/employee-groups/create-a-filter-group
  - directory/employee-groups/how-audiences-match
  - use-cases/policy-acknowledgement
---

A timesheet reminder lands every Friday afternoon for the people in one country, compliance training is chased each year until the button is clicked, and the company newsletter goes out on the first of the month, all from automations that run on a timetable and enrol the right people on each tick. **For:** admins and owners. **Time:** about 20 minutes per automation, plus the filter groups.

![The finished reminder: a weekly Recurring Trigger on Fridays in the London time zone, its next runs listed under it, and one email step on the day.](https://support.pyn.ai/media/use-cases/recurring-reminders/use-cases-recurring-reminders-trigger.png)

## What you'll need

- A filter group per audience, for example current employees in **Country: United Kingdom**, or a department; see [Create a filter group](https://support.pyn.ai/directory/employee-groups/create-a-filter-group/).
- An email sender, or Slack connected for direct messages; see [Add an email sender](https://support.pyn.ai/settings/senders/add-an-email-sender/) and [Slack](https://support.pyn.ai/integrations/slack/).
- For a compliance nudge, the training link, or the policy published in **Library** > **Content**; see [Content](https://support.pyn.ai/library/content/).
- For a newsletter in a channel, **Pyn Bot** invited to the channel in Slack, and a **Post to Channel** step, where enabled for your workspace.

## Build it

1. Create a filter group for each audience and read who matched on the **Confirm Filter Group** page before confirming; see [Create a filter group](https://support.pyn.ai/directory/employee-groups/create-a-filter-group/).

2. Create an automation with the **Recurring Trigger**, set **Starting from Date (Inclusive)** to the first Friday, **Time** to 15:00, **In Time Zone** to the country's zone and **Recurrence** to **Weekly**, then read the list of upcoming runs under it; see [Configure a recurring trigger](https://support.pyn.ai/flows/automations/configure-a-recurring-trigger/).

3. Before publishing, open **Audience**, keep **Lifecycle** at **Current** and add the filter group under **Included**, then read the **Audience Preview** count; see [Set the audience for an automation](https://support.pyn.ai/flows/automations/set-the-audience/).

4. Add a **Send Email to Employee** or **Send Direct Message** step to **Employee**, scheduled **on the day of** at a time after the trigger's, with **Weekdays Only** kept under **Days of Week**; see [Schedule a step](https://support.pyn.ai/flows/steps/schedule-a-step/).

5. For compliance, add a **Link Button** with **Track Action** ticked and up to three reminders, for example **3 days after send** and **7 days after send**; see [Add a button to a message](https://support.pyn.ai/flows/steps/add-a-button-to-a-message/) and [Add reminders](https://support.pyn.ai/flows/steps/add-reminders/).

6. For a newsletter, add a **Post to Channel** step to the company channel, where enabled for your workspace, on a trigger whose **Recurrence** is **Monthly**; see [Post to a channel](https://support.pyn.ai/flows/steps/post-to-a-channel/).

7. Publish, leave the first run in **Verification** so it waits in **Needs Review**, then move to **Automated**; see [Publish an automation](https://support.pyn.ai/flows/automations/publish-an-automation/) and [Change the mode of an automation](https://support.pyn.ai/flows/automations/change-the-mode/).

## Variations

**Slack**

A **Send Direct Message** from **Pyn Bot** suits a timesheet nudge; the button renders as a Slack button and the click marks the delivery **Actioned**. The newsletter is a **Post to Channel** step, where enabled for your workspace: one post per run from a sender who is in the channel, with no reminders because anyone in the channel can act on it.

**Email**

A **Send Email to Employee** step with **From** set to the payroll or People mailbox, as in [Choose a sender](https://support.pyn.ai/flows/steps/choose-a-sender/), so a reply reaches whoever approves timesheets.

For several countries, build one automation per country group, each with its trigger in that country's time zone so 15:00 means 15:00 locally. One automation with the countries combined under **Included** and a country group on each step's **Audience** tab also works, as in [Set a step audience](https://support.pyn.ai/flows/steps/set-a-step-audience/), but every run then uses one time zone.

## Watch out for

- The default audience enrols every current employee on every run, so set it before the first publish; see [Configure a recurring trigger](https://support.pyn.ai/flows/automations/configure-a-recurring-trigger/).
- A 09:00 run creates its enrollments within the hour after 09:00; a step **on the day of** at 09:00 is then already due and sends at once, while one at 10:00 waits for 10:00. The trigger keeps local time across daylight saving in the zone you pick.
- Included groups with the same parent combine with OR and different parents with AND, and a filter or static group is a condition of its own, so including two filter groups means "in both"; see [How audiences match](https://support.pyn.ai/directory/employee-groups/how-audiences-match/).
- Reminders hold back only on a step with a tracked button; on a plain reminder every reminder sends, and a form answered inside Slack does not mark the step actioned either; see [Add reminders](https://support.pyn.ai/flows/steps/add-reminders/).
- The trigger's **Prevent repeat enrollments** is **1 day**, so a daily schedule still enrols each person once a day; see [Prevent repeat enrollments](https://support.pyn.ai/flows/automations/prevent-repeat-enrollments/).

## Check it worked

After the first run, [Enrollments](https://support.pyn.ai/activity/enrollments/) lists one row per audience member with the run date as **Reference**, and every later run adds a new set, so the list grows by the audience size each time. In **Verification** the first set waits in **Needs Review**; see [Review and unpause enrollments](https://support.pyn.ai/activity/enrollments/review-and-unpause-enrollments/). The step appears under [Messages](https://support.pyn.ai/activity/messages/) with its recipients and date, and for the compliance nudge [Track actions](https://support.pyn.ai/activity/actions/track-actions/) lists who is still **Unactioned**, with a CSV to chase from.

## Related

- [Configure a recurring trigger](https://support.pyn.ai/flows/automations/configure-a-recurring-trigger/) for the start date, time, zone and recurrence.
- [Set the audience for an automation](https://support.pyn.ai/flows/automations/set-the-audience/) to decide who each run reaches.
- [Create a filter group](https://support.pyn.ai/directory/employee-groups/create-a-filter-group/) to save a country or department audience once.
- [How audiences match](https://support.pyn.ai/directory/employee-groups/how-audiences-match/) for the OR and AND rules.
- [Get a policy acknowledged](https://support.pyn.ai/use-cases/policy-acknowledgement/) for a compliance ask chased until the button is clicked.
