Before beginning, it's important to understand how Automations function and how their Entry Conditions work. To get started, click here for the first in a series of Automation how-to articles.
There are many reasons for using Repeat Annually in an automation's entry conditions when based on a date. They can include, loan anniversary check-ins, birthday greetings, yearly check-ins and any other event anniversary.
Repeat Annually allows for a single automation to run and then re-run 'on', 'before', or 'after' the anniversary of a date. The most common use for this would be a "Birthday Greeting" automation that would repeat each year on or about their birthday.
The following graphic demonstrates how using Entry Conditions with a Relative Date and Repeat Annually enabled causes the automation repeat actions each year at the same time.
Building the automation Entry Conditions mentioned above is easy.



This only applies to Workflows. Campaigns do not have this conditions.
Repeated date automations will continue to re-run year-after-year. However, there are some things that a user can adjust. Plus some other important items to be aware of.
Removing the automation from a contact:
You can unassign the automation from a specific contact at any time, preventing it from re-triggering in the future.
Disabling the automation entirely:
To cancel the automation for all contacts, you can disable it. This is recommended only if the automation is no longer relevant.
Available for both contact and transaction-based workflow automations:
Repeat Annually can be used with any standard date field in a contact or transaction record.
👍 This concludes how repeat annually work and how to use it
Need more help? Check out: Campaigns vs Workflows