Skip to main content

​
Authentication

Endgame authenticates users via Salesforce OAuth. This allows for a seamless and secure user experience by leveraging Salesforce’s robust authentication framework. The API Integration User should sign in to Endgame first if you are using one. Endgame pulls data using the first user who connects - subsequent logins are only used for SSO. An admin can change the integration user on the integration settings page.

​
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.

​
User Permissions

If you encounter an OAUTH_APPROVAL_ERROR_GENERIC error while signing in to Endgame, check the following: Connected App Approval - The EndgameLabs2 Salesforce Connected App must be approved in Salesforce before users can log in. Users - Check the Permitted Users setting under Apps -> Connected Apps -> Manage Connected Apps -> EndgameLabs2 in Salesforce. Permitted Users has two options:
  • All users may self-authorize- all users will be able to access Endgame without pre-approval in Salesforce
  • Admin approved users are pre-authorized- individual users will need to be assigned a profile or permission set that grants them access to the app.
Integration User - The integration user must have the Approve Uninstalled Connected Apps permission to connect and for the EndgameLabs2 app to show up in Salesforce.

​
(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
  • Additional Permissions: Approve Uninstalled Connected Apps
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 [email protected].
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. The user can be updated by going to the integration page, hovering over the Connect button in the top right corner and clicking Reconnect.

​
Important fields

Endgame references all standard fields in the Required Objects section 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 Salesforce configuration page

Navigate to the Salesforce configuration page (only available to admins)
2

Configure important fields on required objects

From the Required Objects list, click on an object with the Configure tag.
Required object configuration

Required object configuration

3

Mark select fields as important

Search for the fields you want Endgame to include in responses, use the checkbox to select them, then click Save Changes. It will take a few minutes for your changes to be reflected.
Configure object fields modal

Configure object fields modal

You can select up to 50 fields per object. Standard fields along with custom fields that are populated on 1 or fewer records are omitted from the list.

​
Additional objects

Endgame utilizes a set of Salesforce objects by default in your chat responses. You can add addtional objects to be referenced for chat responses in the Salesforce admin configuration under the Additional Objects section. Simply toggle the additional objects on for them to be processed.
Additonal Salesforce objects

Additonal Salesforce objects