Why is my n8n YouTube Upload Node Failing with a 400 Error?

Below are some suggestions that might help narrow down the issue:

1. Validate the File Input

Make sure that the file you’re providing is being passed to the node as valid binary data. In many cases, an invalid or empty file input can cause YouTube to process the upload as a draft. Verify that:

• The video file is uploaded as binary data.
• The binary property name used in your workflow exactly matches the field expected by the YouTube node (often something like "data" or "file", depending on your configuration).
• The file is in a format supported by YouTube and isn’t empty or corrupted.

2. Check Node Parameters

Some parameters in the YouTube Upload operation may default to draft mode if not set correctly. In particular:

• Review the privacyStatus parameter. If it is set to "private" or "draft" by default, you might see the behavior you’re experiencing. Change it to "public" (or your intended status) as needed.
• Ensure that any additional metadata or parameters provided (such as title or description) are in valid format.

3. Verify Authentication and Configuration

Even though your issue appears to revolve around the file input, double-check that your credentials for the YouTube node are set up correctly. Poorly configured authentication can sometimes lead to a 400 error. Refer to the YouTube credentials documentation for guidance on proper setup.

4. Test with a Known Working File

To isolate the problem, try uploading a small, known-to-be-valid video file. This can help determine whether the issue is with the file input format, the file itself, or perhaps the way the binary data is transferred into the node.

5. Debugging the Request

The error message indicates a 400 Bad Request error. Although the error originates from Axios, it means that YouTube is rejecting the request. Consider the following:

• Log the binary data or file metadata before sending it to ensure everything is as expected.
• Enable additional logging or use a test HTTP request node to replicate the file upload against YouTube’s API (if possible) to isolate whether the problem happens in the request formatting or in the data handling.

By verifying the binary data, checking your parameter settings (especially the privacy status), and ensuring your file inputs are correctly configured, you should be able to resolve the issue or further pinpoint what’s causing YouTube to treat your upload as a draft.

If you continue to have problems, please provide more details about how you are passing the file into the node (for example, how the binary data is set up in your workflow) so we can offer more specific guidance.