In Trello, I've got a "Hold until Date" list. These cards have due dates, so all of the data exists such that something could programmatically watch the cards in that list until the due date has passed, and then move the card in question to the "Inbox" list.
Realizing that API programming is off-topic, services like Zapier exist, and even offer the ability to set open-ended HTTP requests. So I'm wondering if what I'm trying to do is possible within the scope of the existing software, and/or what parts might fall outside that scope and be possible with some amount of API programming.
For starters, I've attempted to set up a Zapier trigger that watches cards in a specific Trello list, and can even filter those cards by due date, however, it's unclear if I can set the criteria for that filter relative to the current date. (i.e. Filter when card due date < current date).
In the even that this is not possible within the scope of Zapier's pre-made Trello integration, is this possible within the scope of Zapier's webhook integrations, or does this start to enter the territory of "rolling my own" application server without the use of Zapier at all?
Best Answer
Using the Trello API, I created a bot that can do exactly what you want (and a lot more). It's been running for a while with very satisfied users (see this reddit thread).
To use it, you invite user "butlerbot" to your board. It will create a list called "Butler" automatically. You enter commands as cards in that list.
The command you want is something like:
on a card's due date, move it to list "Inbox"
This command will move the card at midnight the day it's due. If you prefer a different time, you can specify it:
on a card's due date at 8pm, move it to list "Inbox"
(You may want to set your timezone if you're not in US eastern time, there's a simple command for that too.)
Another alternative:
the day after a card is due, move it to list "Inbox"
This will move it to the list the midnight after its due date.
If you need help using it, there's a public Trello board. The developer (that would be me) is very responsive.