hello everyone,
I tried an automation who generate image from replicate to google drive. My problem is the image don’t be generated, it’s arrive in the google drive and when i open it i have this message : {“title”:“Unauthenticated”,“detail”:“You did not pass an authentication token”,“status”:401}
the lora is public and i tried with several tokens api i generated for solving the problem. In the 6 module HTTP make a request, i tried Token or Bearer. Always the same result.
Steps taken so far
the lora is public and i tried with several tokens api i generated for solving the problem. In the 6 module HTTP make a request, i tried Token or Bearer. Always the same result.
Are you seeing the file in the Google Drive outside of Make? Is module 11 the one giving the problem? If so, it could be that your module needs to be re-authenticated.
Yes, i’m seeing the file outside make, in the google drive. it’s just the picture don’t appears and instead, when i open the file generated in Google drive, i have this message
Hmm, I’m not sure. Try by making the file accessible to all (check in an incognito browser that you can access it) and try your scenario. If that works then there is definitely something wrong with you connectors.
I did a quick search with Perplexity and it said:
The error in Make saying “Unauthenticated”, “You did not pass an authentication token”, with a 401 status code typically means that the API request is missing the required authentication token in the request headers. This is a common cause of HTTP 401 Unauthorized errors, which occur when the request lacks valid credentials.
Common reasons for this error in Make include:
Not including an Authorization header with a valid bearer token or API key.
Using an expired or invalid token.
Passing authentication credentials in a wrong format or incorrect authentication method.
Calling the wrong API endpoint or environment without proper token access.
Forgetting to refresh tokens in OAuth flows.
To fix this error:
Verify that the API call includes the correct Authorization header, for example: "Authorization": "Bearer your_token".
Ensure the token is valid, not expired, and has the correct permissions (scopes) for the requested resource.
Check the API endpoint URL for correctness and HTTPS usage.
If using OAuth, confirm tokens are properly refreshed and passed on.
Review Make environment and API key settings to confirm access rights.
This error is essentially telling Make your request isn’t authenticated because it doesn’t contain a valid token needed to authorize the API call.
The endpoints comments don’t really matter, here, since Make takes care of that. I also don’t think the bearer comment is valid since I believe the Google connection uses OAuth.
But it clearly seems to be a problem with credentials. Another option you could look at is to create a new Google connection and try to use that one instead of the one you’re currently using to see if that fixes the problem.
