Integrations · SaaS applications · Available now

Salesforce test data, inside your network

Salesforce connector: object discovery through the REST describe API (Id as key, single-target lookups as relationships), SOQL query and queryMore reads with a pinned API version, and the org's daily API budget respected.

Available now SaaS applications

Shipped in the standard agent and backed by recorded conformance evidence.

What works today

Salesforce connector: object discovery through the REST describe API (Id as key, single-target lookups as relationships), SOQL query and queryMore reads with a pinned API version, and the org's daily API budget respected.

OAuth 2.0 client credentials or an access token, both as secret references. Reads stop before the remaining daily API calls fall below a configurable floor. Optional incremental extraction by SystemModstamp. Records are processed inside your environment and never sent to DataNivra Cloud.

Authentication: OAuth 2.0 client credentials (secret reference); access token (secret reference).

Known limitations

  • Requires agent 0.4.0 or later (the Salesforce connector ships in the standard agent image).
  • Verified against one real Salesforce Developer Edition org (REST API v61.0, OAuth 2.0 client credentials through External Client Apps) with synthetic custom objects; other editions, standard objects and large orgs are untested.
  • Only configured objects are read; polymorphic lookups are not turned into relationships.
  • base64 (attachment body) fields are not read.

Capability matrix

Each capability is tracked separately and shown at the level the recorded conformance evidence supports. A connector that only discovers metadata is never presented as equivalent to one that runs the whole workflow.

Capabilities of Salesforce
CapabilityLevel
DiscoverySupported
ClassificationSupported
ProfilingSupported
MaskingSupported
Deterministic maskingSupported
Entity-aware subsettingSupported
Relationship preservationSupported
Synthetic workflowsSupported
CertificationSupported
ProvisioningSupported
CI/CDSupported
Evidence generationSupported

Read-only proof

Proven before reading: the running user's permission sets (profile and assigned sets) may hold neither Modify All Data nor Modify Metadata, and no Create, Edit, Delete or Modify All permission on any configured object; anything else, or a permission query that fails, refuses the source.

Conformance evidence

DataNivra runs every connector through a common conformance kit on synthetic data: no write statements, proven read-only access, secret redaction, schema and relationship discovery, bounded streaming, cancellation, clear reason codes, egress canaries and no raw values in logs, then the discover, mask, subset, certify and provision workflow. The published status is computed from those results.

Environments whose conformance run met the preview minimum
Engine or serviceVersionEnvironmentDriverAuthenticationVerified on
Salesforce (Developer Edition)API v61.0managed-servicehttpx 0.28.1OAuth 2.0 client credentials2026-10-12

Connector version 0.1.0, last verified 2026-10-12.

What crosses the boundary

Connectors run inside the agent in your network. Only metadata, aggregates and evidence reach DataNivra Cloud:

  • Schema, table and column names and data types (for file sets, operator-declared or opaque table names — never data-derived file names).
  • Aggregates such as row-count estimates, null and distinct ratios; counts from 1 to 10 are reported as 10 (small-cell protection).
  • Classification findings (which column looks like which kind of sensitive data) and relationship metadata.
  • Evidence metadata: checksums, gate outcomes, engine and policy versions, and templated error codes.

Never sent:

  • Any cell value, row, sample, minimum/maximum or top-k value — masked or not.
  • Credentials, connection strings or resolved secret values: DataNivra stores only the secret reference.
  • Free text copied from your data, or exception messages that contain values.

See the customer-resident architecture and how to verify these claims yourself.

Setup outline

  1. Use agent 0.4.0 or later (earlier agent images do not include the Salesforce connector).
  2. Create a dedicated integration user and a permission set with API Enabled, View Setup and Configuration (Salesforce adds View Roles and Role Hierarchy) and Read on the objects to read. Grant no Create, Edit, Delete, Modify All, Modify All Data or Modify Metadata.
  3. Create an External Client App (or connected app) with the OAuth 2.0 client-credentials flow, the api scope and that user as its Run As user.
  4. Store the connection document with the consumer secret as a secret reference; instance_url is your My Domain URL, where the agent requests its token.
  5. In the console, register the source with the secret reference of that document (for example vault://tdm/source-connection) and the agent that can reach it, then run discovery.
  6. Before reading, the agent proves from the user’s permission sets that it cannot write to the configured objects and refuses to continue if it can; it sends GET requests only and stops before the org’s daily API budget runs low.

Example connection document, stored in your secret store and resolved by the agent locally (DataNivra only ever sees its reference):

{
  "kind": "SALESFORCE",
  "instance_url": "https://example-org.my.salesforce.com",
  "api_version": "61.0",
  "auth": "oauth2_client_credentials",
  "client_id": "tdm-reader-consumer-key",
  "client_secret_ref": "vault://tdm/salesforce#client_secret",
  "objects": {
    "members": { "api_name": "Member__c" },
    "claims": { "api_name": "Claim__c" }
  }
}

Next: install the agent, then follow the getting started guide.

All integrations · SaaS application test data management · Guides · Start free