I have an app where a user can send an email to all of his friends, and a copy of the email is sent to the creator.
But the are many emails (the same email many times) arriving to the creator and also many (the same email many times) to the other users. And everytime a creator sends an email to users, the amount of emails arriving is random, one time can be 2 and the other one 5.
The thing is that I am sending the email to a list of users. But instead of sending one email to each user, it sends it many times to the same user. And in my logs, the action is done the same times of the number of users I am sending the email.
For example, if I have to send the email to 5 users (list of users), in my logs, the action is done 5 different times (send email x5).
what action triggers sending the email? is it scheduled api on the list?
the screen you showed (if triggered once) should send ONE email to “espacio’s Creator’s email” and have BCC as list - so everyone on the list will get a copy of it.
you shouldn’t use schedule API on the list. Use just normal scheduled API so the action is triggered once
what you are doing now is triggering the Send Email action depending on the number of BCC people (if the list has 5 people - the action will be triggered 5 times and you want to trigger it only once)
In summary: scheduled API is used for more complex iterations over lists. In your case: if you would want to “personalize” the email content per User you would use Scheduled API on the list. You can’t personalize the email with the use of normal Scheduled API if you have more then 2 users. You should try it
For example, when I want to delete a list of uploaded files I schedule a list with an action to delete a file? But it would do it multiple times because it’s a list?
Well yea you can do that, but you also have “Delate list of things”. If, for example, you wanted to first send the file to the creator email and then delated it then you would use API on the list.
Ohh, okay. So basically the difference between scheduling a normal API workflow and an API workflow on a list is that the API workflow on the list will do the same action for all items on the list until it finishes, right?