Summer ’25 adds the ability to pass collections of email addresses into the Send Email action’s CC and BCC fields in Flow Builder — making multi-recipient automation much simpler.
Summary
What changed
With the Summer ’25 release, the Flow Builder “Send Email” action now accepts collections (lists) of email addresses for the CC and BCC recipient fields. This lets you add multiple CC and BCC recipients dynamically from record fields, related records, or variables without concatenating strings or creating custom Apex.
Key benefits
- Send to multiple CC/BCC recipients directly from Flows using collections.
- Reduce reliance on Apex or external processing to build recipient lists.
- Enable dynamic recipient resolution from related records (e.g., contact lists, account team members).
Quick usage notes
- Create or collect email address collections as Text Collection variables in your Flow.
- Map those collection variables to the Send Email action’s CC and/or BCC fields.
- Validate or deduplicate addresses before calling the action to avoid bounces or duplicates.
Example screenshot
References
Best practices & considerations
- Always validate email formats before adding to the collection.
- Watch org email sending limits and compliance rules when sending to large lists.
- Consider logging sent emails as EmailMessage or Activity if auditability is needed.
Use cases
- Sending notifications to account teams or related contacts pulled dynamically from the database.
- Notifying multiple stakeholders (CC) and keeping managers informed via BCC without exposing addresses.
- Automated reports or alerts where recipients are stored on related records.
Why this matters: Flow is increasingly the primary automation surface for admins. Allowing CC and BCC collections directly in the Send Email action reduces complexity, removes the need for custom code for many scenarios, and speeds up delivery of multi-recipient notifications.
For Salesforce admins and developers, this small change simplifies common automation patterns — especially where recipient lists are stored in related objects. Business users benefit from faster delivery of targeted communications without developer intervention.