How to Send SaaS Lifecycle Emails from Salesforce Flow

Welcome, setup nudge, first-value, credit and win-back emails sent by Flow from the Lead. Every setting, the checks at send time, and a safe sandbox test.

By Published

A SaaS company on Salesforce can send its onboarding and lifecycle email from the Lead record: a welcome, a nudge when setup stalls, a note at first value, credit and plan notices, and a check-in when someone goes quiet.

We drew the steps from a build in a SaaS company's own org. The timings were that org's choices; test your own. If your mail lands in spam, start with the SPF, DKIM and DMARC guide.

Step 1: Put the milestones on the Lead

A flow reacts only to what is on the record. In the org this guide is drawn from, a product sync wrote these fields to each user's Lead.

FieldTypeWhen it is written
Product_User_Id__cText, external ID, uniqueOn create
Lifecycle_Stage__cPicklistFor views and reports; no flow here reads it
Signup_At__c, Connected_At__c, Activated_At__cDate/TimeOnce each
Last_Active_At__cDate/TimeOn each qualifying use
Credits_Left__c, Subscription_Status__cNumber, picklistWhen the balance or plan changes
HasOptedOutOfEmailStandard Email Opt OutBy the unsubscribe link, never by the sync
  • Never clear and reset a milestone. When a time field moves to a future time, Salesforce schedules the path again even if it already ran.
  • Define first value narrowly. Logins, setup checks and failed attempts do not count. An early version in that org counted a listing call, so the first-value email reached people with no result yet.
  • Give merges a fallback. A greeting formula that falls back to "there" keeps an email from opening with "Hi ,".

Step 2: Build one email template per moment

Create Lightning email templates with Related Entity Type set to Lead and keep them in one shared folder, since new templates are private. Merge fields use three braces, as in {{{Recipient.FirstName}}}, and reach custom Lead fields the same way.

Name each template for its moment and order, such as LC Setup Nudge 1, never its timing. That org named templates by timing, and once timings moved, one named for two hours went out at ten minutes.

Write the subject and preview line as a pair. That org put the preview as hidden text at the top of the HTML, added a plain-text version, and ended every email with an unsubscribe link that sets Email Opt Out.

Step 3: Trigger each stage with a record-triggered flow

Create one flow on Lead per milestone that runs when a record is created or updated, optimized for Actions and Related Records. Choose Only when a record is updated to meet the condition requirements, which scheduled paths need here, and an entry formula like this:

Signup flow entry formula
AND(  {!$Record.RecordType.DeveloperName} = "Product_Signup",  NOT(ISBLANK({!$Record.Signup_At__c})),  ISBLANK({!$Record.Connected_At__c}),  ISBLANK({!$Record.Activated_At__c}))

The run-immediately path sends the welcome. Each nudge is a scheduled path timed from the milestone field plus an offset. That org nudged 10 and 43 minutes after signup; 60 minutes, 72 hours and 14 days after setup; and on days 2, 3, 7, 10, 14, 21 and 30 after first value.

Salesforce checks the entry conditions again on every update and cancels pending paths for a record that no longer meets them, so the signup nudges leave the queue once setup is done.

Still start each path with Get Records on the Lead and a Decision, because some reasons to stop sit outside the formula. Branch on a field such as the landing page to pick a version, and skip an email that would land right behind another, as that org did when setup finished within an hour of signup.

For credit and plan notices, run on update and send only when a value crosses a line. The first value written never sends, because its prior value is blank. $Record__Prior is not supported in scheduled paths, so keep this on the immediate path.

Out-of-credits entry formula
AND(  ISCHANGED({!$Record.Credits_Left__c}),  NOT(ISBLANK(PRIORVALUE({!$Record.Credits_Left__c}))),  {!$Record.Credits_Left__c} <= 0,  PRIORVALUE({!$Record.Credits_Left__c}) > 0)

Step 4: Re-check and send from one shared flow

Have every stage flow hand the send to one autolaunched subflow with two inputs, the Lead ID and the template name, so one fix to the opt-out rule reaches every email.

01

The scheduled path reads the Lead again

Get Records by ID, then a Decision.

Check one
02

Still at this stage

If the person moved on, nothing is sent.

03

The shared flow reads the Lead once more

By ID and record type.

Check two
04

Email Opt Out is false

Read at the moment of sending.

05

Find the template and send

Get Records on EmailTemplate by name and folder, then Send Email.

Each call ends as Sent, Skipped or Failed, and the Lead saves either way.

The path every lifecycle email took in the org this guide is drawn from. In the shared flow, the Lead lookup, the template lookups and the send each had a fault path. Source: the org's lifecycle flows, read 19 November 2026.
  • Recipient ID: the Lead ID, required with a template.
  • Email Template ID: from the lookup, because IDs differ between orgs. From version 3.0.1 the action also takes a template name.
  • Sender Type: OrgWideEmailAddress, verified. The running user's profile must be allowed to use that address; on a scheduled path, that is the user who changed the record.
  • Log Email on Send: true, so each send is saved as an email message record.

Re-read Email Opt Out on the Lead in the shared flow immediately before every send, scheduled and queued sends included. The action's documentation does not say it checks the field.

Step 5: Catch people who went quiet with a scheduled flow

A scheduled path is set when a record changes, so it cannot notice that nothing happened. Add a schedule-triggered flow that runs daily on Lead, filtered to Activated_At__c and Last_Active_At__c not null and Email Opt Out false, and hand each send to the shared flow so Email Opt Out is read again at the send.

