Summer ’25 adds flexibility to Flow’s Send Email action — you can compose email content directly in the action or select an existing email template by name.
Overview
With Salesforce Summer ’25, the Send Email action in Flow Builder gains two convenient options: compose the email body and subject directly inside the action, or choose a prebuilt email template from a dropdown by name (no template ID required). Both approaches support merge fields and rich text formatting so emails can match your company’s branding without extra text template resources.
What changed
The Send Email action previously relied heavily on separate text templates or required passing email template IDs into flows. Summer ’25 simplifies this by letting admins and builders:
- Write and format the email subject and body directly within the Send Email element (merge fields supported).
- Select an existing email template by name from a dropdown — no need to find or store the template ID in the flow.
Benefits and use cases
- Faster authoring: build simple notifications directly in the flow without creating a separate resource.
- Consistency: use email templates managed centrally and reference them by name for standardized messaging.
- Branding: include formatted text and company styles when composing within the Send Email action.
- Maintenance: easier to update templates outside flows while keeping flows clean when choosing templates by name.
Quick tips
- Use the compose option for ad-hoc or flow-specific messages that won’t be reused elsewhere.
- Choose templates by name when you need consistent messaging across multiple flows and teams.
- Always test merge fields and formatting in a sandbox before deploying to production.
References
Related Summer ’25 release notes: Compose or select email template in Send Email action (Release Notes)
Why this matters
This change reduces friction for admins and flow builders by consolidating email creation into the flow editor or by simplifying template selection. For admins and developers, it means fewer resources to manage and quicker delivery of automated communications. For business users, messages are more consistent and branding is easier to maintain.
Key takeaways:
- Compose in-flow for quick, one-off emails.
- Select templates by name for standardization and easier maintenance.
- Test merge fields and formatting before releasing.
Why it matters for Salesforce roles: Admins can iterate faster, developers spend less time wiring template IDs, and business users get consistent, branded communications.