You would think so, but this (scheduling a recursive workflow on an API-returned list ) is surprisingly difficult to do from what I can see. It is down to what Keith has dubbed the API Ghetto.
In other to do a recursive workflow, you need to be able to pass the list back to the workflow after each run but you’re kind of stuck since the workflow cannot take a list returned by an API as a parameter. Unless I’m missing something (and I do want to spend some more time on this over this weekend) you’re left with scheduling the workflow on a list as your only option. It is very frustrating, given that this option, even by the Bubble team’s own admission, is not the most reliable.