Salesforce logo
Google Sheets logo

Workflow template

Log new Salesforce leads in Google Sheets

Keep a Google Sheets activity log of new Salesforce leads. The first event creates the spreadsheet and five headers; later events append rows to the same file.

How it works

From a new Salesforce lead to an activity-log row

1 Trigger · 2 Actions
Salesforce1 · Trigger

New Lead

Poll for newly created Lead records accessible to your connected Salesforce user. Establish the initial baseline before creating your test lead.

Google Sheets2 · Action

Create the Salesforce lead log once

Create a spreadsheet and five column headers on the first run, then reuse that file in this workflow copy.

Google Sheets3 · Action

Log the new Salesforce lead

Append the lead ID, name, company, status and creation timestamp as a new row. RAW input keeps formula-like names as literal text.

The result

A running record of newly created leads

Five columns are prepared automatically. The sheet records selected lead metadata without copying contact details, descriptions or custom fields.

Fictional lead data illustrating the five columns created by this workflow.
Lead IDLead nameCompanyStatusCreated at (UTC)
00Q000000000001EAAMara KönigMünchen Demo StudioOpen - Not Contacted2026-09-21T09:00:00.000+0000

Illustrative data. Review who can access the generated spreadsheet: its readers can see the included lead metadata.

Before activation

Set up your workflow

  1. Connect Salesforce

    Select a Salesforce account with API access and permission to read the Lead records you want to log. Choose a polling interval appropriate for your account.

  2. Connect Google Sheets

    Choose the Google account that will own the new log. No existing spreadsheet or manual header setup is required.

  3. Wait for the first poll, then create a lead

    Activate the workflow and let its initial poll establish a baseline. Create a fictional lead and wait for the next poll. Create a second lead to check that another row appears in the same spreadsheet.

Details and limitations
  • New leads after the baseline. Existing leads are not backfilled. Later edits, conversions and deletions do not update earlier rows. Polling introduces a delay, and values are read when the poll runs.

  • Only five selected fields. Email addresses, phone numbers, postal addresses, descriptions, notes, owners and custom fields are not mapped into Sheets. The included name and company still require appropriate spreadsheet access.

  • One file per workflow copy. Testing the creation Action also creates its file. Later events reuse it. Changing creation settings after the first run requires a new creation step; a deleted spreadsheet is not silently replaced.

  • An activity log, not CRM synchronization. RAW input preserves formula-like names as text. Manual reruns can append duplicate rows. The workflow does not synchronize later Salesforce changes or write spreadsheet edits back to Salesforce.

Questions about this template

Do I need to create the spreadsheet and headers first?

No. The first event creates the file with Lead ID, Lead name, Company, Status and Created at (UTC) columns. Subsequent events reuse it in the same workflow copy.

Will this import my existing Salesforce leads?

No. The initial poll establishes a baseline. Create a new lead after that baseline to test the workflow, then wait for its next scheduled poll.

Will changed lead statuses update existing sheet rows?

No. This is a one-way log of new leads. Values are read at polling time, but later edits, conversions and deletions do not update rows already written.

Which Salesforce fields are copied?

Only the lead ID, name, company, status and creation timestamp. Email, phone, postal address, descriptions, notes, owner and custom fields are excluded. Review access to the generated spreadsheet.