Salesforce

The Salesforce Connector integrates with the Salesforce REST API to synchronize CRM records (SObjects) with the Brinqa platform. It uses a dynamic schema discovery mechanism — at runtime the connector interrogates the Salesforce /sobjects metadata endpoint, discovers all queryable SObject types, and builds ObjectClassInfo schemas automatically from field descriptors. Records are fetched via SOQL queries and support incremental synchronization using the SystemModStamp field.

You can bring CRM records data from Salesforce into Brinqa to gain a unified view of your attack surface, thus strengthening your cybersecurity posture.

This document details the information you must provide for the connector to authenticate with Salesforce and how to obtain that information from Salesforce. See create a data integration for step-by-step instructions on setting up the integration.

Required connection settings

When setting up a data integration, select Salesforce from the Connector dropdown. If you cannot find the connector in the dropdown, make sure that you have installed it first. You must provide the following information to authenticate Salesforce with Brinqa:

• API URL: Salesforce instance base URL.
• Login URL: OAuth token endpoint base URL (e.g., https://login.salesforce.com).
• Client ID: OAuth connected app Consumer Key.
• Client Secret: OAuth connected app Consumer Secret.
• Username: Salesforce username (required for password grant).
• Password: Salesforce password (required for password grant).
• Grant type: OAuth grant type (password or client_credentials).
• API version: Salesforce REST API version (e.g., v63.0).

The connector uses OAuth 2.0 to obtain a Bearer token from the Salesforce token endpoint. Two grant types are supported: password and client_credentials. It sends a POST request to the token endpoint with the client credentials and uses the returned bearer token for subsequent API requests.

Additional settings

The Salesforce connector contains additional options for specific configuration:

• Parallelism Level: Thread count for parallel schema discovery. The default setting is the CPU count (max 8).
• Use Schema Cache: Cache SObject field schemas between syncs. The default setting is true.
• Page size: The maximum number of records to get per API request. The default setting is 1000. It is not recommended to go over 1000.
• Parallel requests: The maximum number of parallel API requests. The default setting is 8.
• Maximum retries: The maximum number of times that the integration attempts to connect to the Salesforce API before giving up and reporting a failure. The default setting is 5.
• Custom Headers For Create: Extra HTTP headers for POST requests (key1:value1,key2:value2).
• Custom Headers For Update: Extra HTTP headers for PATCH requests (key1:value1,key2:value2).

Types of data to retrieve

The Salesforce connector can retrieve the following types of data from the Salesforce API:

Table 1: Data retrieved from Salesforce

Connector Object	Required	Maps to Data Model
SObject (Dynamic)	Yes	N/A

info

For detailed steps on how to view the data retrieved from Salesforce in the Brinqa Platform, see How to view your data.

Attribute mappings

Expand the sections below to view the mappings between the source and the Brinqa data model attributes.

SObject (Dynamic)

Table 2: SObject (Dynamic) attribute mappings

Source Field Name	SDM Attribute
record["Id"]	UID
record["Id"]	NAME
record.attributes.url	URL
Generated (Timestamp when the sync batch started)	LAST_CAPTURED
record[fieldName]	(ALL SELECTED FIELDS)

Operation options

The Salesforce connector supports the following operation options:

Table 3: Operation options

Connector Object	Option	All Possible Values	Description	Example
SObject (Dynamic)	ATTRIBUTES_TO_GET	String[]	Salesforce field names to include in the SOQL SELECT clause. If unset, all fields returned.	Key: ATTRIBUTES_TO_GET Value: ["Id", "Name", "Industry"].
	WHERE	String	Custom SOQL WHERE clause fragment appended to the query.	Key: WHERE Value: "Industry = 'Technology'".

APIs

The Salesforce connector uses the Salesforce REST API. Specifically, it uses the following endpoints:

Table 4: Salesforce API Endpoints

Connector Object	API Endpoint
SObject (Dynamic)	GET /services/data/{apiVersion}/query?q={SOQL}
	GET /services/data/{apiVersion}/sobjects
	GET /services/data/{apiVersion}/sobjects/{type}/describe

Changelog

The Salesforce connector has undergone the following changes:

Table 5: Salesforce Changelog

Version	Description	Date Published
3.0.3	Initial Integration+ release. Added support for multiple OAuth 2.0 grant types, configurable API version, LAST_CAPTURED attribute, and centralized API path construction.	May 14, 2026