Can't filter tasks by inactivity or overdue status in workflows
Hey community/team,
I'm trying to set up a workflow that acts as a reminder system, but I’ve hit a limitation:
I want to filter tasks that haven’t been updated in the last 3 days – basically untouched tasks – or tasks where the due date has passed. This would trigger a reminder email, which is super helpful for following up.
But the issue is: the time-based filters in workflows only accept absolute dates, not relative ones like "older than 3 days" or "due date is before today".
This makes it pretty much impossible to build dynamic reminders without constantly updating the filters manually 😕 Would love to see support for relative date filters (e.g. "last updated > 3 days ago") in the workflow builder.
Anyone else run into this?
7 Replies
Hey @thomast when you have some free time could you please give this a look 🙏
Hi @Marvin Erkes, indeed this is not implemented yet. This should be done in the coming weeks. If you need it now, you could still add a Code step that filter the tasks
Thank you @thomast . Can you post a few example code steps? Not yet sure how to code these.
This is definetely a feature that someone in sales cannot live without 😂
Hey @BigKahuna filters mode aka conditions node are coming during next quarter ! Will let you know updated
Here is my current workflow code function that I did over the weekend.
Right now I did not find a way to do:
- HTML Email body
- Multiple emails to different users (need one workflow for each users, iach..)
- Assignee not populated on task
- Assigne ID filter on API
- Search Records is giving all items as output (just first, last, count)
@thomast Maybe you could give some advice on the current approach
- HTML Email body => not possible today but probably for this quarter
- Multiple emails to different users => this quarter as well, we want to implement a Loop step
- Assignee not populated on task => should already work. What's your issue?
- Assigne ID filter on API => should work as well. You try to filter through frontend and look for the
findManyTaskscall that is made
- Search Records is giving all items as output => only returns one item until we implement the loops I talked before. Once done, we'll allow to fetch multiple items. Today workflows do not handle arrays properly