It is not very different in the implementation, so if you understand the api workflow on a list, it wouldn’t take long to create the recursive version.
The difference is in how bubble processes the actions and the affect it would have on your capacity. When doing it recursively each action is triggered only after the previous is completed, therefore your capacity usage is only as great as required to execute one action ( ie. one of the list of things ).
On the other hand the api workflow on a list triggers each action one after another, but not necessarily before the previous was completed…this will have adverse impacts on capacity as bubble may be attempting to process three items simultaneously, putting stress on capacity.
I had an issue with api workflow on a list with capacity and that affected the items being created getting added to a list of things. It also caused my capacity to max out. Things I saw were items getting created out of order ( I had sort orders on each item and they weren’t created in succession ) as well as having items not get added to the list.
Bubble support recommended the api workflow recursive and no issues with it.