1. What is a Flow in Salesforce?
A Flow is an automation tool inside Salesforce that helps you perform actions without manual work. You can use a Flow to update fields, send email alerts, create records, or run background logic whenever something changes in Salesforce.
Think of a Flow as a step‑by‑step set of instructions. When a certain condition is met, Salesforce automatically performs the steps for you.
Why do we use Flows with MassMailer?
MassMailer Flow Alert allows you to send MassMailer emails directly from Salesforce Flows. MassMailer can send emails based on actions happening inside Salesforce. When something changes on a record (for example, new lead created, status updated, or checkbox checked), a Flow can trigger a MassMailer email.
2. What is MassMailer Flow Alert?
MassMailer Flow Alert is a feature that lets Salesforce Flows send emails through MassMailer. Instead of using Salesforce’s native Email Alert, you use a MassMailer Email Alert to:
Send branded emails
Use templates with dynamic merge fields
Track opens, clicks, bounces
MassMailer Flow Alert is added in the Flow as an Action, where you choose which MassMailer template and recipient details to use.
3. How MassMailer Flow Alert Works
A Flow starts when a record is created or updated.
The Flow checks conditions (example: Status = “Active”).
When the condition is true, the Flow uses MassMailer Email Alert.
MassMailer sends the email from the selected template.
You can later track the delivery, open rate, and bounce information.
4. MassMailer Fields – Purpose and When to Use Them
1- Activity Related To ID: It stores the ID of the parent record (such as Account, Opportunity, Case, Campaign, or a Custom Object) where the MassMailer email activity and status should be linked.
It is used to show the MassMailer email activity and status on the Related List and Timeline of the specified parent record.
We support the actual record ID, as well as dynamic values and variables to associate the MassMailer email activity with the relevant parent record
2- Additional To Addresses: It allows you to specify additional recipient email addresses along with the main recipient.
It is used to send the email to extra recipients by entering their email addresses in this field.
We support static email addresses, as well as dynamic values and variables to include additional recipients along with the primary recipient.
3- Additional To Names: It stores the field API name from which additional recipient email addresses should be taken.
It is used when you want to send emails to extra recipients stored in a specific field on the record.
We support static field API names as well as variables to dynamically fetch additional recipient email addresses from the record.
4- CC: It stores the email addresses of people who should receive a copy of the email. Multiple email addresses can be provided as comma-separated values.
It is used to send a visible copy of the email to additional recipients.
We support static email addresses as well as variables to define CC recipients, allowing multiple comma-separated values.
5- BCC: It stores the email addresses of people who should receive the email in BCC. Multiple email addresses can be provided as comma-separated values.
It is used to send a hidden copy of the email to one or more additional recipients.
We support static email addresses as well as variables to define BCC recipients, allowing multiple comma-separated values.
6- Campaign ID: It stores the ID of the Campaign whose members are being targeted for the email.
It is used when sending emails to Campaign Members to identify which Campaign the email belongs to.
We support using the actual Campaign record ID, as well as dynamic values and variables, to identify the Campaign whose members are being targeted.
7- Child Email Field:
It stores the email field API name of the child records from which the recipient email address is picked.
It is used to identify which email field on the child record should be used to send the email.
We support static field API names as well as variables to dynamically determine the email field on the child record.
8- Child Filter Criteria:
It stores the filter conditions used to select which child records from a related list should receive the email.
It is used to ensure that emails are sent only to child records that meet the specified criteria.
We support static filter criteria as well as variables to dynamically determine which child records should receive the email.
9- Child Relationship Name:
It stores the relationship name between the parent object and its child records in Salesforce.
It is used when sending emails from a parent record to identify which child-related list should be used.
We support static relationship names as well as variables to dynamically identify the related child records used for sending emails.
10- File ID: It stores the ID(s) of the Salesforce Files that should be attached to the email.
It is used to send one or more files as attachments along with the email.
We support static File IDs, dynamic values as well as variables to attach one or more Salesforce Files to the email.
11- From Address: It stores the email address of the sender from which the email is sent. (Required)
It is used to define who the email appears to be sent from to the recipient.
We support static email addresses, record field values, and variables to define the sender’s email address.
12- From Name: It stores the name of the individual or entity sending the email. (Required
It is used to define who the email appears to be sent from to the recipient.
We support static values, record field values, and variables to define the sender’s display name.
13- Group Number/Name: It stores the numeric group number or group name of the Email Preference / Unsubscribe Group to which the email belongs.
It is used to associate the email with the correct group for subscription and unsubscribe management.
We support static group numbers or group names, as well as variables to associate the email with the correct group.
14- IP Pool Names: It stores the name(s) of the sending IP pools configured in the email provider (such as SendGrid) that should be used to send the email.
It is used to control which IP pool is used for email delivery and manage sending reputation.
We support static IP pool names as well as variables to control which sending IP pool is used for email delivery.
15- Is Transactional: It stores a boolean value (True/False) to specify whether the email is transactional or non-transactional.
It is used to identify important system or account-related emails (Transactional, such as invoices, password resets, or notifications) versus marketing or promotional emails (Non-Transactional, such as newsletters or campaigns).
We support static boolean values as well as variables to specify whether the email is transactional or non-transactional.
16- MassMailer Group Id: It stores the group id of the MassMailer Unsubscribe Group that the email should be associated with.
It is used to link the email to a specific MassMailer group for subscription and unsubscribe management.
We support static MassMailer Group IDs as well as variables to associate the email with the appropriate Unsubscribe Group.
17- MassMailer List View API Name: It stores the API Name of the MassMailer List View that defines which recipients should receive the email.
It is used to select the audience for the email based on the filters configured in the MassMailer List View.
We support static List View API names as well as variables to dynamically select the audience for the email.
18- Merge Field Record Ids: It stores the Id(s) of the records whose fields will be used as merge fields in the email content.
It is used when the email is sent to one object, but the merge field data needs to come from another related object.
We support static record IDs as well as variables to provide the records used for merge field resolution in the email content.
19- Parent Fields to Link Email Status Events: It stores the field API names from the parent record whose values should be copied into the MassMailer email status or event records.
It is used to make parent record information available on email status events for reporting and filtering purposes.
We support static field API names as well as variables to determine which parent record fields are copied to the email status or event records.
20- Record Id Field: It stores the ID of the triggering record, such as a Lead, Contact, or other standard or custom object. (Required)
It is used to identify the specific record for which the email is being sent.
We support dynamic record references and variables (such as the Flow triggering record ID) to identify the record for which the email is being sent.
21- Reply To: It stores the email address where replies to the email should be sent. (Required).
It is used to define the reply-to address for recipient responses.
We support static email addresses, record field values, and variables to define the reply-to email address for recipient responses.
22- Salesforce Group Id: It stores the Id of the Unsubscribe Group associated with the email.
It is used to link the email to a specific Salesforce group for managing subscriptions and unsubscribe behavior.
We support static Salesforce Group IDs as well as variables to associate the email with the appropriate Unsubscribe Group.
23- Salesforce List View API Name: It stores the API Name of the Salesforce List View that defines the set of records to which the email should be sent.
It is used when sending emails to records selected through an existing Salesforce List View (for example, All Qualified Leads or My Open Contacts).
We support static Salesforce List View API names as well as variables to define the set of records selected for email delivery.
24- Scheduled DateTime: It stores the specific date and time at which the outreach should be executed in the future.
It is used to schedule the email send to run at a later time instead of immediately.
We support static date/time values as well as variables to schedule the email send for a future date and time.
25- Send To Campaign Members: It stores a Boolean value (True/False) to specify whether the email should be sent to Campaign Members.
It is used to send the email to each Campaign Member (Leads or Contacts) associated with the Campaign when it’s true.
We support static boolean values as well as variables to control whether the email is sent to Campaign Members.
26- Sent From Flow: It stores a boolean value (True/False) to indicate whether the email was triggered and sent using a Salesforce Flow. It is used to identify emails that originate from Flow-based automation.
We support static boolean values as well as variables to indicate whether the email was triggered and sent from a Salesforce Flow.
27- Suppress Activity Logging: It stores a Boolean value (True/False) to specify whether Salesforce activity records should be created for the email.
It is used to prevent Email Activity / Activity History entries from being created on related records when set to True.
We support static boolean values as well as variables to control whether Salesforce email activity records are created.
28- Suppress Click Tracking: It stores a Boolean value (True/False) to specify whether link clicks inside the email should be tracked.
When its set to True, then link clicks inside the email are not tracked.
We support static boolean values as well as variables to control whether link clicks inside the email are tracked.
29- Suppress Google Analytics Tracking: It stores a boolean value (True/False) to control whether Google Analytics (UTM) parameters are added to links in the email.
When it's set to True, then the links in the email remain clean without Google Analytics tracking.
We support static boolean values as well as variables to control whether Google Analytics (UTM) tracking parameters are added to email links.
30- Suppress Open Tracking: It stores a Boolean value (True/False) to control whether email open events should be tracked. When open tracking is enabled, MassMailer adds a small invisible tracking element to detect when the recipient opens the email.
When it’s set to True, then email open tracking is disabled, and open events are not recorded.
We support static boolean values as well as variables to control whether email open events are tracke
31- Suppress Subscription Tracking: It stores a Boolean value (True/False) to control whether subscription and unsubscribe rules are applied to this email. Normally, MassMailer checks the recipient’s email preferences and subscription status before sending the email.
When it is set to True, then MassMailer ignores subscription and unsubscribe rules and sends the email regardless of the recipient’s preferences.
32- Suppressed Email Status Values: It stores a list of email status values for which MassMailer should not create or log email status events, such as Delivered, Opened, Clicked, or Bounced.
When specific status values are provided, MassMailer ignores those events and does not create email status records for them.
We support static boolean values as well as variables to control whether subscription and unsubscribe rules are applied when sending the email.
33- Target Campaign Members Status: It stores the Campaign Member status value(s) used to determine which Campaign Members should receive the email.
When specified, the email is sent only to Campaign Members whose status matches the provided value(s).
We support static Campaign Member status values such as New, Click, Invalid, Sent, and Delivered, as well as variables, to determine which Campaign Members should receive the email.
34- Template API Name: It stores the API Name of the email template that should be used for sending the email. It is used to identify which MassMailer email template will be applied when the email is sent.(Required).
It supports both static API names, record field values, and variables to identify the email template that should be used when sending the email.
35- Template ID: It stores the ID of the email template that should be used for sending the email. (Required)
It is used as an alternative to Template API Name, and only one of them (Template API Name or Template ID) should be provided.
It support static Template IDs, record field values, and variables to define the email template used for sending the email.
36- Timezone Value: It stores the time zone that should be used when processing date and time values for the email.
It is used to ensure that dates and times displayed in the email are accurate for the intended audience or business context.
We support static time zone values, record field values, and variables to determine the time zone used for processing date and time values in the email.
37- To Address: It stores the email address of the primary recipient to whom the email is sent. (Required)
It is used to specify the main recipient of the email.
We support static email addresses, record field values, dynamic values, and variables to define the primary recipient of the email.
38- To Name: It stores the display name of the recipient to whom the email is being sent. (Required)
It is used to show the recipient’s name in the email details.
We support static values, record field values, dynamic values, and variables to define the recipient’s display name.
5. Example: Simple Flow Using MassMailer Email Alert
Below is a basic example you can publish.
Scenario: When a Lead becomes “Qualified”, send a welcome email.
Create a Record-Triggered Flow on Lead.
Trigger when Status = Qualified.
Add an Action → MassMailer Email Alert.
Fill fields:
Template Name: Welcome Email
Recipient Object: Lead
Recipient Email: Lead.Email
Sender Email: support@company.com
Track Opens: True
Save & activate the Flow.
Now every time a Lead becomes Qualified, the welcome email is automatically sent.
6. Best Practices
Always test with your own email before enabling the Flow.
Avoid sending multiple emails from multiple flows for the same action.
Use a naming standard: Flow_Lead_WelcomeEmail.
Keep templates stored in one central folder.
Use tracking fields to monitor performance.