Connect Salesforce to Google Sheets

A sheet is where a non-technical stakeholder wants a report, and where a team wants to keep a lookup table they can edit without a ticket. The manual version is a rep exporting a report each Monday, or an ops person copy-pasting a routing table into a flow's configuration.

• A pipeline or forecast sheet is refreshed on a schedule, with headers, formatting, and a last-updated cell, so a manager reads current data without a Salesforce seat
• A routing, pricing, or threshold sheet is read live by a flow, so a change the sales ops team makes takes effect on the next run with no deploy
• Rows are matched on a key column you choose, an ID or an email, rather than the row number, so an insert or a sort does not corrupt the sync
• Every write is a run you can inspect with the range and the values, so a bad refresh can be traced and run again

The two flows most revenue-ops teams turn on first.

A refreshed open-pipeline sheet, and a routing sheet that drives lead assignment

One scheduled export flow, and one flow that reads the sheet as a config.

1. 1
   Export trigger: a schedule every weekday at 07:00 in the sales leader's timezone.
2. 2
   Query: Salesforce Query (SOQL) for open opportunities with the owner, stage, amount, close date, and next step.
3. 3
   Write: Google Sheets clears Pipeline!A2:H and writes the result there with the values update operation, keeping the header row and a formula summary below untouched, and sets Meta!B1 to now().
4. 4
   Routing trigger: a lead-routing flow starts on the Salesforce New lead trigger and continues when the lead has no assigned owner.
5. 5
   Read the table: read Routing!A:D from Google Sheets, then a Lookup step finds the row where country and segment match and returns owner_email. A catch-all row with country = ANY covers the gaps.
6. 6
   Assign: a Salesforce update sets OwnerId from the resolved email. If no rule matches, the flow appends a row to Unrouted!A:D for sales ops to fix.
7. 7
   Reprocess: a second flow polls Unrouted and re-runs assignment once a matching rule is added.

The starting map for the open-pipeline export. The header row is the schema; the key column is what a later update matches on.

For the routing sheet the direction reverses: the sheet's columns (country, segment, owner_email, notes) are the source, and the Lookup step returns owner_email for the flow to write to Lead.OwnerId.

• Scheduled exports. Pipeline, forecast, activity, and renewal reports refreshed on a schedule with a last-updated stamp. (Salesforce to Sheets)
• Row-level updates. A specific opportunity or account row is updated in place when the record changes, found by the key column. (Salesforce to Sheets)
• Config tables. Routing rules, discount thresholds, territory maps, and enum lookups are read live by flows so a business team owns them. (Sheets to Salesforce)
• Bulk edits and imports. A sheet a team fills in, new leads, account updates, is validated row by row and upserted into Salesforce, with errors written to a status column. (Sheets to Salesforce)

The same controls apply to this sync as to every other Neblex workload.

• Run history. Every write records the spreadsheet, the range, and the values. A failed refresh can be replayed from the step that failed, or simply run again.
• Approval on bulk import. A sheet-to-Salesforce import can include a Wait for form step, so a person reviews the rows before a mis-keyed column updates a thousand records.
• Scoped access. Google uses OAuth as an account that only has access to the sheets the flows need. Salesforce uses a permission set limited to the objects read and written.
• Environments. Build against a Salesforce sandbox and a copy of the sheet, then promote the same flow to production with the production spreadsheet.