Do I need an account with Salesforce?

Yes. You connect your own Salesforce account once, from Ingest, and the data comes from what that account can see.

How fresh is the data?

As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.

Will running it again create duplicate rows?

No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.

Do I need to write code?

No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Salesforce

Business software

Ready to use

Salesforce data, published as Salesforce publishes it. Ingest delivers this data to a data warehouse you own as 17 tables, and updates it on the schedule you choose. There is no code to write and nothing to install.

What you get

Table	Each row is
account `account`	All Account rows, including soft-deleted ones (IsDeleted true). Incremental sync follows SystemModstamp, so edits and deletions are re-read; rows merge on Id.
campaign `campaign`	All Campaign rows, including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.
campaign_member `campaign_member`	Campaign members (the lead or contact linked to each campaign), including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.
case_ `case_`	All Case rows, including soft-deleted ones. Incremental sync follows SystemModstamp, so edits, status changes and deletions are re-read; rows merge on Id.
contact `contact`	All Contact rows, including soft-deleted ones. Compound Mailing/Other addresses repeat their separate columns. Incremental sync follows SystemModstamp; rows merge on Id.
event `event`	All Event rows (calendar activities), including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.
lead `lead`	All Lead rows, including soft-deleted ones and converted leads. Incremental sync follows SystemModstamp, so edits and deletions are re-read; rows merge on Id.
opportunity `opportunity`	All Opportunity rows, including soft-deleted ones. Incremental sync follows SystemModstamp, so edits and deletions are re-read; rows merge on Id.
opportunity_contact_role `opportunity_contact_role`	Opportunity contact roles (which contact plays which role on each opportunity), including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.
opportunity_history `opportunity_history`	Opportunity stage history (one row per stage change). This is historical data; incremental sync follows SystemModstamp, which for history rows tracks CreatedDate. Rows merge on Id.
opportunity_line_item `opportunity_line_item`	Opportunity line items (products on each opportunity), including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.
pricebook_entry `pricebook_entry`	All PricebookEntry rows (a product's price in each price book), including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.
pricebook2 `pricebook2`	All Pricebook2 rows (standard and custom price books), including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.
product2 `product2`	All Product2 rows (the product catalog), including soft-deleted and inactive ones. Incremental sync follows SystemModstamp; rows merge on Id.
task `task`	All Task rows (activities), including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.
user_ `user_`	All User rows visible to the execution user, including inactive and soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.
user_role `user_role`	All UserRole rows (the role hierarchy), including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.

Beyond these tables, Salesforce lists the other objects your own account holds when you connect it, your custom objects among them, and you choose which of them to sync. Each lands as a table of its own.

How it works

Choose Salesforce. Connect your Salesforce account once, from Ingest.
Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 10 more, in an account you own.
Pick a schedule. Daily is the default, and weekly and monthly are there too.
Ingest runs it from then on. If a run fails, your dashboard shows which table and why.

Questions

Do I need an account with Salesforce?: Yes. You connect your own Salesforce account once, from Ingest, and the data comes from what that account can see.
Which warehouses can Salesforce data go to?: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
How fresh is the data?: As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.
Will running it again create duplicate rows?: No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.
Do I need to write code?: No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

For your data team: technical reference

Connector salesforce, version 0.1.0, a REST source, status beta, authentication oauth2.

Vendor documentation: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_rest.htm

Configuration

Key	Label	Type	Required
`my_domain`	My Domain (the part before .my.salesforce.com)	string	yes

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`account` All Account rows, including soft-deleted ones (IsDeleted true). Incremental sync follows SystemModstamp, so edits and deletions are re-read; rows merge on Id.	beta	watermark	merge	`Id`	backfill_days
`campaign` All Campaign rows, including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.	beta	watermark	merge	`Id`	backfill_days
`campaign_member` Campaign members (the lead or contact linked to each campaign), including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.	beta	watermark	merge	`Id`	backfill_days
`case_` All Case rows, including soft-deleted ones. Incremental sync follows SystemModstamp, so edits, status changes and deletions are re-read; rows merge on Id.	beta	watermark	merge	`Id`	backfill_days
`contact` All Contact rows, including soft-deleted ones. Compound Mailing/Other addresses repeat their separate columns. Incremental sync follows SystemModstamp; rows merge on Id.	beta	watermark	merge	`Id`	backfill_days
`event` All Event rows (calendar activities), including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.	beta	watermark	merge	`Id`	backfill_days
`lead` All Lead rows, including soft-deleted ones and converted leads. Incremental sync follows SystemModstamp, so edits and deletions are re-read; rows merge on Id.	beta	watermark	merge	`Id`	backfill_days
`opportunity` All Opportunity rows, including soft-deleted ones. Incremental sync follows SystemModstamp, so edits and deletions are re-read; rows merge on Id.	beta	watermark	merge	`Id`	backfill_days
`opportunity_contact_role` Opportunity contact roles (which contact plays which role on each opportunity), including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.	beta	watermark	merge	`Id`	backfill_days
`opportunity_history` Opportunity stage history (one row per stage change). This is historical data; incremental sync follows SystemModstamp, which for history rows tracks CreatedDate. Rows merge on Id.	beta	watermark	merge	`Id`	backfill_days
`opportunity_line_item` Opportunity line items (products on each opportunity), including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.	beta	watermark	merge	`Id`	backfill_days
`pricebook_entry` All PricebookEntry rows (a product's price in each price book), including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.	beta	watermark	merge	`Id`	backfill_days
`pricebook2` All Pricebook2 rows (standard and custom price books), including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.	beta	watermark	merge	`Id`	backfill_days
`product2` All Product2 rows (the product catalog), including soft-deleted and inactive ones. Incremental sync follows SystemModstamp; rows merge on Id.	beta	watermark	merge	`Id`	backfill_days
`task` All Task rows (activities), including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.	beta	watermark	merge	`Id`	backfill_days
`user_` All User rows visible to the execution user, including inactive and soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.	beta	watermark	merge	`Id`	backfill_days
`user_role` All UserRole rows (the role hierarchy), including soft-deleted ones. Incremental sync follows SystemModstamp; rows merge on Id.	beta	watermark	merge	`Id`	backfill_days

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Clockify, Jira, Airtable, Facebook Ads, Frankfurter.

Get Salesforce data into your warehouse

Last updated 2026-10-26.