Salesforce
Salesforce connections give you access to your organization’s customer relationship management data.
Source Setup
Etleap authenticates to Salesforce via OAuth. The connection setup page will forward you to Salesforce to authenticate and authorize the Etleap application.
Required User Permissions
Etleap regularly checks a Salesforce connection’s quota usage by calling the resource limits endpoint. This endpoint requires that both API Enabled and View Setup and Configuration permissions are enabled for the authenticated user. If these permissions are not enabled for your connection, the validation will fail.
What Data is Available?
You can build pipelines from most standard objects from Salesforce.
Etleap also supports extracting custom objects .
In the file picker, custom objects have __c at the end of their name.
The following objects are not supported by Etleap:
- AcceptedEventRelation
- AccountChangeEvent
- AccountContactRoleChangeEvent
- ActivityHistory
- AggregateResult
- AssetChangeEvent
- AttachedContentDocument
- AuthorizationFormConsentChangeEvent
- CampaignChangeEvent
- CampaignMemberChangeEvent
- CampaignMemberStatusChangeEvent
- CaseChangeEvent
- CaseStatus
- CombinedAttachment
- ContactChangeEvent
- ContactPointTypeConsentChangeEvent
- ContentBody
- ContentDocumentLink
- ContentFolderItem
- ContentFolderMember
- ContractChangeEvent
- ContractStatus
- Custom_Object__ChangeEvent
- DatacloudCompany
- DatacloudContact
- DeclinedEventRelation
- EmailMessageChangeEvent
- EmailStatus
- EmailTemplateChangeEvent
- EventChangeEvent
- EventRelationChangeEvent
- FeedLike
- FeedSignal
- FeedTrackedChange
- FieldSecurityClassification
- FolderedContentDocument
- IdeaComment
- IndividualChangeEvent
- LeadChangeEvent
- ListEmailChangeEvent
- LookedUpFromActivity
- MacroChangeEvent
- MacroInstructionChangeEvent
- Many_Fields__ChangeEvent
- Name
- NoteAndAttachment
- OpenActivity
- OpportunityChangeEvent
- OpportunityContactRoleChangeEvent
- OrderChangeEvent
- OrderItemChangeEvent
- OrderStatus
- OwnedContentDocument
- PartnerRole
- PartyConsentChangeEvent
- Pricebook2ChangeEvent
- ProcessInstanceHistory
- Product2ChangeEvent
- QuickTextChangeEvent
- RecentlyViewed
- RecommendationChangeEvent
- SolutionStatus
- TaskChangeEvent
- TaskPriority
- TaskStatus
- UndecidedEventRelation
- UserChangeEvent
- UserProfile
- UserRecordAccess
- Vote
The exact list of objects available for extraction depends on the configuration of your Salesforce Account.
In order to decide which records to extract, Etleap will use the SystemModStamp if present in the object fields.
This will allow us to detect updated to records, as well as inserts, and the result pipelines will be in update mode.
If SystemModStamp is not present, we will use CreatedDate to extract new records only and updates for existing records will not be extracted.
The resultant pipeline will be in append mode.
If none of SystemModStamp or CreatedDate are available, the pipeline will be in replace mode.
This will extract all records of an object in each extraction.
Deleted records
Etleap will extract deleted records from Salesforce for objects that have the SystemModStamp field.
This will delete records in the destination, if the pipeline settings allow this (e.g. the pipeline is not set to retain history).
Archived records
By default, Salesforce does not return archived records when querying tables. Etleap will explicitly request archived records for the following Salesforce objects:
- Task
- Event
Unlike deleted records, archived records will not be removed from the destination.
For all objects, except Task and Event, to remove archived records from your destination, please refresh the pipeline.
Blacklist fields
Salesforce supports blacklisting fields for all objects. Blacklisted fields are never extracted by Etleap. For more information, please see our Field Blacklisting page.
Key Considerations
Quota
To extract data, Etleap uses the Bulk API V2 . Each Salesforce Account has a limit of 10,000 query jobs per day. By default, Etleap will only create 1,000 query jobs a day. Additionally, Etleap will stop extracting once there are fewer than 500 query jobs available for the account, regardless of how many query jobs Etleap created in the day. Extractions will resume once the quota is replenished, at the end of the day.
You can configure the quota allocated to Etleap in the connection page:
You can also view the total quota usage by expanding the connection card on the Connections page .
