Sync data between Google Sheets and Salesforce — import leads from spreadsheets, export reports to Sheets, and keep both systems updated.
What can you automate?
The most common ways teams connect Google Sheets and Salesforce.
Import leads from spreadsheets
When rows are added to a Google Sheet, create or update leads in Salesforce.
Export pipeline to Sheets
Every morning, query Salesforce for open opportunities and write them to a Google Sheet.
Bi-directional contact sync
When a Salesforce contact is updated, update the matching row in Sheets and vice versa.
Event lead import
After a trade show, paste attendee data into a Sheet and import all rows as Salesforce leads.
Weekly sales report
Every Friday, run a SOQL query for closed-won deals and append a summary to a spreadsheet.
Platform Comparison
How each automation tool connects Google Sheets and Salesforce.
Iterator for bulk row processing. SOQL support for precise exports.
Top triggers
Top actions
Code-first with pre-built components. Full npm/PyPI access in every step. Free tier includes 10K invocations/day.
Top triggers
Top actions
Find or Create Lead in one step. Salesforce is a premium app.
Top triggers
Top actions
Deep Microsoft 365 integration. Best when both apps have Power Automate connectors. Desktop flows add RPA capability.
Top triggers
Top actions
Full SOQL query access. Bulk API support for large imports.
Top triggers
Top actions
What Will This Cost?
Drag the slider to your expected monthly volume.
Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.
Prices shown for annual billing. Based on published pricing as of April 2026.
Estimated ROI
1000
min saved/mo
$583
labor value/mo
Free
no platform cost
Based on ~2 min manual effort per operation at $35/hr fully loaded labor cost.
When this pair isn't the right answer
Honest scenarios where Google Sheets + Salesforce via an automation platform isn't the best fit.
Salesforce Data Loader is free and built specifically for Sheet-to-Salesforce bulk loads. For scheduled imports or exports of more than about 1,000 rows, Data Loader uses the Salesforce Bulk API — dramatically faster and cheaper than row-by-row automation tool flows. The Data Import Wizard is even simpler for basic cases. Only use an automation tool when the sync needs to run on demand, trigger follow-up workflows, or combine Sheets data with another source first.
Row-by-row upserts at scale are the wrong approach. Automation tools typically call Salesforce once per row. Salesforce's Bulk API can ingest 10,000 records in a single call and is what Salesforce itself recommends above about 2,000 records. A 10,000-row nightly sync via an automation tool burns 10,000 tasks; the same job via Bulk API is one call. If your Sheet has that much data, move to Bulk API.
Salesforce Connect with the Google Sheets connector is native and live. If Salesforce needs to show Sheet data in a list view or Lightning component, Salesforce Connect can expose the Sheet as an "External Object" that Salesforce queries live — no sync job, no stale copies. It's a paid feature, but for read-only patterns it's the right choice.
What breaks at scale
Where Google Sheets + Salesforce integrations hit ceilings — API rate limits, tier quotas, and per-task economics.
Salesforce's 24-hour call limit is the real bottleneck. Enterprise Edition allocates about 1,000 calls per licensed user per 24 hours with a minimum floor. A nightly upsert of 5,000 rows one-at-a-time burns 5,000 calls before anything else runs — often 30 to 50% of a small org's daily budget. Bulk API jobs count as 1 call per batch of up to 10,000 records, which is how Salesforce expects you to handle volume.
Sheets read limits are per project, not per user. 100 reads per 100 seconds per user per project. A Zapier account running a polled Sheets read every 15 minutes across 20 different flows hits this during peak hours. You don't get errors, just slower polls — the integration falls behind without raising alarms.
Per-task pricing collapses on high-row-count syncs. Row-level upserts bill 1 task per row whether the row actually changed or not. A weekly 10,000-row sync = 40,000 tasks a month on that flow alone, which is above most team plans. Bulk API plus a simple scheduled script does the same job with about 1/40th the task count.
Our Recommendation
Make handles Salesforce's complex data model better than Zapier for bulk operations.
- Its iterator module processes spreadsheet rows one at a time without custom code.
Analysis
Google Sheets-to-Salesforce is the integration that replaces manual data imports. Every sales team has a "upload this spreadsheet to Salesforce" workflow.
The direction matters.
Sheets-to-Salesforce (importing) and Salesforce-to-Sheets (exporting) are fundamentally different workflows. Most teams need both directions.
[Make](/platforms/make/) is the best platform for bulk imports.
Salesforce API access is required.
You need Professional edition ($80/user/month) or higher. Essentials edition does not include the API.
Deduplication is critical for imports.
If you import the same spreadsheet twice, you do not want 1,000 duplicate leads. Zapier has Find or Create Lead. Make requires Search → Router → Create.
For exports: scheduled SOQL reports.
Run a SOQL query every morning and write results to a Google Sheet. Make and n8n support raw SOQL queries.
Zapier uses point-and-click field selection.
Google Sheets + Salesforce Workflow Guides
Step-by-step setup guides for connecting Google Sheets and Salesforce.