Triggered When a Date Arrives: Automating Recurring Tasks & Conditional Actions Based on Specific Dates

Date-triggered automations in monday.com can automatically create recurring tasks, send deadline reminders, and update project statuses when specific dates arrive. However, while the native "When a date arrives" trigger handles basic scenarios well, it has significant limitations around formula-calculated dates, relative timing, and timeline column integration that often force users to seek custom solutions.

What Does "When a Date Arrives" Actually Do?

Monday.com's native date trigger fires automations when a date column reaches a specific date. You can set it to trigger at a predetermined time (like 9 AM) and combine it with status conditions for more complex workflows. The automation runs according to the timezone of whoever sets it up, not the viewer's timezone.

This works perfectly for straightforward scenarios: sending a reminder when a project deadline arrives, changing a task status when a follow-up date is reached, or creating the next item in a recurring sequence. You can find pre-made templates under the Dates tab in your board's Automations page.

The key limitation is that these automations trigger at fixed times you select during setup, not at the actual time stored in the date column. If your date column shows "March 15, 2026 at 3:30 PM," the automation still fires at whatever time you configured (like 9 AM), not at 3:30 PM.

How to Set Up Recurring Tasks with Date Automations

Creating recurring tasks involves using the "When a date arrives" trigger combined with a "Duplicate this item" action. You set the automation to run daily, weekly, or monthly, and monday.com creates new instances of your template item on schedule.

The process is straightforward: select your template item, set up the date trigger for when you want the next instance created, and configure the duplication action. The new item inherits all the column values from the original, including any default dates you've set.

However, this approach breaks down when you need relative dates. For example, if you want every new weekly report to be due "this Friday" regardless of when it's created, native automations can't calculate that dynamically. Each new item gets the same fixed due date from the template.

Why Formula-Calculated Dates Don't Trigger Automations

One of the most frequently requested features in the monday.com community is the ability to trigger automations based on formula-calculated dates. Users consistently run into this limitation when trying to automate workflows that depend on date calculations.

For instance, you might have a formula that calculates "Start Date + 14 days" to determine when a follow-up is needed. Even though this creates a valid date, you cannot use it as a trigger for automations. The "When a date arrives" trigger only recognizes manually entered dates, not calculated ones.

This forces users into workarounds like creating separate date columns and manually copying formula results, or using external integration tools. For complex project workflows involving multiple calculated milestones, this becomes a significant operational burden.

Community Cookbook's Formula Column Change Trigger addresses this gap by monitoring formula columns for changes and can trigger actions when calculated dates are reached, enabling the automated workflows that native triggers cannot support.

Timeline Columns and Date Automation Challenges

Timeline columns present special challenges for date-based automations. While you can trigger automations when a timeline's end date arrives, you cannot natively trigger automations on timeline start dates without custom solutions.

This limitation affects project management workflows where you want to automatically notify team members when project phases begin, or update statuses when work periods start. The asymmetry between start and end date triggers creates gaps in timeline-based automation strategies.

Additionally, timeline columns don't work well with the relative date calculations that many project workflows require. If you want to automatically set milestone dates based on project start dates, you'll need to use separate date columns and complex formula arrangements rather than leveraging timeline functionality directly.

The Sync Parent Dates from Subitem Timelines recipe helps bridge this gap by enabling parent items to automatically reflect the date ranges of their subitems' timelines.

Timezone Gotchas for Global Teams

Date automations run according to the timezone of whoever creates them, not the viewer's timezone. This can create confusion for distributed teams where the automation creator is in New York but team members are in London or Tokyo.

If you set up an automation to run at 9 AM Eastern Time, it will always run at 9 AM ET, regardless of where your teammates are located. This means your London colleagues might receive their "morning standup" reminders at 2 PM local time.

For global teams, it's important to choose automation times that work across your primary timezones, or create separate automations for different regions. Unfortunately, monday.com doesn't provide per-user timezone customization for automations.

Relative Date Scheduling That Native Automations Can't Handle

Many workflow requirements involve relative date calculations that go beyond what native automations support. Users frequently need automations that can:

• Set due dates to "the Friday after creation" regardless of creation day
• Schedule follow-ups for "2 business days after status change"
• Create cascading deadlines working backwards from a final event date
• Trigger reminders at item-specific time offsets (2 hours before the appointment time in the date column)

These scenarios require dynamic date calculations that consider the current date, business day logic, or item-specific timing. Native automations work with fixed dates and predetermined times, making these workflows impossible without custom solutions.

The automating date calculations guide explores how formula columns combined with custom triggers can enable these sophisticated date workflows.

Combining Date Triggers with Status Conditions

You can create more sophisticated workflows by combining date triggers with status conditions. For example, "When deadline arrives AND status is still 'Working on it', then send urgent reminder." This prevents notifications for already-completed items.

These conditional combinations work well for project monitoring, where you want different actions based on item status when dates arrive. However, you're still limited to the status values that exist when you create the automation—you can't dynamically adjust conditions based on changing business rules.

Anniversary Dates and Annual Recurring Workflows

Setting up annually recurring automations based on specific dates (like contract renewal dates or employee anniversary reminders) requires careful planning with native automations. You need to manually update the target dates each year, or create workarounds using recurring monthly checks.

Users often struggle with anniversary-style automations because monday.com's recurring triggers work on fixed schedules (daily, weekly, monthly) rather than annual cycles tied to specific dates. Creating a "birthday reminder" system that checks anniversary dates throughout the year requires either 365 separate automations or complex external integrations.

When to Use Custom Date Triggers Instead

Community Cookbook's custom date triggers fill critical gaps in monday.com's native capabilities. Consider custom solutions when you need:

• Automations triggered by formula-calculated dates
• Relative date offsets based on item data (not fixed schedules)
• Timeline start date triggers
• Business day calculations in date workflows
• Item-specific timing (triggering at the time stored in the date column, not a fixed time)

The Formula Column Threshold Trigger can monitor date calculations and fire when calculated dates cross specific thresholds, enabling deadline-based workflows that adapt to changing project timelines.

Real-World Date Automation Workflows

Effective date automation workflows often combine multiple triggers and conditions:

Project Milestone Tracking: Use timeline end dates to trigger status updates, with conditional logic based on completion percentage. When phase deadlines arrive, automatically update project status and notify stakeholders if work isn't complete.

Client Follow-up Sequences: Create recurring tasks for client outreach, with due dates calculated relative to last contact date. This requires formula columns to calculate next contact dates and custom triggers to act on those calculations.

Event Planning Cascades: Work backwards from event dates to automatically set preparation deadlines. A wedding planner might need vendor confirmations 30 days before, venue setup 7 days before, and day-of coordination starting 2 hours before event time.

These scenarios demonstrate why sophisticated date automation often requires combining native monday.com features with custom solutions that can handle the complex date logic that real businesses need.

Frequently Asked Questions

Can I trigger an automation based on a formula-calculated date rather than a manually entered date?+

Why don't my date automations trigger at the time shown in my date column?+

How can I create recurring tasks with due dates that are relative to creation date?+

Can I set up anniversary reminders that repeat annually based on a date field?+

Why can't I trigger automations on timeline column start dates?+

Do date automations respect different timezones for team members?+