Updating Salesforce CRM from SFMC Email Actions

A client we worked with ran an annual event and sent invitations through SFMC. When customers clicked "Confirm attendance" in the email, the client wanted the Event_RSVP__c field on the CRM Contact to flip to "Confirmed" automatically. Sales reps looking at Contacts in Salesforce would see the RSVP status without marketing needing to generate a spreadsheet.

This is Salesforce Activity inside Journey Builder. No custom integration, no webhook, no developer work on the Salesforce side beyond making sure the field exists.

The canvas

Salesforce Activity is a standard Activity type in Journey Builder. Drop it on the canvas, configure the object + field + value.

Additional use cases we've shipped

Sync unsubscribe back to CRM

Important compliance win. Without this, sales continues cold-emailing someone who explicitly opted out. That's a real legal risk and an uncomfortable conversation.

Create follow-up tasks

Turns marketing automation into a trigger for sales follow-up without needing a separate rev-ops integration.

Score updates

Permissions: the usual cause of failures

Salesforce Activity runs through the MC Connect Integration User in the Salesforce CRM. That user account must have permission to:

• Read the object (to find the record)
• Edit the field being updated
• Create records of the type being created (for Create Task / Create Contact actions)

When Salesforce Activity fails with permission errors:

Permission issues are the most common failure mode on first setup. The error message usually points at the object but not the specific permission missing.

The Lead vs Contact trap

Salesforce has both Lead and Contact objects. When a Lead converts, the data moves to a Contact. Journeys triggered from Lead objects that try to update Lead fields after conversion will fail - the Lead record is gone.

Pattern we use to handle this:

Determine which object to update dynamically based on current state.

Testing in sandbox

Before production, test every Salesforce Activity in a Salesforce sandbox:

Don't trust "it should work" for a Journey Activity that writes to CRM. Test the full loop.

Takeaway

Salesforce Activity closes the loop between email engagement and CRM state. Unsubscribes flow back, event RSVPs show up on Contacts, sales tasks get created automatically. Permissions on the MC Connect Integration User are the most common failure mode - check them first. Sandbox-test every new Activity before production so the first production run isn't the bug report.

---

Building SFMC-to-CRM write-back flows? Our Salesforce team configures Salesforce Activities, Integration User permissions, and bidirectional data flows on production engagements. Get in touch ->

See our full platform services for the stack we cover.