​
Authentication

Endgame authenticates users via Salesforce OAuth. This allows for a seamless and secure user experience by leveraging Salesforce’s robust authentication framework.

​
Connected App Approval

Approving a Connected App in Salesforce requires the Customize Application AND either the Modify All Data OR Manage Connected Apps permissions.
Salesforce requires an approval process for Connected Apps, which needs to be completed before Endgame can receive data. After going through the initial OAuth handshake, navigate to Setup -> Connected Apps -> Connected Apps OAuth Usage and click Install next to the EndgameLabs2 app.

​
(Optional) API Integration User

Endgame accesses data using the Bulk API 2.0 APIs, so the initial connection can be done with a dedicated API Integration user. In salesforce user creation, select:
  • User License: Salesforce Integration
  • Profile: Minimum Access - API Only Integrations
Use the integration user for the initial connection to Endgame.

​
Data ingestion

Endgame leverages the Bulk API 2.0 fetch data from Salesforce on an hourly basis—which means integration is generally immaterial when it comes to API limits. We ingest the objects outlined below by default—but it’s also possible to explicitly define additional objects as needed. After the initial sync, we constrain subsequent requests to records that have been updated (as determined by SystemModStamp). Endgame polls for the query job to complete with incremental backoffs starting at every one minute and going up to ten minutes between job completion poll attempts. Endgame also downloads the results using a page size of 25,000, downloading those pages in parallel. Data from Salesforce is fetched using the credentials of the first user to log into Endgame. If needed, these credentials can be updated to a different user by sending a request to support@endgame.io.
Only accounts the integration user has permission to in Salesforce will be run through any AI systems. The integration user is the one you first log in with after consultation with Endgame.

​
Default objects

Endgame ingests a number of Salesforce objects by default, but please note that additional objects may be added in the future to enable additional functionality.

  • Account
  • User
  • Lead
  • Contact
  • Opportunity
  • Task
  • Event

  • RecordType
  • OpportunityLineItem
  • OpportunityContactRole
  • Campaign
  • CampaignMember
  • Note
  • OpportunityHistory

​
Important fields

Endgame references all standard fields in the above objects by default, and while custom fields are also ingested as part of the integration, Endgame does not automatically reference all custom fields as Salesforce instances often have hundreds of fields and only a handful that truly matter to help users deeply understand their accounts. Instead, Endgame provides two mechanisms to reference information from custom fields: 1) by explicitly instructing Endgame to reference certain custom fields (“Important fields”) within a chat prompt; and 2) by allowing administrators to designate specific custom fields for Endgame to reference by default. To configure your Important fields:
1

Go to the configuration page

Navigate to https://end-p1.endgame.io/settings (only available to admins)
2

Focus on Salesforce

Click “Manage” in the Salesforce Integration within the General tab.Screenshot 2025-07-23 at 8.38.05 PM.png
3

Select an object

Select the object that contains fields you deem important from an Endgame perspective.Screenshot 2025-07-23 at 8.40.37 PM.png
4

Mark select fields as important

Search for and mark “Important” the fields you want Endgame to focus on. Then, click “Submit Changes”. It will take a few minutes for your changes to be reflected.
You can select up to 50 fields per object.
Screenshot 2025-07-23 at 8.42.36 PM.png
Standard fields along with custom fields that are populated on 1 or fewer records are omitted from the list.