# Scheduling API Workflows Recursively for Emails

**URL:** <https://forum.bubble.io/t/scheduling-api-workflows-recursively-for-emails/125771>\
**Category:** APIs\
**Created:** [December 14, 2020, 11:21pm UTC](https://forum.bubble.io/t/scheduling-api-workflows-recursively-for-emails/125771 "2020-12-14T23:21:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![johnny](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/johnny/32/203020_2.png) [@johnny](https://forum.bubble.io/u/johnny)\
**Post date:** [December 14, 2020, 11:21pm UTC](https://forum.bubble.io/t/scheduling-api-workflows-recursively-for-emails/125771/1 "2020-12-14T23:21:57Z")

</div>

Continuing the discussion from [[New Feature] Scheduling API workflows can now be done recursively](http://forum.bubble.io/t/new-feature-scheduling-api-workflows-can-now-be-done-recursively/37372):

So, I’m trying to schedule a whole load of emails (5,000+) to out my users and want to use recursive scheduled workflows. My brain is processing how I might do this, but don’t know how to actually execute it.

My thoughts:

1. Starting the scheduling of the workflows would be “Do a search for users:first item”
2. In the workflows it’ll run and send the email to the first user in the User Database, then schedule a recursive workflow to go to the next user

I’m stuck on how I can tell Bubble to go to the next user…

Any thoughts? Probably very simple, but my brain hurts thinking about this 😂

---

<div class="post-metadata">

**Author:** ![johnny](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/johnny/32/203020_2.png) [@johnny](https://forum.bubble.io/u/johnny)\
**Post date:** [December 15, 2020, 12:49am UTC](https://forum.bubble.io/t/scheduling-api-workflows-recursively-for-emails/125771/2 "2020-12-15T00:49:23Z")

</div>

Figured out a workaround. Just by creating a new parameter what counts where it is in the list.