Advanced Analytica Advanced Analytica: IBOM
← All connectors
Salesforce logo

Source connector

Salesforce

Set up Salesforce as a source and move its data into your chosen destination.

Version 2.11.1 certified generally available

Salesforce

Use this page to set up and reference the Salesforce source connector.

Prerequisites

  • A Salesforce Account with Enterprise edition or Professional edition with API access purchased as an add-on

You may also need the following items. This article explains how to get them.

  • Optional but recommended: A dedicated Salesforce user
  • For ClientCredentials (Use your own External Client App), a local External Client App configured for the client credentials flow and a My Domain URL
  • For Airbyte Open Source: Salesforce OAuth credentials

Setup

Set up Salesforce

Create a Minimum Access standard profile, then assign custom permission sets. These give the new user read access to the required data.

You can use any Salesforce user with read permission. However, a dedicated user with the Minimum Access standard profile gives you granular control.

Use Permission Sets to give this user read access to the data Airbyte needs. Learn more about Permission sets in Salesforce’s documentation. To sync Salesforce permissions data, you also need the permissions necessary to sync security-related data.

Log in to Salesforce with an admin account.

Step 1: Create a user
  1. Click the gear icon in the top-right corner, then click Setup.
  2. In the left navigation bar, under Administration, click Users > Users.
  3. Create a new User. Enter the user’s first name, last name, alias and email.
  4. Entering the email automatically fills the username and nickname fields.
    1. Leave role unspecified
    2. Select Salesforce for the User License
    3. Select Standard User for Profile.
    4. Choose whether to generate a new password and notify the user.
    5. Select save
Step 2: Create a permission set
  1. In the left navigation bar, select Users > Permission Sets.
  2. Click New to create a Permission Set.
  3. Give your permission set a descriptive label, such as “Airbyte Read Only Access”. The API name fills automatically from this label.
  4. For licence, leave –None— selected and click save.
  5. After creating the permission set, define its permissions through Object Settings.
    1. Click “Object Settings.”
    2. Select the Object Name for each object requiring read-only access, such as Accounts, Contacts and Opportunities.
    3. Select “Edit”, check the “Read” permission and clear every other permission, including Create, Edit and Delete.
    4. Click Save
    5. Continue adding read permissions for every object Airbyte needs to access.
  6. Enable an additional permission to access uninstalled connected apps.
    1. Click “System Permissions”
    2. Select “Edit”
    3. If API Access Control is enabled, check the “Use Any API Client” permission.
    4. If API Access Control isn’t enabled, check the “Approve Uninstalled Connected Apps” permission.
    5. Click Save
Step 3: Assign the permission set
  1. On the Permission Sets page, click “Manage Assignments” beside your new read-only permission set.
  2. Click “Add Assignments.”
  3. Find and select the user you created in Step 1.
  4. Click Assign

Open the email account you used and verify your new Salesforce user. You’ll set a password during this process. Keep it accessible.

:::info Profile vs. Permission Set: The user’s profile provides their baseline permissions. The permission set adds or restricts permissions beyond that baseline. Object-Level vs. Field-Level Security: This guide covers object-level read-only access. You can use object-level security or set more granular controls. Within each object settings page, scroll down and select read access for only the required fields. :::

Get Salesforce OAuth credentials (Airbyte Open Source only)

To authenticate with Airbyte Open Source, get these OAuth credentials:

  • Client ID
  • Client Secret
  • Refresh Token

Use credentials from an existing OAuth app with Client (Airbyte Connected App). Salesforce no longer allows new Connected Apps from Spring ‘26. For a new app, follow Use your own External Client App (client credentials) below. Set Authentication Method to ClientCredentials (Use your own External Client App). This method doesn’t require a refresh token.

