Pipedream Google Drive → n8n
6 Pipedream Google Drive actions and 3 event sources, and the n8n nodes they become. Converted nodes keep your configured values; expressions like {{steps.x.$return_value}} are rewritten to n8n expressions. Pipedream app slug: google_drive.
Actions
| Pipedream action | n8n | Fit |
|---|---|---|
| google_drive-upload-file | Google Drive file → upload | Check output |
| google_drive-create-folder | Google Drive folder → create | Direct |
| google_drive-download-file | Google Drive file → download | Check output |
| google_drive-find-file | Google Drive fileFolder → search | Direct |
| google_drive-add-file-sharing-preference | Google Drive file → share | Check output |
| google_drive-share-file | Google Drive file → share | Direct |
Triggers (event sources)
| Pipedream trigger | n8n | Fit |
|---|---|---|
| google_drive-new-files-instant | Google Drive Trigger fileCreated | Check output |
| google_drive-new-or-modified-files | Google Drive Trigger fileUpdated | Check output |
| google_drive-changes-to-specific-files | Google Drive Trigger fileUpdated | Check output |
Credentials
Create a Google Drive credential in n8n (type googleDriveOAuth2Api). Converted nodes reference it by name, so n8n links it on import when the names match. Pipedream connected accounts can't be exported and are deleted by April 30, 2027.
What "Fit" means
Direct: same operation, same inputs. Check output: the n8n node returns a different JSON shape, so later steps that read its result need a look. Partial: some options have no n8n equivalent. Mappings verified on 2026-10-13 against the Pipedream registry and n8n source.
Questions
Does n8n have a Google Drive node?+
Yes. 6 of the 6 Pipedream Google Drive actions listed here map to a native n8n node.
Will my Pipedream Google Drive connection move to n8n?+
No. Pipedream exports only an account ID, never the token, and deletes connected accounts by April 30, 2027. Create a Google Drive credential in n8n (type googleDriveOAuth2Api) and select it on the converted nodes.
Are Pipedream Google Drive triggers supported in n8n?+
3 of the 3 Pipedream Google Drive event sources listed here have an n8n trigger node. The rest are rebuilt with a Schedule Trigger that polls the API, or a Webhook node.
What happens to code steps that call the Google Drive API?+
Code steps keep working through a compatibility layer, and tokens read via this.<app>.$auth move to a secrets block in the Code node. Steps that use an npm SDK are rewritten to plain HTTP calls so they run on n8n Cloud.