Connect Gmail, Google Sheets, and Salesforce — one workflow, no re-typing
Connecting two tools is easy. The pain is the triangle: an enquiry lands in Gmail, someone creates the lead in Salesforce, someone logs it in the tracking sheet, and someone writes the reply. Three copies of the same information, typed by hand, drifting apart within a week.
Here are the three ways to wire all three together, from cheapest to most capable.
Your three options
- 01
The native tools, piecemeal
Best for: Salesforce's Gmail integration logs emails against records, and Google's free Salesforce connector pulls reports into Sheets. Both free, both fine at their one job.
The catch: They don't talk to each other. You get email logging and report pulls, but nothing carries an enquiry through the chain — a person is still the glue between all three.
- 02
Zapier or Make, multi-step
Best for: A multi-step zap can go Gmail → Salesforce lead → Sheets row. For clean, predictable emails at low volume, this genuinely works.
The catch: Free-form enquiries break it — a zap copies the email, it doesn't understand it. Multi-step zaps also fail quietly, and per-task pricing triples when every email takes three actions.
- 03
A custom-built workflow
Best for: The enquiry is read and understood: lead created in Salesforce with the right fields, row appended to your tracking sheet, and a drafted reply waiting in Gmail for approval. One event, all three systems, human sign-off where it matters. This is what I build.
The catch: It's a built project — worth it when enquiries are frequent enough that the re-typing (and the leads that slip through it) cost real money.
What I build for Gmail + Sheets ↔ Salesforce
- Enquiry emails parsed and created as Salesforce leads with the right fields — not just a raw email blob
- The same enquiry appended to your team's tracking sheet at the same moment, so CRM and sheet never disagree
- A drafted reply in your voice waiting in Gmail for one-click approval
- Pipeline changes in Salesforce reflected back to the sheet your team actually looks at
- Follow-up nudges when an enquiry sits unanswered
Common questions
- Can Zapier connect Gmail, Google Sheets, and Salesforce?
- Yes, with a multi-step zap — and if your enquiries arrive in a consistent format at low volume, try that first. The custom route earns its cost when emails are free-form and the details need to be understood and extracted, not just copied.
- Do I need to change how my team works?
- No. Enquiries keep landing in the same inbox, Salesforce stays your CRM, and the sheet your team lives in keeps working. The automation runs in the gaps between them.
- What if the automation gets an email wrong?
- Anything ambiguous is flagged for a human instead of guessed at, and replies are drafts until you approve them. The failure mode is "asks you," not "sends something wrong."
- What does this cost?
- A three-system workflow is a fixed-scope project, typically measured in days. Tell me what your enquiry-to-CRM flow looks like today and I'll give you a straight answer — including "a zap is enough" if it is.
Exporting this by hand every week?
Send me what you’re copying between Gmail and Sheets ↔ Salesforce and I’ll tell you what can be automated, what it would take, and whether the free option is enough. No pitch.