Backend Workflow & Dates

Hi Bubblers, I’ve tried for quite some time to figure this out myself and reading through the forum but haven’t been able to come across the solution (apologies if it is hidden in plain site).

I am building a training database for my company and want to be able to send an email when the expiry date (a field on the training record) is within 60 days of the current date / time.

The only solution I can see is that when the record is created, an API is scheduled on that specific record to send the email when it is 60 days out from the original expiry. However, I thought there may be a simpler solution that just monitors the database and will email as the record gets to that date (similar to a change in database trigger).

Any help or advice would be extremely appreciated.

you could set a daily recurring workflow to check for records where expiry date > current date round down to date and expiry date is < current date rounded down to date + 1 day

this will match records from midnight to midnight for a 24 hr period

Thank you!! Great idea, do you know how to set it to do that? This is what I’ve done based on what you mentioned… Not sure if this is right?

Below is the API workflow trigger

This triggers a API workflow on a list that then sends an email using this info data? Or is it much simpler than that?

Also - if this is done daily, will it send an email every single day until they update it (just thinking that may be annoying for people, perhaps the rule needs to be = -60 days, instead of greater than as it would send every day I assume until they change that?

you need to use a 24 hr time window like I mentioned above

greater than and less than combined

you can’t use = unless you store the dates as midnight and then compare them to a date at midnight

normally I set a make.com scenario to ping the backend workflow daily. I just find that the easiest way to do it.

1 Like

Don’t do a daily recurring event…it is a waste of WUs and unnecessary. Your first thought to schedule is the correct thought so do that. And if you think for some reason the date might change after creation ensure you save original scheduled workflows I’d and cancel it when scheduling new expiration date workflow.

Thanks @boston85719 . Curious to know what the difference in WUs would be, is it quite significant. Looking for a simple solution, and thought running on a list would be better - if WUs are higher daily, perhaps this should be just once a month sent out.

Difference would be the cost of searching everyday versus not plus some more WU consumption costs like triggering actions

1 Like

Thank you @boston85719 and @mitchbaylis , I’ll play around with the two options to see what works best. Appreciate both our feedback.