I have been struggling with how to do this using Zapier Tables
I want to flag when a task is past the due date, due today or due after a certain number of days.
I want to trigger a zap that changes the value in a drop down menu so it will move to a different column in the kanban form I’m building.
Originally I tried creating a zap that triggered when a record was updated and I was going to use paths based on what the formula value was. BUT none of my test runs recognized the new values.
Please let me know if there is a better way to do this. (The AI has absolutely useless for anything other than “create these 10 fields”
Best answer
How to trigger a Zap when a formula field is updated in Zapier Tables
- Beginner
Best answer by aiappsapi
Worth adding one thing for this specific case, since the due date logic is time based rather than edit based.
A formula that compares the due date to today only changes because the clock moved, and nothing wrote to the record when that happened. Updated Record triggers fire on a write, so a task that quietly becomes overdue at midnight will not trigger anything until someone edits that row by hand.
The reliable pattern for the overdue side is a Schedule by Zapier trigger running once a day, then a find or search step over the table filtered on the date field, then the dropdown update. Keep the formula field for display in the Kanban view, and let the scheduled Zap be the thing that actually moves the record.
Anything driven by a real edit, like a status change, works exactly as Fahad described.
- Zapier Solution Partner
Hi
You can try this approach:
Step 1: Click the name of your formula field in your Zapier Table (the one that calculates due dates)
Step 2: Select "+ Create Zap" from the menu that appears
Step 3: A new Zap opens up with the trigger already set to watch specifically that formula field
Step 4: Now add your action to update the dropdown menu that controls your Kanban column
The trigger will be set up as an "Updated Record" trigger, but it'll have your formula field pre-selected in the configuration. So it's using the same trigger name, just configured differently .
Documentation:
Hope this helps you get it sorted!
+11- Community Manager
Glad Fahad was able to point you in the right direction
- Beginner
+11- Community Manager
That’s so nice to hear
Worth adding one thing for this specific case, since the due date logic is time based rather than edit based.
A formula that compares the due date to today only changes because the clock moved, and nothing wrote to the record when that happened. Updated Record triggers fire on a write, so a task that quietly becomes overdue at midnight will not trigger anything until someone edits that row by hand.
The reliable pattern for the overdue side is a Schedule by Zapier trigger running once a day, then a find or search step over the table filtered on the date field, then the dropdown update. Keep the formula field for display in the Kanban view, and let the scheduled Zap be the thing that actually moves the record.
Anything driven by a real edit, like a status change, works exactly as Fahad described.
+11- Community Manager
Thanks for chiming in here
If you have, then it might be worth switching to aiappsapi's suggested approach. Alternatively, perhaps you could set up a view where a record shows up when the due date is today (or past due) and then trigger the Zap from new records that land in that view.
ZapConnect 2026 is coming
Join us September 23rd, 2026 for a free, one-day virtual event with 30+ sessions on AI automation. Get live build-alongs, playbooks, and strategies to lead AI transformation at your organization.
Log in to the Community
No account yet? Create an account
Use your Zapier credentials
Log in with ZapierEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.