There's a couple of things to understand about repeater fields in order to see what's required to do what you are asking. Although they are called repeater fields, they are actually embedded forms, just as is the address field. With repeaters, every time you add or remove a row, you are adding or deleting an entry for the embedded form. Each row in a repeater is its own form entry. When you add form fields to a repeater during your design phase, you are actually building the repeater form that is used to capture the entry data. When you click the submit button on the primary form, Formidable processes all embedded forms first to build the linkages to the parent entry/field. This means that to send emails to everyone entered through a repeater row, you must gather the email addresses from each of the repeater form's entries. This requires custom code. You can fire this custom code in the frm_after_create_entry hook or another hook that fires before the email action. I don't know what that hook might be right now. I don't have time to research it. But, because I know how friendly Formidable is to developers, there's probably a hook somewhere you can exploit that makes sense for your particular use case. If you need help with development, please feel free to search through our Formidable Developers Directory at https://formidable-masterminds.com/developers-directory/