Pipedream Google Sheets steps in n8n

Google Sheets is where many Pipedream workflows end: a form, a webhook or an LLM step produces a row, and the row goes into a sheet. n8n has a native Google Sheets node and a Google Sheets Trigger, so this is one of the cleanest apps to move.

The n8n side

Google Sheets node (n8n-nodes-base.googleSheets):

• Document: Create, Delete
• Sheet Within Document: Append Row, Append or Update Row, Clear, Create, Delete, Delete Rows or Columns, Get Row(s), Update Row

Google Sheets Trigger: events Row added, Row updated, Row added or updated. It checks the sheet on a schedule (Poll Times), so it is not instant like Pipedream's "(Instant)" sources.

What maps where

Pipedream (app google_sheets)	In n8n	Status
Add Single Row	HTTP Request → values:append with the Google Sheets credential	automatic
Add Multiple Rows	HTTP Request → values:append, rows as an array	automatic
Get Values in Range	HTTP Request → values/{range}	automatic
Update Row	HTTP Request → PUT values/{sheet}!A{row}	automatic
New Row Added, New Updates (and Instant variants)	Google Sheets Trigger, event Row added / Row updated	automatic, pick the tab
Conditional formatting, protected ranges, comments	HTTP Request to the Sheets API, or Google Sheets node where an operation exists	manual

The converter writes HTTP Request nodes rather than the Sheets node on purpose: Pipedream's actions take A1 ranges and raw arrays of values, and the Sheets API call keeps that behaviour exactly (valueInputOption=USER_ENTERED, rows inserted, not overwritten). If you want the column-mapping UI of the native node, swap the node after the first green run.

Credentials

Pipedream's Google connection does not move. In n8n create a Google Sheets OAuth2 credential:

1. In Google Cloud, enable the Google Sheets API and the Google Drive API.
2. Create an OAuth client (Web application) and add the n8n redirect URL shown in the credential window.
3. On n8n Cloud you can use the managed "Sign in with Google" instead; self-hosted needs your own client.
4. A Service Account also works for Sheets: share the spreadsheet with the service account email.

Self-hosted behind a domain: N8N_EDITOR_BASE_URL and WEBHOOK_URL must match the redirect URL you registered, or the OAuth callback fails.

Typical migration: form to sheet

Pipedream: HTTP trigger (form post) → Add Single Row → Gmail send. n8n: Webhook → Code (trigger) → HTTP Request (Sheets append) → Gmail. Create two credentials, move the form's webhook URL to the n8n production URL, send one test submission.

Pitfalls

• API quota. The Sheets API allows 300 read and 300 write requests per minute per project, and 60 per minute per user. A batch request counts as one. n8n runs a node once per item, so 500 incoming items mean 500 append calls; aggregate rows first and send one Add Multiple Rows call.
• Header changes. If someone renames a column after you set up the native node, n8n's common-issues page says to re-select the mapping mode.
• Arrays in cells. Convert arrays and objects to JSON strings before appending.
• 7-day tokens. An External Google Cloud app in Testing status loses tokens after 7 days. Publish it.
• Trigger latency. Pipedream's instant source reacted to edits; the n8n trigger polls. Set Poll Times to every minute if timing matters.

How to move your Google Sheets workflows

1. Export from Pipedream (official export or GitHub Sync).
2. Upload on /convert for the free report: step-by-step status, credentials to create, manual items.
3. Download the n8n JSON. 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

More context: Pipedream to n8n migration guide and the code step checker for code steps that use the googleapis package. Related: Google Drive, Airtable, Gmail.