Youtube uploads automation

[DILSHER]

What is your goal?

I want to upload at least 50 videos on youtube daily. Each video file size is around 200MB.

What is the problem & what have you tried?

Hi everyone,

I’ve built a simple YouTube upload automation in Make.com with the following workflow:

The user enters the video details (Google Drive link, title, description, etc.) into a Google Sheet.
The Google Drive – Download a File module downloads the video.
The YouTube – Upload a Video module uploads it to YouTube.

The workflow itself works perfectly.

However, I’ve run into what seems like a major limitation. My understanding is that all paid Make.com plans include 5 GB/month of data transfer. In my use case, I expect to process around 20 GB of video data per day, so I’d exceed that limit very quickly.

Am I misunderstanding how the data transfer limit works, or is Make.com simply not designed for high-volume video upload workflows like this?

Has anyone built a similar system at scale? If so:

How did you handle the data transfer limitation?
Is there a better architecture that still uses Make.com?
Or is this the point where a custom uploader (using the YouTube API) becomes the better solution?

I’d really appreciate any advice from people who have tackled similar workflows. Thanks!

Screenshots (scenario flow, module settings, errors)

[Stoyan_Vatov]

Its 5GB for every 10k operations. You’d see it if you hover over the question mark next to Data transfer.

[Dmitrkoliga]

@DILSHER

What is your goal?

I want to upload at least 50 videos on youtube daily. Each video file size is around 200MB.

What is the problem & what have you tried?

Hi everyone,

I’ve built a simple YouTube upload automation in Make.com with the following workflow:

The user enters the video details (Google Drive link, title, description, etc.) into a Google Sheet.
The Google Drive – Download a File module downloads the video.
The YouTube – Upload a Video module uploads it to YouTube.

The workflow itself works perfectly.

However, I’ve run into what seems like a major limitation. My understanding is that all paid Make.com plans include 5 GB/month of data transfer. In my use case, I expect to process around 20 GB of video data per day, so I’d exceed that limit very quickly.

Am I misunderstanding how the data transfer limit works, or is Make.com simply not designed for high-volume video upload workflows like this?

Has anyone built a similar system at scale? If so:

How did you handle the data transfer limitation?
Is there a better architecture that still uses Make.com?
Or is this the point where a custom uploader (using the YouTube API) becomes the better solution?

I’d really appreciate any advice from people who have tackled similar workflows. Thanks!

For that volume, I’d seriously consider using Make only for orchestration and letting a custom service handle the actual YouTube uploads through the API. It keeps the automation simple while avoiding potential bottlenecks with large file transfers.