Overview

MassMailer supports automated email delivery to child records from a parent object by using an Apex action within Salesforce Flow Builder. This approach enables organizations to configure scalable, event-driven email automation directly inside Salesforce.

By invoking the Email via MassMailer Apex action from a flow, administrators can send emails to related child records based on parent-level events, record updates, or business process triggers.

Functional Architecture

This implementation combines three components:

  • Parent Object – Source record that triggers the flow

  • Child Records – Related records containing recipient email fields

  • MassMailer Apex Action – Executes email delivery through Flow Builder

When a qualifying event occurs on the parent object, Flow Builder invokes the MassMailer Apex action, retrieves related child records through the defined relationship, and sends emails using the configured template and sender settings.

Supported Use Cases

This configuration is useful for:

  • Sending notifications to contacts related to an account

  • Triggering email alerts to child custom object records

  • Automating communication based on parent record updates

  • Executing scalable outreach in approval or service workflows

MassMailer supports both standard and custom Salesforce objects for this process.

How the Apex Action Works

MassMailer provides an Apex-based action that can be called directly from Salesforce Flow Builder. The action allows users to define sender information, relationship logic, and email template references.

Required Input Parameters

The following parameters are typically required:

  • From Name

  • From Address

  • Child Email Field

  • Child Relationship Name

  • Template ID or Template API Name

  • Record ID Field

These parameters determine the sender identity, identify the related child records, and define which template should be used during email generation.

Configuration Flow

Step 1: Open Salesforce Flow Builder

Create or edit a flow based on the required trigger type, such as:

  • Record-triggered flow

  • Scheduled flow

  • Autolaunched flow

Step 2: Define the Parent Object Trigger

Configure the flow to start when a specific event occurs on the parent object.

Step 3: Add MassMailer Apex Action

Insert the Email via MassMailer Apex action into the flow.

Step 4: Map Required Inputs

Populate the required parameters, including:

  • Sender information

  • Child relationship name

  • Child email field

  • Template reference

  • Parent record ID field

Step 5: Save and Activate the Flow

Validate the configuration and activate the flow for execution.

Technical Considerations

  • Ensure the child object contains a valid email field

  • Verify the relationship name between parent and child objects

  • Confirm template availability and API name correctness

  • Validate user permissions for flow execution and MassMailer access

  • Test the automation in a sandbox before production deployment

Accurate field mapping and relationship configuration are critical for successful execution.

Benefits

Using Flow Builder with MassMailer Apex action provides:

  • Automated email delivery from parent-driven events

  • Reusable email automation logic

  • Support for standard and custom objects

  • Scalable communication to multiple related records

  • Centralized workflow management within Salesforce

Conclusion

Triggering emails to child records from a parent object in MassMailer through Salesforce Flow Builder is a practical method for automating record-based communication. By leveraging the Email via MassMailer Apex action, organizations can build flexible workflows that improve responsiveness, reduce manual effort, and support large-scale communication use cases within Salesforce.

For more information, you can refer to the blog post.