Pipedream Google Drive steps in n8n

Google Drive steps in Pipedream usually watch a folder or move files: a new invoice PDF lands in a folder, a step downloads it, another sends it to an LLM or an accounting tool. n8n has a native Google Drive node and a Google Drive Trigger. The real difference is how files travel: Pipedream used /tmp, n8n uses binary data on the item.

The n8n side

Google Drive node (n8n-nodes-base.googleDrive):

Resource	Operations
File	Copy, Create from Text, Delete, Download, Move, Share, Update, Upload
File/Folder	Search
Folder	Create, Delete, Share
Shared Drive	Create, Delete, Get, Get Many, Update

Google Drive Trigger: polls Drive for matching changes (for example a new file in a folder). A manual test run returns the latest match, or an error if nothing matches.

What maps where

Pipedream (app google_drive)	In n8n	Status
Upload File	Google Drive → File → Upload (binary input)	manual
Download File (to /tmp)	File → Download; the file becomes binary data	manual
Search Files / Find File / Find Folder	File/Folder → Search	manual
Copy File, Move File	File → Copy / Move	manual
Create New File From Text	File → Create from Text	manual
Add Comment, permissions edge cases	HTTP Request to the Drive API with the Google Drive credential	manual
New Files (Instant), New or Modified Files (Instant)	Google Drive Trigger, polling	manual
Code step using googleapis and this.google_drive.$auth.oauth_access_token	Code node; token becomes GOOGLE_DRIVE_OAUTH_ACCESS_TOKEN, package listed	automatic, review

Google Drive actions are not in the converter's automatic list. They show up in the free report with their props (file ID, folder ID, name), so you can rebuild each one with a single node.

/tmp versus binary data

The biggest rewrite with Drive is not the API call but the file handling. A typical Pipedream code step reads /tmp/invoice.pdf written by the download step. In n8n there is no shared /tmp between nodes; the download node outputs an item with binary.data, and the next node (Gmail attachment, HTTP Request multipart, Extract from File) reads that property. When a code step opens /tmp files, the converter lists it in the report as a manual item.

Credentials

Options from n8n's Google docs:

• OAuth2 (single service): on n8n Cloud a managed "Sign in with Google"; self-hosted needs your own OAuth client with the Drive API enabled.
• Service Account: supported by the Drive node and trigger. Share the folders with the account's email.

Self-hosted: the OAuth redirect URL registered in Google Cloud must match your public n8n URL (n8n's Drive common-issues page covers this).

Typical migration: invoice folder to accounting

Pipedream: New Files (Instant) in folder → Download File → code step (send PDF to an API). n8n: Google Drive Trigger (folder) → Google Drive → Download → HTTP Request (multipart, binary field data).

Pitfalls

• 7-day tokens. An External Google Cloud app in Testing status loses its tokens after 7 days. Publish the app.
• "Google hasn't verified this app". Expected for your own OAuth client; continue through the warning or verify the app.
• Latency. Pipedream's Instant sources used Drive push channels, which expire (by default after an hour, at most a day for files and a week for changes) and must be renewed. n8n's polling avoids renewal but adds up to one poll interval of delay.
• Large files. Binary data is held in memory by default on self-hosted n8n; for big files set N8N_DEFAULT_BINARY_DATA_MODE=filesystem.

How to move your Google Drive workflows

1. Export the workflows from Pipedream.
2. Upload on /convert: the free report marks /tmp usage and Drive steps.
3. Download the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

More in the Pipedream to n8n guide; check /tmp-heavy code in the code step checker. Related: Google Sheets, Google Docs, AWS S3.