How to get your Salesforce data ready for agentic AI

Sync Salesforce standard and custom objects with Airbyte, then let AI agents read and search accounts, opportunities, and cases through the Airbyte MCP.

|
Nov 16, 2026

Summarize with AI:

Airbyte syncs Salesforce standard and custom objects into your warehouse with a least-privilege integration user, and the Airbyte context layer lets agents read and search Salesforce records directly through the Airbyte MCP.

Salesforce is where many companies keep the account story: who the customer is, what they are buying, which deals are open, and which cases they have raised. Sales, success, and support agents all need that story. Most of their questions also reach beyond Salesforce. Renewal risk depends on product usage and billing as well as pipeline stage.

Agents work best against a centralized, governed copy of that data. A warehouse copy lets agents run aggregate queries across years of opportunities without spending Salesforce API quota, and joins CRM records with the rest of the business. For "what is the current state of this record" questions, Airbyte also lets agents read Salesforce directly with read-only access.

Why Salesforce data matters for agentic AI

  • It is customized. Most orgs have custom objects and fields that carry the real business meaning. Agents need those, not just the standard schema.
  • It is permissioned. Profiles, permission sets, and field-level security decide who sees what. The integration user's permissions decide what Airbyte can read.
  • It is quota-bound. Salesforce enforces daily API limits, so how data is extracted matters.
  • It changes in subtle ways. Formula fields can change without the record's other fields changing, and deleted records sit in the recycle bin for a time.

What agents can do with Salesforce data

  1. Account briefings. Summarize an account's open opportunities, recent tasks and events, and open cases before a call.
  2. Pipeline review. Find opportunities that have been stuck in a stage, or that lack a next step, and list them for the owner.
  3. Support context. Pull a customer's case history and related contacts when a new case arrives.
  4. Lead routing help. Look up whether a new lead matches an existing contact or account.
  5. Access audits. Use the synced User and permission metric streams to answer who has which licenses and profiles.

How Airbyte gets Salesforce data ready

Authentication and the integration user

Airbyte recommends a dedicated Salesforce user with the Minimum Access standard profile, plus a permission set that grants Read only on the objects you want to sync. You can narrow it further with field-level security. Discovery then reflects only what that user can read.

Authentication methods:

  • ClientCredentials (your own External Client App). The default for new setups. You create a local External Client App for the client credentials flow and enter your My Domain URL, client ID, and client secret. This method doesn't use a refresh token, so Salesforce's 30-day idle refresh-token expiry doesn't apply. Salesforce classifies the flow as high risk because the key and secret alone grant access, so pair it with a least-privilege user.
  • Client (Airbyte Connected App). OAuth through Airbyte's existing Connected App. Salesforce no longer allows creating new Connected Apps as of Spring '26, so this is mainly for existing setups. The Sandbox toggle applies only to this method; for client credentials, your My Domain URL selects the org.

You need Enterprise edition, or Professional edition with API access as an add-on.

Streams

The connector reads standard and custom objects, each as its own stream. Objects appear when they are queryable and the user has permission to read them. You can filter which objects are offered by search criteria.

The connector can also sync security-related objects such as User, ActivePermSetLicenseMetric, and ActiveProfileMetric. Syncing full user data needs the "View All Users" permission.

Sync modes

  • Incremental Append + Deduped (recommended)
  • Full Refresh Overwrite and Full Refresh Append
  • Incremental Append

Start Date defaults to the last two years when blank. A Lookback Window (default 10 minutes, as an ISO 8601 duration) rereads recent changes to cover Salesforce's eventual consistency. Increase it if records go missing.

Bulk API vs REST API

The connector uses the Bulk API by default, which Salesforce recommends for large extractions. It falls back to the REST API for objects the Bulk API doesn't support or that have unsupported column types, which can cost more API quota.

Limits, deletes, and formula fields

  • Daily rate limits. When the connector hits the daily limit, it ends the sync early with success and resumes on the next run. Resuming works for incremental syncs only.
  • Deletes. For objects that support it, records in the recycle bin are synced with isDeleted=true.
  • Formula fields. If a formula changes but no other field on the record does, reset the stream and backfill to pick up the new values.

How agents reach Salesforce data

Salesforce is an agent connector in Airbyte Cloud, so it works with both parts of the context layer:

  • Agent access (direct reads). Agents can list and get accounts, contacts, leads, opportunities, tasks, events, campaigns, cases, notes, users, opportunity stages, and reports, and download content versions and attachments. Salesforce's own search is available on the main CRM objects, and a query action runs read queries. Direct reads use credentials stored in Airbyte, are read-only, and count toward your Salesforce API limits.
  • Search. When a connection syncs Salesforce to an agent-connector destination, Airbyte can index selected streams. The open-source Airbyte agent SDK lists semantic search for opportunities and tasks, which suits questions like "which deals mention a security review."

Agents connect through the hosted Airbyte MCP at https://mcp.airbyte.com/mcp. Direct reads and searches are free up to 100,000 combined per organization per month.

Direct reads use the connector's stored credentials, not each person's own Salesforce permissions. An Airbyte user could therefore see records through an agent that Salesforce sharing rules would hide from them. Scope the integration user and who can use the connector accordingly.

What this unlocks

  • Custom objects and fields available to agents, not just the standard schema.
  • A read-only integration user that limits what can leave Salesforce.
  • Syncs that respect daily API limits and resume where they stopped.
  • Deleted records flagged so counts stay accurate.
  • CRM records joined with billing, product, and support data.

Getting started

  1. Create a dedicated user with Minimum Access and a read-only permission set.
  2. Create an External Client App for client credentials, or use an existing Airbyte Connected App setup.
  3. Create the Salesforce source in Airbyte, pick objects, and use Incremental Append + Deduped.
  4. Sync to BigQuery or Snowflake, then connect your agent to the Airbyte MCP.

Try Airbyte free or talk to sales about CRM data for agents.

Frequently asked questions

Which Salesforce objects can Airbyte sync?

Standard and custom objects, each as its own stream. Airbyte discovers objects dynamically, so a stream appears when the object is queryable and the authenticated user has permission to read it.

How should I authenticate Salesforce with Airbyte?

Airbyte recommends a dedicated user with the Minimum Access profile and a read-only permission set. Salesforce no longer allows new Connected Apps as of Spring '26, so new setups use your own External Client App with the client credentials flow and a My Domain URL. Existing Airbyte Connected App OAuth setups still work.

What happens when Airbyte hits the Salesforce daily API limit?

The sync ends early with a success status and the next sync picks up where it stopped. Resuming only works for incremental syncs, which is why Airbyte recommends Incremental Append + Deduped for Salesforce.

Does Airbyte sync deleted Salesforce records?

Yes, for objects that support it. Records in the Salesforce recycle bin are synced with isDeleted set to true, so agents can filter them out.

Can an agent update Salesforce records through the Airbyte context layer?

No. Direct reads and searches through the context layer are read-only. Agents can list, get, and search Salesforce records, but cannot create, update, or delete them through these tools.

Integrate with 700+ apps using Airbyte

Move data from 700+ sources into warehouses, lakes, and beyond. Set up pipelines in minutes with pre-built connectors and the Connector Builder.