New Lead
Poll for newly created Lead records accessible to your connected Salesforce user. Establish the initial baseline before creating your test lead.
Workflow template
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
Poll for newly created Lead records accessible to your connected Salesforce user. Establish the initial baseline before creating your test lead.
Create a spreadsheet and five column headers on the first run, then reuse that file in this workflow copy.
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
Five columns are prepared automatically. The sheet records selected lead metadata without copying contact details, descriptions or custom fields.
| Lead ID | Lead name | Company | Status | Created at (UTC) |
|---|---|---|---|---|
| 00Q000000000001EAA | Mara König | München Demo Studio | Open - Not Contacted | 2026-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
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.
Choose the Google account that will own the new log. No existing spreadsheet or manual header setup is required.
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.
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.
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.
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.
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.
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.