A Decision sends when Last_Active_At__c falls between now minus 8 days and now minus 7, so each person gets it on the day they cross the line. That org sent a last one at 30 days. A missed daily run skips everyone who crossed a line that day.

These flows run as the Default Workflow User. If one sends email, enter the org-wide address as the Automated Process User Email Address in Process Automation Settings.

Step 6: Make a failed send save the record anyway

The immediate path of a record-triggered flow runs in the save's transaction, and when any operation fails, the whole transaction rolls back. The inquiry auto-reply in that org first shipped without a fault path, and in a sandbox that blocked email no new Lead could be saved.

Draw a fault connector from the Send Email action and each Get Records to an Assignment that stores {!$Flow.FaultMessage} and a Failed status. Salesforce calls a fault path the only way to guarantee an interview does not fail and is not retried.

Then make failures visible. That org kept the message in a variable, which protected the save and left nothing to report on. Salesforce recommends that every fault path email you the resource values.

Step 7: Test in a sandbox without emailing customers

New and refreshed sandboxes start with Access level set to System email only under Deliverability. With No access, a Send Email action that uses a template or logs the email returns an error, which your fault path has to handle.

  1. Move every Lead and Contact email onto the reserved .invalid domain.
  2. Create test Leads on addresses you can read, such as plus addresses on your own domain.
  3. Set Access level to All email for the test window only.
  4. Write each test Lead's fields the way the product would, and read every email on a phone.
  5. Watch Time-Based Automations, or the FLOW_SCHEDULED_PATH_QUEUED event in debug logs.
  6. Opt the test Leads out when you finish, or later emails keep arriving for weeks. Then set Access level back.

Active scheduled flows can run right after a refresh, and the Send Email action does not send while you debug in rollback mode.

Step 8: Measure what was sent, opened, answered and bounced

QuestionWhere Salesforce records it
Sent?An email message record, with Log Email on Send on
Opened?IsOpened and FirstOpenedDate on the email message, with Email Tracking and Enhanced Email on
Bounced?EmailBouncedDate and EmailBouncedReason on the Lead for hard bounces, with bounce management on
Replied?A logged inbound email, if replies are captured
Left?Email Opt Out on the Lead
Worked?The next milestone timestamp

Salesforce calls pixel open tracking imprecise, since mail gateways can trigger it and blocked images hide real opens, so judge each email by the last row. Replies go to the sending address. We have not confirmed how replies to an org-wide address reach Salesforce, so test that before you count the Replied row; if a person's mailbox stands behind the address, look at Einstein Activity Capture.

Every setting on one page

SettingWhere it livesValue in this guide
When to runFlow StartOnly when updated to meet the conditions
Scheduled path Time SourceFlow StartThe milestone field plus an offset
Sender TypeSend EmailOrgWideEmailAddress
Log Email on SendSend EmailTrue
Fault connectorSend Email, each Get RecordsAn Assignment that stores the error
Default Workflow UserProcess Automation SettingsAn active user
Automated Process User Email AddressProcess Automation SettingsThe org-wide address
Access levelDeliverabilityAll email; System email only in sandboxes
Enable Email TrackingActivity SettingsOn
Activate bounce managementDeliverabilityOn

When an email does not send

What you seeLikely cause
A nudge never went outThe Lead stopped meeting the entry conditions
An org-wide address errorThe running user's profile cannot use that address
A new Lead failed to saveA send error with no fault path
Nothing sends in the sandboxAccess level is System email only

Limits, and when you need a marketing platform

  • A Send Email action that uses a template or logs the email counts toward the single email limit: 5,000 external recipients per org per day, by GMT. Developer Edition and trial orgs allow 50 per user.
  • Email alerts also count against a daily allocation of 1,000 per standard user license, up to 2,000,000. Alerts over it are discarded, never resent.
  • Scheduled paths and scheduled flows each allow 250,000 interviews per 24 hours, or 200 times your user licenses if higher.
  • One Send Email action reaches at most 150 recipients.

Compare a marketing platform when you need to email whole audience segments (Salesforce points that job to the Send Email Message element in Marketing Cloud Growth), when volume nears the single email limit, or when the people who change wording and timing should not need flow permissions.

Before you turn it on for every signup

  • Who is already in a state? A flow that fires on a change can email a backlog on the first sync. That org ran its one-time re-sync before turning the flows on, so people with a broken connection were not all emailed at once.
  • How many emails a day is too many? Nothing in these flows caps it.
  • What happens when you edit a flow? Pending paths run under the active version; deactivating cancels them.

Frequently asked questions

Can Salesforce send onboarding emails without a marketing platform?

Yes, for one-to-one lifecycle email. Record-triggered flows with scheduled paths, a daily scheduled flow and the Send Email action cover it, within the single email limit of 5,000 external recipients per org per day.

Does the Flow Send Email action skip Leads who opted out?

Its documentation does not say so, and Salesforce's single email API ignores Email Opt Out by default. Re-read HasOptedOutOfEmail on the Lead in a Decision right before every send.

Why did a scheduled path email never send?

Usually the Lead stopped meeting the entry conditions, which cancels pending paths, or the flow was deactivated. A failed path sends an error email and is retried up to five times.

Official references

GAT Solutions is an independent Salesforce consultancy. Salesforce is a trademark of Salesforce, Inc.

Continue the decision

View all resources →

Free consultation

Building lifecycle email in Salesforce? Tell us where it stands.

Never send us a key or password.

See revenue systems for B2B SaaS

Book a call, or send us what is stuck.

Prefer to talk it through?

Pick a 30-minute time with Gray. Bring the backlog or the thing that broke.

Loading available times…