https://linen.dev logo
YOUTUBE_UPLOAD_VIDEO - error: 'Location header no...
# 🖥│support-forum
m
Hello! I am trying to execute video upload for connected account to youtube, but i am getting this error: Upload result: { data: {}, error: 'Location header not found in response', successfull: false, successful: false, logId: 'log_6QuvfsG5hMQJ' } I execute it like this: const result = await entity.execute({ actionName: 'YOUTUBE_UPLOAD_VIDEO', connectedAccountId: youtubeConn.id, params: { title, description, tags, categoryId, privacyStatus, videoFilePath: videoFile.filepath, }, }); in console.log: 2025-07-25T18:23:08.269Z - Initializing Composio w API Key: [REDACTED] and baseURL: https://backend.composio.dev entity id 56effceb-9bcd-43d8-bc88-a0d7e6894827 Using YouTube connection: 6b12139f-cdd1-4a7b-a043-89468eceed6d Upload params: { title: 'My Test Video', description: 'Uploaded from Postman / cURL', tags: [ 'postman', 'test', 'upload' ], privacyStatus: 'public', categoryId: '22', ReadStream { fd: 48, path: 'C:\\Users\\user\\AppData\\Local\\Temp\\qqw3scf6z10nofu15cogznzqz' ..... } How to solve this error? Thanks!
c
Hi Max, Could you share how you are trying to execute the Tool
YOUTUBE_UPLOAD_VIDEO
? This action can only be used via SDK as it has a parameter
videoFilePath
. Thanks!
c
The
YOUTUBE_UPLOAD_VIDEO
can only be used via SDK. It uses your file path, which is intended to be local, so it cannot be executed through the user interface or using Curl.
m
Hi! Just to clarify — I’m not using Postman or curl directly for the YOUTUBE_UPLOAD_VIDEO action. I’m calling it from the backend using the official composio-core SDK on a Node.js server (Next.js API route), and I’m passing a valid videoFilePath that points to a real file saved under /tmp. However, the response I’m getting is: "error": "'access_token'", "successful": false The connectedAccount for YouTube does exist, but it seems like the access token is missing or invalid. Could you please check this log for more details? logId: log_EyXI99U-Om0Y I'm using the following authConfig.id: ac_fJK5gR5owHm4 Could you confirm that this config includes the required scopes for video uploads (e.g., youtube.upload) and that the token is valid? Thank you!
c
Hi Max, Could you please provide some details about the AuthConfig? Is it set to Default or Custom? Also, have you made any modifications to the scopes?
c
Thanks for the information, we'll look into this and update you.
We were able to reproduce the issue, I’ve escalated it to the engineering team. They’ll be working on a fix and I will update you when it’s live.
m
Do you know when it will be fixed or how to make it work correctly? Maybe if I enable all scopes that are suggested by default from the very beggining?
c
Hi Max, it seems like there is a bug on our end. The team is working on a fix and will update you. Thanks for the patience!
Hey, sorry for the delay in getting back. This issue has been fixed
3 Views