n8n: upload a file to Google Drive from a URL

To upload a file to Google Drive in n8n, first get the file into the workflow as binary data, for a file at a URL with an HTTP Request node whose Response Format is File. Then add a Google Drive node with Resource File and Operation Upload, set Input Data Field Name to that binary field, and choose the Parent Drive and Parent Folder.

n8n behavior is quoted from its HTTP Request node and Google Drive file operations docs, read 2026-09-28. The last section covers generated videos, from Sume's Runs and results and Video Generation docs.

How do I download a file from a URL in n8n?

Use an HTTP Request node with Method GET and the file's URL. Under Options, add Response and set Response Format to File, then name the field in Put Output in Field (for example data). The next node receives the bytes in that binary field. Redirects are followed by default, and by default the node succeeds only on a 2xx response, so a missing file stops the workflow instead of uploading an error page.

How do I configure the Google Drive Upload operation?

Add a Google Drive node after the download and set these parameters:

How do I connect Google Drive to n8n?

Create a Google credential in n8n. The Google Drive node accepts both OAuth2 and a Service Account; n8n recommends OAuth2 as more widely available and easier to set up. On n8n Cloud, Managed OAuth2 lets you sign in with Google directly for the Google Drive node, with no Google Cloud Console setup.

How do I upload and share the file?

Sharing is a second Google Drive node with Operation Share, pointed at the uploaded file's id. Pick a Role (Reader, Commenter, Writer, and others) and a Type: User or Group by email, a whole Domain, or Anyone. Send Notification Email controls whether users or groups get an email. For review hand-offs, Reader or Commenter for named users keeps the file off the open web.

Which URL do I download for a generated video?

For a Sume Format run, download primary_output_url from the completed run. It is a durable, public media.sume.com URL, so the HTTP Request node needs no credential; copy a file from a URL to S3 lists the artifact fields worth keeping with a copy. Getting the finished run into n8n is covered in the Wait node guide.

For a POST /v1/videos job, download GET /v1/videos/{jobId}/content with your API key as a Bearer credential. The API reference says the route redirects to the video, and current code answers 302, which the node follows by default. Download a generated video from the API covers the route's errors.