Triggering SFMC Journeys from Salesforce CRM Events

When Sales Cloud marks an Opportunity as "Closed Won," the customer should immediately receive the first email in an onboarding series. No marketing team middleman. No nightly export job.

That's exactly what Salesforce Entry Source in Journey Builder is for - trigger the Journey when a CRM record matches a filter.

Configuration

In Journey Builder, create a new Journey, choose Salesforce as the Entry Source:

When any Opportunity's Stage changes to Closed Won, SFMC receives the event via MC Connect, resolves the associated Contact via the lookup, and adds the Contact to the Journey.

That Contact then flows through the Journey's Send Email, Wait, and Decision Split steps like any other subscriber.

Common triggers by Salesforce Cloud

Sales Cloud

Service Cloud

Experience Cloud (Community)

Each of these is a standard pattern we've shipped on engagements. The trigger object and filter change; the Journey structure is roughly the same.

Two mistakes that bite first-time builders

Mistake 1: Forgetting the Contact lookup path

The trigger object might be Opportunity or Lead - not always Contact directly. Journey Builder needs to resolve the subscriber's email, so there must be a path from the trigger object to a Contact with an Email field.

Opportunity -> Primary Contact -> Email. Lead -> Email is direct. Case -> Contact -> Email.

Forgetting to configure the lookup leaves the Journey with no target subscriber. Behavior varies: sometimes Journey sends nothing, sometimes it errors, rarely is the message obvious.

Mistake 2: Re-entry on CRM state churn

Opportunity flips between Closed Won and Reopened multiple times (common during contract negotiations). Each time it hits Closed Won, the Contact re-enters the Journey and receives the onboarding series again.

Fix: Journey Settings > Contact Entry Mode > No Re-entry. Set this before launch. Once the Contact has entered this Journey, re-triggering doesn't add them again.

Exception: if the Journey is designed to repeat (annual renewal reminder), you want Re-entry on - but that's a deliberate choice, not a default.

What the CRM user sees

Salesforce CRM users don't interact with Journey Builder directly. The flow looks like:

1. Sales rep marks the Opportunity as Closed Won.
2. MC Connect fires the event to SFMC.
3. Journey Builder adds the Contact.
4. Customer receives the first onboarding email within minutes.

From the sales rep's perspective, it "just happens" - no additional action required.

Testing before going live

Always test in a Salesforce sandbox connected to an SFMC sandbox/non-production BU:

Only after the full sandbox cycle passes is it safe to flip to production.

Takeaway

Triggering from CRM events is the key integration pattern MC Connect unlocks. Configure the trigger object + filter + Contact lookup carefully, set No Re-entry unless repetition is intentional, and test every edge case in sandbox before production. Once wired, Sales and Service teams get automated customer communication without any new process to learn.

---

Building CRM-triggered Journeys? Our Salesforce team configures Salesforce Entry Sources, Journey logic, and sandbox testing on production engagements. Get in touch ->

See our full platform services for the stack we cover.