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
Send Email: "Invitation to Annual Event"
-> Wait: 3 days
-> Engagement Split: Did the subscriber click "Confirm attendance"?
-> Yes:
-> Salesforce Activity: Update Contact
Field: Event_RSVP__c = "Confirmed"
-> Send Email: "RSVP confirmed - see you there!"
-> No:
-> Send Email: "Reminder: Event in 3 days"
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
Subscriber unsubscribes in SFMC
-> Salesforce Activity: Update Contact
Field: Email_Opt_Out__c = true
-> Sales rep sees the opt-out in CRM, stops cold-emailing
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
Subscriber finishes the onboarding Journey
-> Salesforce Activity: Create Task
Subject: "Follow up with new customer - onboarding complete"
Assigned To: Owner of Contact
-> Sales rep receives a CRM task reminder
Turns marketing automation into a trigger for sales follow-up without needing a separate rev-ops integration.
Score updates
Subscriber interacts strongly (open + click + specific CTA)
-> Salesforce Activity: Update Lead
Field: Lead_Score__c += 10
-> Lead qualification pipeline moves them forward
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:
[ ] Open Salesforce Setup
[ ] Find the MC Connect Integration User (typically called "Marketing Cloud")
[ ] Check profile/permission set for the object and field in question
[ ] Add permissions if missing
[ ] Re-test the Activity
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:
Journey Entry: Lead
-> Wait until Stage changes
-> Check: Has the Lead been converted to a Contact?
-> Yes: Salesforce Activity targeting the Contact (not the Lead)
-> No: Salesforce Activity targeting the Lead
Determine which object to update dynamically based on current state.
Testing in sandbox
Before production, test every Salesforce Activity in a Salesforce sandbox:
[ ] Permission check: does the Integration User have edit access?
[ ] Field exists: the target field is on the object in the sandbox too?
[ ] Valid value: the value you're writing matches the field's type and picklist options?
[ ] End-to-end flow: trigger the Journey, observe the Contact record, confirm the field flipped?
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.
