Can Retool call a Cloud Run backend REST API service?

[dheerajpanyam]

Retool is a low code / no code tool to quickly build Admin dashboards. I am trying to invoke a Cloud Run  backend API service hosted on GCP using service account key which doesn't seem to be working. I am getting a 401 unauthorized access error. The SA has cloud run invoker role and it is the same SA that CR service runs as.

[ronnelg]

Hi @dheerajpanyam, 

What authentication method are you using? If Google Service Account, what Service Account OAuth Scopes you are using? You can try to remove the scope, leave it blank, save changes and then try to run it again. You can check this post for your reference.

Ensure also that your provided credential to Retool is correct. 401 unauthorized error potential causes are invalid authentication credentials provided or incorrect resource credentials.

If the issue still exists, you can check the Retool Community for other discussion that may help you with.

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.

[dheerajpanyam]

Hi @ronnelg . Thanks so much for your answer appreciate it very much. Regarding the SA OAuth scopes , i tried with cloud-platform which is the broadest and also without any scope, in both cases it failed. I am using the Service Account based authentication method. Just to confirm the SA key that i am passing to Retool is the SA key associated with the CR service, is this correct or do i need to create a new SA?

[ronnelg]

Yes, that is correct. But, you can also try to create a new SA with key and Cloud Run Invoker role permission and see if it works.

[dheerajpanyam]

Thanks Sir @ronnelg 

[dheerajpanyam]

Hi @ronnelg  We tried all the options you recommended but it is not working. We posted in the Retool community a week ago and waiting for an answer. I totally understand that this is a 3rd party tool and hence scope is outside google cloud community and appreciate your response. Any further ways to troubleshoot from logs etc?