Use your own External Client App {#use-your-own-external-client-app-client-credentials}

Create a local External Client App (ECA) in your Salesforce org. This connects without an Airbyte-managed OAuth app or refresh token:

  1. Create or choose a dedicated integration user for the Run As user. Give it read access to the objects and fields you want to sync. See Create a dedicated Salesforce user.
  2. In Salesforce Setup, search for External Client App Manager, then click New External Client App. Under Basic Information, enter an app name and contact email. Keep the suggested API name and set Distribution State to Local. See Salesforce’s External Client App creation guide.
  3. Enable OAuth for the app. The form requires a Callback URL. Enter a placeholder because the client credentials flow doesn’t use it. Under Available OAuth Scopes, add Manage user data via APIs (api). You don’t need the web and refresh_token, offline_access scopes. See Salesforce’s OAuth settings guide and client credentials flow guide.
  4. In the app’s Settings, enable Client Credentials Flow and save the change.
  5. In External Client App Manager, open the app’s actions list and select Edit Policies. In the client credentials policy, enable Client Credentials Flow if needed. Set Run As to the integration user’s username and save the policies. See Salesforce’s External Client App client credentials policy guide. Client-credentials policy changes for Connected Apps can take several minutes to propagate. Allow time before testing (Salesforce guidance).
  6. In External Client App Manager, open the app’s actions list and select Edit Settings. Expand OAuth Settings, then select Consumer Key and Secret to copy the consumer key and secret. Salesforce might ask you to verify your identity before displaying them. See the client credentials flow guide.
  7. In Setup, search for My Domain and open it. Copy your org’s URL. A production URL looks like https://acme.my.salesforce.com. A sandbox URL looks like https://acme--uat.sandbox.my.salesforce.com. Salesforce explains where to find this URL in its client credentials flow guide.
  8. In Airbyte, set Authentication Method to ClientCredentials (Use your own External Client App; selected by default). Enter the My Domain URL, consumer key (Client ID) and consumer secret (Client Secret).

Salesforce classifies this flow as high-risk because the key and secret alone grant access. Use a least-privilege integration user. Stream discovery shows only objects and fields the Run As user can read. is_sandbox doesn’t select the org for ClientCredentials. The My Domain URL selects it. A sandbox refresh doesn’t copy locally created External Client Apps. Recreate the app in the refreshed sandbox.

This method doesn’t use a refresh token. Salesforce’s 30-day idle refresh-token expiry therefore doesn’t apply.

Set up the connector in Airbyte

Airbyte Cloud

  1. Log into your Airbyte Cloud account.
  2. Click Sources, then click + New source.
  3. On the Set up the source page, select Salesforce from the Source type dropdown.
  4. Enter a name for the Salesforce connector.
  5. Set Authentication Method to one of these options:
    • ClientCredentials (Use your own External Client App; selected by default): Enter your My Domain URL, Client ID (consumer key), and Client Secret (consumer secret) from your External Client App.
    • Client (Airbyte Connected App): Click Authenticate your account to authorise your Salesforce account. Airbyte authenticates the Salesforce account you’re already signed in to. Confirm it’s the correct account.
  6. The Sandbox toggle applies only to Client (Airbyte Connected App). For ClientCredentials, your My Domain URL selects the org.
  7. (Optional) For Start Date, use the datepicker or enter the date in YYYY-MM-DD or YYYY-MM-DDTHH:MM:SSZ format. Data added on or after this date will be replicated. If blank, Airbyte replicates the previous two years by default. Timestamps use UTC.
  8. (Optional) For End Date, use the datepicker or enter the date in YYYY-MM-DD or YYYY-MM-DDTHH:MM:SSZ format. Incremental streams replicate data updated before this date. This exclusive bound means a date-only value excludes the named day from midnight UTC. Full refresh streams ignore this field and replicate all data. If blank, Airbyte replicates data up to the current time. Timestamps use UTC.
  9. (Optional) Use the Filter Salesforce Object section to target specific data for replication. Click Add, then select the relevant criteria from the Search criteria dropdown. For Search value, add your relevant search terms. You can add multiple filters. Without filters, Airbyte replicates all data.
  10. (Optional) For Lookback Window, enter an ISO 8601 duration, such as PT10M, PT30M or PT1H. This controls how far back the connector rereads data during each incremental sync. The default is PT10M (10 minutes). Increase this value if records are missing from your destination. Salesforce API eventual consistency delays can cause this issue.
  11. (Optional) Enable Preserve “NA” and similar string values to preserve literal strings such as NA, N/A, NULL, None or NaN. Otherwise, these strings sync as null. This setting applies only to streams synced through the Bulk API. REST-synced streams already preserve these values. The setting is off by default, so these strings are treated as null. See Preserving “NA” string values for details.
  12. Click Set up source and wait for the tests to finish.

Airbyte Open Source

  1. Open the Airbyte Open Source dashboard.
  2. In the left navigation bar, click Sources. In the top-right corner, click + New source.
  3. Find and select Salesforce from the available sources.
  4. Enter a recognisable Source name for this source.
  5. Set Authentication Method to one of these options:
    • ClientCredentials (Use your own External Client App; selected by default): Enter your My Domain URL, Client ID (consumer key), and Client Secret (consumer secret) from your External Client App.
    • Client (Airbyte Connected App): Enter your Client ID, Client Secret, and Refresh Token.
  6. The Sandbox toggle applies only to Client (Airbyte Connected App). For ClientCredentials, your My Domain URL selects the org.
  7. (Optional) For Start Date, use the datepicker or enter the date in YYYY-MM-DD or YYYY-MM-DDTHH:MM:SSZ format. Data added on or after this date will be replicated. If blank, Airbyte replicates the previous two years by default. Timestamps use UTC.
  8. (Optional) For End Date, use the datepicker or enter the date in YYYY-MM-DD or YYYY-MM-DDTHH:MM:SSZ format. Incremental streams replicate data updated before this date. This exclusive bound means a date-only value excludes the named day from midnight UTC. Full refresh streams ignore this field and replicate all data. If blank, Airbyte replicates data up to the current time. Timestamps use UTC.
  9. (Optional) Use the Filter Salesforce Object section to target specific data for replication. Click Add, then select the relevant criteria from the Search criteria dropdown. For Search value, add your relevant search terms. You can add multiple filters. Without filters, Airbyte replicates all data.
  10. (Optional) For Lookback Window, enter an ISO 8601 duration, such as PT10M, PT30M or PT1H. This controls how far back the connector rereads data during each incremental sync. The default is PT10M (10 minutes). Increase this value if records are missing from your destination. Salesforce API eventual consistency delays can cause this issue.
  11. (Optional) Enable Preserve “NA” and similar string values to preserve literal strings such as NA, N/A, NULL, None or NaN. Otherwise, these strings sync as null. This setting applies only to streams synced through the Bulk API. REST-synced streams already preserve these values. The setting is off by default, so these strings are treated as null. See Preserving “NA” string values for details.
  12. Click Set up source and wait for the tests to finish.

Supported sync modes

The Salesforce source connector supports these sync modes:

Supported streams

The Salesforce connector reads Standard Objects and Custom Objects from Salesforce. It reads each object as a separate stream. See all Salesforce Standard Objects here.

Airbyte dynamically exports available Salesforce objects based on these conditions:

  • The authenticated Salesforce user has the Role and Permissions required to read and fetch objects. Set these through the Permission Set assigned to the Airbyte user. See Create a dedicated Salesforce user for details.
  • The Salesforce object’s queryable property is set to true. Airbyte can only fetch queryable objects. If a queryable object isn’t available in Airbyte, check the authenticated Salesforce user’s API access.

Sync permissions data

The Salesforce connector can sync security-related objects. Use this data to understand user permissions, roles and access patterns within your Salesforce organisation.

Common uses for Salesforce permissions data include:

  • Permission Replication: Use Salesforce source permissions to guide downstream permissions.
  • Security Auditing: Create reports about user access rights and permission assignments.

These streams contain security and permissions data:

  • User: Core user accounts with security fields, including profiles, roles and user permissions. Includes user status, login history and assigned licences.
  • ActivePermSetLicenseMetric: Permission set licence usage metrics, including assigned users, active users and total available licences.
  • ActiveProfileMetric: User profile usage metrics, including user licence associations and assignment counts.

For full details about Salesforce security objects, see the Salesforce Object Reference documentation.

How permissions syncing works

Salesforce provides some security-related data through its standard object model:

  1. Dynamic Object Discovery: The connector automatically discovers available Salesforce objects (sobjects) based on the authenticated user’s permissions.
  2. Permission-Based Access: Available security objects depend on the authenticated user’s permissions and your Salesforce environment configuration.
  3. Standard Object Syncing: Available security-related objects sync as regular Salesforce objects through the same mechanisms as other business data.

:::note Security-related object availability varies by Salesforce environment, including production and sandbox, and by user permissions. Security objects can contain large datasets when you have many users. Monitor your Salesforce API limits accordingly. :::

Permissions required {#permissions-to-sync-permissions}

The authenticated Salesforce user needs permission to read security objects. Consider granting these permissions through a dedicated permission set:

  • “View All Users”: Required to access comprehensive User data.
  • Standard read permissions for the specific objects you want to sync.

For more about Salesforce security and permissions, see the official Salesforce documentation on User Permissions and Permission Sets.

IP allow list

If you use Airbyte Cloud and restrict access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.

Limitations and troubleshooting

Connection test login failures

  • Expired or revoked authentication / invalid_grant: Re-authenticate the source. Check Sandbox (is_sandbox). Sandbox organisations authenticate through test.salesforce.com, while production organisations use login.salesforce.com.
  • Invalid Connected App credentials / invalid_client_id or invalid_client: Compare the OAuth client ID and client secret in the source settings with the Connected App.
  • API access disabled / API_DISABLED_FOR_ORG: Use a Salesforce edition that supports API access. Give the authenticated user the API Enabled permission.
  • IP restrictions / LOGIN_MUST_USE_SECURITY_TOKEN: Allowlist the Airbyte deployment’s outbound IP addresses. Alternatively, update the Connected App IP Relaxation policy to meet your security requirements. For Airbyte Cloud, use the addresses linked in IP allow list.
Expand to see details about Salesforce connector limitations and troubleshooting.

Connector limitations

Rate limits

Salesforce’s Daily Rate Limits restricts the connector. It syncs until reaching the daily rate limit, then ends early with a successful status. The next sync continues where it stopped. This continuation works only with incremental syncs, so use the Incremental Sync - Append + Deduped sync mode.

Sync formula fields

The Salesforce connector syncs formula field outputs. If a formula changes without another field update, reset the stream. Then sync a historical backfill to retrieve every updated field value.

Sync deleted records

The Salesforce connector retrieves deleted records from the Salesforce recycle bin. Supported streams mark deleted records with isDeleted=true. To learn how Salesforce manages recycle bin records, see docs.

BULK API and REST API usage

Salesforce extracts data through either the BULK API or REST API. Salesforce recommends the BULK API for faster extraction above 2,000 records. The connector therefore uses the BULK API by default for Salesforce objects, except under these conditions:

  • The Salesforce object contains columns unsupported by the BULK API, such as base64 or complexvalue types.
  • The BULK API doesn’t support the Salesforce object. The connector then syncs it through the REST API. This can sometimes consume more of your API quota. Affected objects include:
    • AcceptedEventRelation
    • Attachment
    • CaseStatus
    • ContractStatus
    • DeclinedEventRelation
    • FieldSecurityClassification
    • KnowledgeArticle
    • KnowledgeArticleVersion
    • KnowledgeArticleVersionHistory
    • KnowledgeArticleViewStat
    • KnowledgeArticleVoteStat
    • OrderStatus
    • PartnerRole
    • RecentlyViewed
    • ServiceAppointmentStatus
    • ShiftStatus
    • SolutionStatus
    • TaskPriority
    • TaskStatus
    • UndecidedEventRelation

For more about the differences between Salesforce APIs, see here.

:::info Force Using Bulk API Set Force Use Bulk API to true to ignore unsupported properties and sync streams through BULK API. :::

Session expiry during long Bulk API syncs

Salesforce access tokens expire after a configurable session timeout, which defaults to two hours. Before connector version 2.7.20, long Bulk API syncs could fail with INVALID_SESSION_ID errors. The connector captured the access token once at sync start and didn’t refresh it. From version 2.7.20, the connector refreshes the access token every 30 minutes. This occurs well before the default session timeout. If a session ends between refreshes, the connector detects the INVALID_SESSION_ID response. It then immediately refreshes the token before retrying.

If INVALID_SESSION_ID errors continue, confirm that you’re running connector version 2.7.20 or later.

Session expiry during REST pagination

Streams that can’t use the Bulk API use the REST queryAll endpoint. These include objects with compound fields, such as addresses. The connector paginates them with nextRecordsUrl. Before version 2.10.3, REST streams used the access token captured when the stream was created. They couldn’t refresh it or use a token refreshed by another stream. If the session ended during a sync, the REST stream continued retrying with the expired token. This could happen after the proactive refresh above when Refresh Token Rotation was enabled. The sync then failed with Exhausted available request attempts ... Salesforce session expired or invalid.

From version 2.10.3, REST streams read the current access token for every request and retry. They therefore use refreshes made by any stream. They don’t initiate the 30-minute refresh. If their session ends, the INVALID_SESSION_ID response forces a token refresh before retrying. Salesforce retains query results for the same user across sessions. The retried nextRecordsUrl therefore continues where the stream stopped. If Salesforce rejects the refresh, the sync fails immediately with a configuration error asking you to re-authenticate. It doesn’t exhaust its retries.

Refresh Token Rotation (RTR)

Salesforce’s Refresh Token Rotation makes refresh tokens single-use. Each refresh_token exchange returns a new refresh token and immediately invalidates the previous one, without a grace period or overlap window. From version 2.8.0, the connector captures the rotated token after every token exchange. This includes initial login and the mid-sync refreshes described above. It saves the token to the connection configuration, allowing syncs to continue with RTR enabled.

From 4 November 2026, Salesforce expires refresh tokens after 30 inactive days. This affects the Client method, but not ClientCredentials. ClientCredentials doesn’t use refresh tokens. For External Client Apps created since July 2026, Salesforce permanently enables refresh token rotation.

Enable the connector support before enabling RTR on the app. Invalidation happens immediately. Enabling Enable Refresh Token Rotation while a connection uses a pre-2.8.0 connector will break it at the next token exchange. It will authenticate with an already invalidated token and require re-authentication. Follow this order:

  1. Upgrade the Salesforce source to 2.8.0 or later. On Airbyte Cloud, wait until the rollout reaches your workspace.
  2. Then enable Enable Refresh Token Rotation on the connected app / External Client App.

Responsibility for the connected-app setting depends on your authentication method:

  • Airbyte Cloud (default OAuth): the connected app is managed by Airbyte.
  • Airbyte Open Source / bring-your-own OAuth app: you own the connected app. After upgrading the connector, you’re responsible for enabling RTR.

Known limitations. Salesforce provides no grace window. Therefore, two edge cases remain inherent to RTR and can’t be fully prevented:

  • The pre-save Test connection button rotates the token but can’t save the new one because the connection doesn’t exist yet. This invalidates the token you just entered. Complete the connection setup promptly after testing. Re-authenticate if a later sync reports an authentication error.
  • Running a manual check during a sync on the same source can race two rotations and invalidate one. Don’t start a connection test while a sync is running.

ClientCredentials authentication errors

Error messageResolution
Salesforce accepts client credentials only at your org’s My Domain URL. Enter the URL shown in Salesforce Setup under My Domain.Use the My Domain URL from Salesforce Setup, not login.salesforce.com or test.salesforce.com.
Salesforce doesn’t recognize the Client ID. Enter the consumer key of your External Client App.Check the External Client App’s consumer key.
Salesforce rejected the Client Secret. Enter the consumer secret of your External Client App.Check the External Client App’s consumer secret.
The External Client App has no Run As user for the client credentials flow. Set Run As to your integration user in the app’s policies.Set Run As in the app’s Policies.
My Domain URL is required for the ClientCredentials method. Enter the URL shown in Salesforce Setup under My Domain.Enter your Salesforce My Domain URL.
Client ID and Client Secret are not set for the ClientCredentials method. Enter the consumer key and consumer secret of your External Client App.Enter both External Client App credentials.
Refresh Token is missing for the Client method. Authenticate your Salesforce account, or select ClientCredentials.Re-authenticate with Client (Airbyte Connected App) or set Authentication Method to ClientCredentials (Use your own External Client App).
Salesforce rejected the client credentials. Check Client ID, Client Secret and My Domain URL against your External Client App.Verify the app credentials and My Domain URL.

OAuth authorisation with required PKCE

Salesforce lets admins require the Proof Key for Code Exchange (PKCE) extension for OAuth authorisation flows, either across the org or on the connected app. Before connector version 2.9.1, authorisation failed in orgs requiring PKCE because requests omitted code_challenge. From version 2.9.1, the connector sends a code_challenge using the S256 method in the authorisation request. It sends the matching code_verifier during the token exchange. Authorisation therefore works whether your org requires PKCE or not. You don’t need to change the configuration.

Missing records from eventual consistency

Salesforce doesn’t guarantee immediate API access to recently created or updated records. A record may have its SystemModStamp set before the underlying transaction commits. During an incremental sync, the connector can move its cursor beyond these records. Later syncs can then miss them permanently.

Symptoms:

  • Records are missing from the destination but appear when you query Salesforce directly
  • The same source has no missing records when synced later to another destination
  • Sync logs contain no errors

Solution: Increase the Lookback Window in the connector configuration. This controls how far the connector rereads data from the previous cursor position during each incremental sync. The default is PT10M (10 minutes). If records are missing, try PT30M (30 minutes) or PT1H (1 hour). The connector uses append-dedup mode, so rereading overlapping data doesn’t create destination duplicates.

The lookback window uses ISO 8601 duration format. The format is PT<number><unit>. Here, P starts the duration and T separates date and time components. Common examples:

ValueMeaning
PT10M10 minutes
PT30M30 minutes
PT1H1 hour
PT2H2 hours
P1D1 day

Preserve “NA” string values {#preserving-na-string-values}

When using the Bulk API, the connector downloads results as CSV. By default, it interprets NA, N/A, NULL, None, NaN, null and #N/A as missing values. It then syncs them as null. This can affect data correctness when the string is a valid value. For example, NA might mean “North America” in a picklist.

Symptoms:

  • A Salesforce field containing NA/N/A or a similar value becomes null in the destination
  • This affects only streams synced through the Bulk API. See Usage of the BULK API vs REST API. REST-synced streams aren’t affected.

Solution: Enable Preserve “NA” and similar string values in the connector configuration using config field preserve_na_values. This preserves these strings while empty cells still sync as null. The option is off by default to preserve the connector’s historical behaviour. After enabling it, refresh the affected streams to backfill the corrected values.

Changelog

Expand to review
VersionDatePull RequestSubject
2.11.12026-11-0991215Add request timeouts and TCP keepalive so a stalled connection no longer hangs the sync
2.11.02026-10-2389735Add the ClientCredentials authentication method (Use your own External Client App) as the default, alongside Client (Airbyte Connected App)
2.10.52026-11-0390894Require Python 3.11 or newer, retaining support for Python 3.11–3.13.
2.10.42026-10-3090253Explain Salesforce OAuth, API permission, and IP restriction failures with actionable guidance and sandbox login hints.
2.10.32026-10-2387665Let REST streams use the refreshed access token, so a session invalidated mid-pagination no longer fails the sync, and mask rotated refresh tokens in logs
2.10.22026-10-2089072Fix syncs hanging indefinitely when a Salesforce OAuth token refresh or describe request stalls, by adding a request timeout
2.10.12026-10-2089399Update dependencies
2.10.02026-10-1589008Upgrade to Python 3.13 and base image 4.1.1
2.9.32026-10-0788170Surface the underlying request error and retry, instead of failing with an AttributeError, when a Salesforce request raises a non-HTTP error such as an invalid URL
2.9.22026-09-1085166Report a Salesforce field that no longer exists or is not accessible to the authenticated user as a configuration error naming the stream and field, instead of a system error containing the raw Salesforce response
2.9.12026-08-2785057Send PKCE code_challenge/code_challenge_method=S256 on the consent URL and code_verifier on the token exchange, so OAuth works in orgs that require PKCE
2.9.02026-08-2582722Add an optional end date for bounded incremental syncs
2.8.12026-08-0582784Fail fast when the refresh token is rejected instead of retrying the token endpoint from every stream
2.8.02026-07-2380892Persist rotated refresh token to support Salesforce OAuth Refresh Token Rotation (RTR)
2.7.262026-07-1682225Promoted release candidate to GA
2.7.26-rc.12026-07-1481535Use ordered ConcurrentMessageRepository so state checkpoints are emitted in-order with records, preventing data loss (cursor advancing past uncommitted records) when a sync is terminated ungracefully
2.7.252026-07-1380307Update cryptography to resolve CVEs (CVE-2026-26007, PYSEC-2026-35)
2.7.242026-07-0980738Add optional preserve_na_values config toggle (default off) to keep ‘NA’-like string values instead of converting them to null in Bulk API CSV parsing
2.7.232026-05-2178339Add granular OAuth scopes (api, web, refresh_token, lightning) to consent URL
2.7.222026-04-2876978Bump airbyte-cdk to ^7.17.4
2.7.212026-04-2877132Promoted release candidate to GA
2.7.21-rc.12026-04-2176389Fix bulk job slicing by bypassing deprecated DeclarativeStream.stream_slices() after CDK 7.13+ upgrade
2.7.202026-04-0275201Fix Bulk API INVALID_SESSION_ID by replacing static token provider with auto-refreshing SalesforceTokenProvider
2.7.192026-03-3175579Add oauth_connector_input_specification for declarative OAuth with sandbox/production URL switching
2.7.182026-02-2573501Skip time-based slicing for full refresh syncs
2.7.172026-02-1173235Make lookback window configurable to address Salesforce API eventual consistency
2.7.162025-10-2969078Promoting release candidate 2.7.16-rc.1 to a main version.
2.7.16-rc.12025-10-2767509Minor performance tuning
2.7.152025-10-2268166Add ActivityFieldHistory to UNSUPPORTED_FILTERING_STREAMS to fix missing records
2.7.142025-10-2168455Update dependencies
2.7.132025-10-1460432Update dependencies
2.7.122025-09-1566136Update to CDK v7
2.7.112025-05-1460271Define suggested streams
2.7.102025-05-1060100Update dependencies
2.7.92025-05-0459644Update dependencies
2.7.82025-04-2758997Update dependencies
2.7.72025-04-1958453Update dependencies
2.7.62025-04-1257976Update dependencies
2.7.52025-04-0557424Update dependencies
2.7.42025-03-2753689catch JSONDecodeError for error response
2.7.32025-03-2956776Update dependencies
2.7.22025-03-2455898Fix input state serialization issues
2.7.12025-03-2251921Update dependencies
2.7.02025-03-2055186Update manifest for adapting changes with AsyncRetriever
2.6.52025-02-2054178Promoting release candidate 2.6.5-rc.1 to a main version.
2.6.5-rc.12025-02-1853229Upgrade to API v62.0
2.6.42025-01-1148635Starting with this version, the Docker image is now rootless. Please note that this and future versions will not be compatible with Airbyte versions earlier than 0.64
2.6.32024-11-0546835Update dependencies
2.6.22024-10-10Bump minimum CDK to 5.10.2
2.6.12024-10-0546436Update dependencies, including CDK fix in v5.10.2
2.6.02024-10-0245678Have bulk streams use CDK components
2.5.342024-09-2846187Update dependencies
2.5.332024-09-2145779Update dependencies
2.5.322024-09-1445579Update dependencies
2.5.312024-09-0745329Update dependencies
2.5.302024-08-3144959Update dependencies
2.5.292024-08-2444747Update dependencies
2.5.282024-08-1744327Update dependencies
2.5.272024-08-1243732Update dependencies
2.5.262024-08-1043673Update dependencies
2.5.252024-08-0343211Update dependencies
2.5.242024-07-2742685Update dependencies
2.5.232024-07-2042166Update dependencies
2.5.222024-07-1341752Update dependencies
2.5.212024-07-1041529Update dependencies
2.5.202024-07-0941255Update dependencies
2.5.192024-07-0841043Use the latest CDK version possible
2.5.182024-07-0640835Update dependencies
2.5.172024-06-2540329Update dependencies
2.5.162024-06-2139927Update dependencies
2.5.152024-06-1639517Salesforce refactor: add CheckpointMixin for state management
2.5.142024-06-0639269[autopull] Upgrade base image to v1.2.2
2.5.132024-05-2338563Use HttpClient to perform HTTP requests for bulk, authentication and schema discovery
2.5.122024-05-1638255Replace AirbyteLogger with logging.Logger
2.5.112024-05-0938205Use new delete method of HttpMocker for test_bulk_stream
2.5.102024-05-0938065Replace deprecated authentication mechanism to up-to-date one
2.5.92024-05-0237749Adding mock server tests for bulk streams
2.5.82024-04-3037340Source Salesforce: reduce info logs
2.5.72024-04-2436657Schema descriptions
2.5.62024-04-1937448Ensure AirbyteTracedException in concurrent CDK are emitted with the right type
2.5.52024-04-1837419Ensure python return code != 0 in case of error
2.5.42024-04-1837392Update CDK version to have partitioned state fix
2.5.32024-04-1737376Improve rate limit error message during check command
2.5.22024-04-1537105Raise error when schema generation fails
2.5.12024-04-1137001Update airbyte-cdk to flush print buffer for every message
2.5.02024-04-1136942Move Salesforce to partitioned state in order to avoid stuck syncs
2.4.42024-04-0836901Upgrade CDK for empty internal_message empty when ExceptionWithDisplayMessage raised
2.4.32024-04-0836885Add missing retry on REST API
2.4.22024-04-0536862Upgrade CDK for updated error messaging regarding missing streams
2.4.12024-04-0336385Retry HTTP requests and jobs on various cases
2.4.02024-03-1235978Upgrade CDK to start emitting record counts with state and full refresh state
2.3.32024-03-0435791Fix memory leak (OOM)
2.3.22024-02-1935421Add Stream Slice Step option to specification
2.3.12024-02-1235147Manage dependencies with Poetry.
2.3.02023-12-1533522Sync streams concurrently in all sync modes
2.2.22024-01-0433936Prepare for airbyte-lib
2.2.12023-12-1233342Added new ContentDocumentLink stream
2.2.02023-12-1233350Sync streams concurrently on full refresh
2.1.62023-11-2832535Run full refresh syncs concurrently
2.1.52023-10-1831543Base image migration: remove Dockerfile and use the python-connector-base image
2.1.42023-08-1729538Fix encoding guess
2.1.32023-08-1729500handle expired refresh token error
2.1.22023-08-1028781Fix pagination for BULK API jobs; Add option to force use BULK API
2.1.12023-07-0628021Several Vulnerabilities Fixes; switched to use alpine instead of slim, CVE-2022-40897, CVE-2023-29383, CVE-2023-31484, CVE-2016-2781
2.1.02023-06-2627726License Update: Elv2
2.0.142023-05-0425794Avoid pandas inferring wrong data types by forcing all data type as object
2.0.132023-04-3025700Remove pagination and query limits
2.0.122023-04-2525507Update API version to 57
2.0.112023-04-2025352Update API version to 53
2.0.102023-04-0524888Add more frequent checkpointing
2.0.92023-03-2924660Set default start_date. Sync for last two years if start date is not present in config
2.0.82023-03-3024690Handle rate limit for bulk operations
2.0.72023-03-1424071Remove regex pattern for start_date, use format validation instead
2.0.62023-03-0322891Specified date formatting in specification
2.0.52023-03-0123610Handle different Salesforce page size for different queries
2.0.42023-02-2422636Turn on default HttpAvailabilityStrategy for all streams that are not of class BulkSalesforceStream
2.0.32023-02-1723190In case properties are chunked, fetch primary key in every chunk
2.0.22023-02-1322896Count the URL length based on encoded params
2.0.12023-02-0822597Make multiple requests if a REST stream has too many properties
2.0.02023-02-0222322Remove ActivityMetricRollup stream
1.0.302023-01-2722016Set AvailabilityStrategy for streams explicitly to None
1.0.292023-01-0520886Remove ActivityMetric stream
1.0.282022-12-2920927Fix tests; add expected records
1.0.272022-11-2919869Remove AccountHistory from unsupported BULK streams
1.0.262022-11-1519286Bugfix: fallback to REST API if entity is not supported by BULK API
1.0.252022-11-1319294Use the correct encoding for non UTF-8 objects and data
1.0.242022-11-0118799Update list of unsupported Bulk API objects
1.0.232022-11-0118753Add error_display_message for ConnectionError
1.0.222022-10-1217615Make paging work, if cursor_field is not changed inside one page
1.0.212022-10-1017778Add EventWhoRelation to the list of unsupported Bulk API objects.
1.0.202022-09-3017453Check objects that are not supported by the Bulk API (v52.0)
1.0.192022-09-2917314Fixed bug with decoding response
1.0.182022-09-2817304Migrate to per-stream states.
1.0.172022-09-2317094Tune connection check: fetch a list of available streams
1.0.162022-09-2117001Improve writing file of decode
1.0.152022-08-3016086Improve API type detection
1.0.142022-08-2916119Exclude KnowledgeArticleVersion from using bulk API
1.0.132022-08-2315901Exclude KnowledgeArticle from using bulk API
1.0.122022-08-0915444Fixed bug when Bulk Job was timeout by the connector, but remained running on the server
1.0.112022-07-0713729Improve configuration field descriptions
1.0.102022-06-0913658Correct logic to sync stream larger than page size
1.0.92022-05-0612685Update CDK to v0.1.56 to emit an AirbyeTraceMessage on uncaught exceptions
1.0.82022-05-0412576Decode responses as utf-8 and fallback to ISO-8859-1 if needed
1.0.72022-05-0312552Decode responses as ISO-8859-1 instead of utf-8
1.0.62022-04-2712335Adding fixtures to mock time.sleep for connectors that explicitly sleep
1.0.52022-04-2512304Add Describe stream
1.0.42022-04-2012230Update connector to use a spec.yaml
1.0.32022-04-0411692Optimised memory usage for BULK API calls
1.0.22022-03-0110751Fix broken link anchor in connector configuration
1.0.12022-02-2710679Reorganize input parameter order on the UI
1.0.02022-02-2710516Speed up schema discovery by using parallelism
0.1.232022-02-1010141Processing of failed jobs
0.1.222022-02-0210012Increase CSV field_size_limit
0.1.212022-01-289499If a sync reaches daily rate limit it ends the sync early with success status. Read more in Performance considerations section
0.1.202022-01-269757Parse CSV with “unix” dialect
0.1.192022-01-258617Update connector fields title/description
0.1.182022-01-209478Add available stream filtering by queryable flag
0.1.172022-01-199302Deprecate API Type parameter
0.1.162022-01-189151Fix pagination in REST API streams
0.1.152022-01-119409Correcting the presence of an extra else handler in the error handling
0.1.142022-01-119386Handling 400 error, while sobject doesn’t support query or queryAll requests
0.1.132022-01-118797Switched from authSpecification to advanced_auth in specefication
0.1.122021-12-238871Fix examples for new field in specification
0.1.112021-12-238871Add the ability to filter streams by user
0.1.102021-12-239005Handling 400 error when a stream is not queryable
0.1.92021-12-078405Filter ‘null’ byte(s) in HTTP responses
0.1.82021-11-308191Make start_date optional and change its format to YYYY-MM-DD
0.1.72021-11-248206Handling 400 error when trying to create a job for sync using Bulk API.
0.1.62021-11-168009Fix retring of BULK jobs
0.1.52021-11-157885Add Transform for output records
0.1.42021-11-097778Fix types for anyType fields
0.1.32021-11-067592Fix getting anyType fields using BULK API
0.1.22021-09-306438Annotate Oauth2 flow initialization parameters in connector specification
0.1.12021-09-216209Fix bug with pagination for BULK API
0.1.02021-09-085619Salesforce Aitbyte-Native Connector
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.