Can I add custom Opportunity fields to the sheet?

Yes. Add the field's API name to the mapping node and a column with the same header to the sheet. The setup guide shows the two edits side by side; there is no limit beyond what a sheet row can hold.

What about Opportunities that already exist?

The package includes a one-time backfill workflow. Run it once and it pages through every open and closed Opportunity and writes each as a row; from then on the live workflow keeps them current.

Does deleting an Opportunity remove the row?

No. The trigger reports creates and updates, not deletes, so a deleted Opportunity's row stays until someone removes it. Closed Lost is the usual path in Salesforce, and that is an update, which the sheet does receive.

Will it run on Make or Zapier?

Both versions ship in the package. Zapier uses the Salesforce Updated Record trigger, two Find Record steps for the account and owner names, and a Google Sheets lookup that updates the row or creates it. Make's Salesforce Watch Records module feeds the same mapping. Polling intervals depend on the plan you hold on each platform.

Do I need a paid n8n plan?

Any n8n Cloud plan works, and so does self-hosted. Polls that find no changes do not count as n8n executions, so the run count tracks how often Opportunities change rather than the polling interval.

SFGSMade to order

Sales & CRM hygiene

Salesforce opportunity changes → live pipeline sheet in Google Sheets

One Google Sheet that matches Salesforce, row for row, without anyone exporting.

Sales leaders who live in a spreadsheet keep asking for a fresh export. This package ends that. Whenever an Opportunity is created or edited in Salesforce, the matching row in a Google Sheet is added or updated, keyed on the Opportunity ID. The sheet holds name, account, stage, amount, close date, owner and last change, so any chart or pivot built on it stays current.

How it works

SF
Trigger
Opportunity created or updated (Salesforce Trigger node, polled every five minutes)
Salesforce
SF
Step 1
Look up the Account and Owner names
The trigger returns IDs for the Account and the Owner, so two small lookups fetch the account name and the owner's full name for the sheet.
if
Step 2
Map the Opportunity fields to sheet columns
Opportunity ID, name, account, stage, amount, close date, owner, created date and last modified date are shaped into one row in the column order the sheet expects.
GS
Step 3
Append or update the row matched on Opportunity ID
Matching runs on the Opportunity ID column; an existing row is overwritten in place and a new Opportunity gets a new row at the bottom.

What changes once it runs

A stage change in Salesforce is in the sheet within five minutes, in the same row it always was.
Charts, pivots and filters built on the sheet keep working because rows are updated in place, never duplicated.
New Opportunities appear at the bottom with every column filled, including the owner's name rather than an ID.
Nobody exports a report on Monday morning.

What you get

The n8n workflow export with the polling trigger and the append-or-update step configured
Make and Zapier versions for teams that already run on either
Google Sheets template with the nine columns, a Closed Won filter view and a pipeline-by-stage pivot
Setup guide covering the Salesforce connection, the polling interval and the column mapping
Recorded walkthrough of an Opportunity edit landing in the sheet

Before you start

Salesforce Enterprise, Unlimited or Developer edition, or Professional with the API access add-on
Read access to Opportunities, Accounts and Users for the Salesforce user or Connected App you connect
Google account with edit rights to the destination sheet, connected to n8n through OAuth
Destination sheet with a header row; the package includes a template with the nine columns already named

Built for

Questions before you buy

Can I add custom Opportunity fields to the sheet?: Yes. Add the field's API name to the mapping node and a column with the same header to the sheet. The setup guide shows the two edits side by side; there is no limit beyond what a sheet row can hold.
What about Opportunities that already exist?: The package includes a one-time backfill workflow. Run it once and it pages through every open and closed Opportunity and writes each as a row; from then on the live workflow keeps them current.
Does deleting an Opportunity remove the row?: No. The trigger reports creates and updates, not deletes, so a deleted Opportunity's row stays until someone removes it. Closed Lost is the usual path in Salesforce, and that is an update, which the sheet does receive.
Will it run on Make or Zapier?: Both versions ship in the package. Zapier uses the Salesforce Updated Record trigger, two Find Record steps for the account and owner names, and a Google Sheets lookup that updates the row or creates it. Make's Salesforce Watch Records module feeds the same mapping. Polling intervals depend on the plan you hold on each platform.
Do I need a paid n8n plan?: Any n8n Cloud plan works, and so does self-hosted. Polls that find no changes do not count as n8n executions, so the run count tracks how often Opportunities change rather than the polling interval.

Nearby on the shelf

Whole catalog