Skip to main content

Understanding the 'Days Ago' Condition in Workflows (CRM)

Understanding the 'Days Ago' Condition in Workflows (CRM)

Overview

The Days Ago condition in Dazos workflows is designed to match a date field to a specific number of days in the past. This article explains how the condition works, what it can and cannot do, and clarifies a common point of confusion around matching dates to today.

When to Use This Condition

Use the Days Ago condition when you want a workflow to trigger based on how long ago a date field occurred. A common example is triggering a follow-up workflow exactly 3 days after a patient's Admission Date.

How the 'Days Ago' Condition Works

When adding a condition to a workflow using a date field (such as Admission Date), you can select Days Ago as the operator. This allows you to match the date field to a specific number of days in the past relative to the current date.

For example, setting Admission DateDays Ago3 will match records where the Admission Date is exactly 3 days ago.

  • Days Ago — matches records where the date field is exactly that many days in the past

  • Less Than Days Ago — matches records where the date field is within the last X days

  • More Than Days Ago — matches records where the date field is older than X days ago

The Days Ago operator (without a range qualifier) is the appropriate choice when you need an exact day match, such as exactly 3 days ago.

Known Limitation: 'Today' Is Not Available as a Date Field

While Days Ago can be used with date fields like Admission Date, there is no Today date field available in workflow conditions. This means you cannot configure a condition that matches a date to exactly today using a direct field reference.

If you need to match a date to the current day, refer to the workaround article linked in the Related Resources section below.

Tips & Notes

⚠️ Important: The Days Ago condition is a workflow condition, not an action. It controls when the workflow triggers — it does not calculate or update a field value.

💡 Tip: If you are unsure which operator to use, open an individual record to view the available date fields and their labels. This helps ensure your condition references the correct field name.

Best Practice: Test your workflow with a sample record after configuring the Days Ago condition to confirm it triggers as expected before rolling it out to your full dataset.

Related Resources

  • Using Logic-Based Conditions in Reporting and Workflows (CRM)

  • How to Create a Workaround for Required Task Date Fields Using a Custom Today Field

  • How to Sync Date Fields Between Module Tabs Using Workflows (CRM)

  • How to Configure Workflows to Trigger Only Once Instead of on Every Record Update (CRM)

Did this answer your question?