OAuth2 doesnt let me set url headers for access token url

I am trying to setup a resource on retool that lets me send messages through the gotoConnect API. They have OAuth 2.0 authroization protocol.

I've tried using the OAuth 2.0 generic authentication method with all the correct information however it says invalid client sectret. I've made sure multiple times that I have the right one.

I think becuase the way to get an access token for gotoconnect is to provide in the header the base64 encoded version of the client id and client secret.

currently retool doesnt let me do that and I dont think I can implement it through a custom flow. Please help me. This is what i tried:

2 Likes

Hi @Layth! Welcome to the community. :slightly_smiling_face:

I wasn't aware of this until just the other day, but there's a toggle in the Beta menu that will configure your OAuth2 queries to do exactly what you need:

Hopefully that helps! Let me know if you have any follow-up questions. :+1: