Summary
This article explains which Salesforce objects &Open uses to power campaign workflows, what we read or write on each object, and why. Use this as a reference for data flows between &Open and your Salesforce org.
This Article expands Adding custom Contact fields to SFDC to capture gifting activity that describes how to get started in SFDC adding custom fields and the initial setup of those.
List of objects
CampaignMemberStatus
What we do
Read and write
Why it’s needed
Allows creation and use of clear, useful statuses for members associated with a campaign.
Fields we write
Label
CampaignId
HasResponded
Fields we read
Id
Label
IsDefault
HasResponded
CampaignMember
What we do
Read and write
Why it’s needed
Provides the attributes required to create a gift request and keep member status in sync.
Fields we write
Status
Fields we read
Id
CampaignId
Type
FirstName
LastName
Country
City
State
Email
LeadOrContactId
EmailMessage
What we do
Write
Why it’s needed
Creates email records for all messages sent as part of a campaign.
Idempotency
We use upsert with a unique MessageIdentifier so duplicate requests never create duplicate records.
Fields we write
RelatedToId
FromAddress
FromName
Subject
HtmlBody
Incoming
IsClientManaged
MessageDate
MessageIdentifier
Status
ToIds
Note: Data security and minimal access
We limit access to only the fields required for the campaign features described above.
Where we write to Salesforce, we do so with clear, auditable events and idempotency safeguards.
Support
If you have questions about how this integrates with your specific Salesforce setup, contact your &Open representative and we’ll help review configuration and permissions.
Would you like me to:
Add more objects if you have them listed elsewhere
Adjust wording to match Intercom’s tone or your brand voice
Trim the technical field lists and keep only “What we do” and “Why it’s needed” for a lighter customer version
Related reading
See also: Further details and FAQs