How to Setup a Google OAuth 2.0 API Connection - Bubble.io Tutorial

[@neko_reco]

6:05 6:56-8:07 クライアントIDとシークレットID 8:35 bubble側のワークフロー 9:32 distination 11:36 ボタン押すヨォ！！ 12:56 ta-ta-tata-♩ 13:46 API Connector

[@daczito]

I havent seen your most recent videos, but based on this one, you have a lot of room for improvement in your educational skills. Its not easy to understand what is going on, and why we are doing the specific steps, where those values came from and what its used for.

[@NoCodeAcademy]

Hey appreciate the feedback, it's been noted and upgrades to the structure of these type of tutorial videos is under way, kzbin.info/www/bejne/o2XZfqt6abWGl80. Any feedback is welcome, I appreciate the opportunity to get better.

[@sambamurthys5639]

Hey please reply me how to add scopes under an organization because it shows only limited scopes

[@parabunx]

And what about document AI ? in this case it seem there is no scope...

[@agrikolas3133]

How can I fix it? "There was an issue setting up your call. Raw response for the API Status code 400 { "error": "invalid_grant", "error_description": "Bad Request" }"

[@NoCodeAcademy]

Hi thanks for the comment, could be any of these: Invalid Authorization Code: The authorization code you are using might be invalid, expired, or already used. Authorization codes are typically short-lived and can only be used once. Redirect URI Mismatch: The redirect URI provided in your token request must match the one used during the authorization request. Any mismatch will cause an "invalid_grant" error. Invalid Client Secret: The client secret provided in the token request may be incorrect. Expired Refresh Token: If you are using a refresh token to obtain a new access token, the refresh token might be expired or revoked. Clock Skew: There might be a significant difference between the time on the server issuing the token and the time on the client requesting it. OAuth 2.0 implementations often include checks for the token's validity period. Incorrect Grant Type: The grant type specified in the token request might not be valid for the client.

[@AlenaMcLucas]

I had the same issue, turns out I'd taken too much time in between grabbing the authorization code and then initializing this call (pizza called haha). After generating a new code again using his same previous steps (using the app preview to generate it), I was able to get it working. Hope this helps!

[@JoshComninellis]

@@NoCodeAcademy I am having this SAME problem and I can't seem to figure it out. I actually did all of the steps and everything was working correctly at first. I initialized the call and the call came back correctly and everything. Then I went to your next video about refresh tokens (kzbin.info/www/bejne/gXmog4B5h9SlfpY) and started that process. I was having trouble following along so I changed the name of my API to match yours in the video, just to make it easier on me. Once the name of my API was changed, it asked me to reinitialize the call in bubble. I did that and it came back with this same error mentioned above: Raw response for the API Status code 400 { "error": "invalid_grant", "error_description": "Bad Request" } I went back and checked ALL of the items you listed above. I redid the authorization and tried a new code at least 3-4 times. I checked all of my credentials with Google Cloud console. I even remade the API from scratch just to see if that might help. But now I consistently get this code. Really appreciate you making this video. ANY help would be so appreciated.

[@JoshComninellis]

@@NoCodeAcademy I completed the steps in this video and successfully got the API working as expected. However, while working on the second video-the one involving the refresh token-I renamed the API call to improve clarity while following along with the process. After doing so, I received a prompt to reinitialize the call, which I did. Unfortunately, after reinitializing, I received the same error this user shared: Raw response for the API Status code 400 { "error": "invalid_grant", "error_description": "Bad Request" } I tried all of the suggestions you list above (except the last one, which I don't yet understand) and the problem persists. I have recreated my access token and updated the call at least four times just in case. No luck. Any suggestions would be so so so appreciated. Been banging my head against the wall with this for a while now.

[@toba-bonjour]

About the access oken, I think it is is only available 3600 seconds with google api services which means you must redo this copy and past after 1h. Does the API connector plugin offer an authentication that automatically handle new access token? One more time, thanks for the video :)

[@NoCodeAcademy]

Hey that's correct, it's only 3600 seconds. But there is a refresh token which this video doesn't go into because it's already quite long. The purpose of this video is so you can setup and test your implementation. But don't worry here's next steps (a) usually, you build a check into the system of if the token has expired and then you wait until you app user attempts an action to that requires the API and then you refresh the token (b) kzbin.info/www/bejne/aqeTc36oidiarpo I haven't viewed this but it states he goes into a refresh token. If not, I plan to release a video on this topic but that's what I have for now. Good luck.

[@toba-bonjour]

@@NoCodeAcademy You're a legend, thanks!

[@johnmalcom5409]

@@toba-bonjour exactly my question: how do I build a few calls that need Auth0 and don't have to re-authorize each time. Did this video help?

[@GabrielRibeiro-nb3hk]

Thanks for the video, but I'm having an error in the e-mail sing in authorizing screen, this error: "Error 400: invalid_request Request details: redirect_uri=xxxxx". Anybody does know how to fix it?

[@NoCodeAcademy]

Hi Gabriel, check that your URI in the Google Cloud Console 7:25 matches the URI redirect in your auth URL 11:11. Hope that helps.

[@sapiensscience8716]

Hey friend, can you insert the video conference?

[@NoCodeAcademy]

Hi I'm not sure what video conference you're referencing? Could you please add some context?

[@ELABATSHi]

But i have an issue that users data not saving in user built in with bubble and its save with new data type . It will be difficult to recignize each user will login to get and display his data separately on bubble and each time user login it saves same information again . Do you have any solution to let the data of any user login yo be save into user built in data ? Thank you

[@NoCodeAcademy]

Hi thanks for your comment. To confirm my understanding, when someone logs via this Google OAuth process with an account of [e-mail], then logs out and then logs back in again via Google OAuth process as [e-mail] you are seeing Bubble create duplicate records for this login?

[@zzzdzzdz]

How to use it when i use google run and dont have scopes

[@NoCodeAcademy]

Hi thanks for the comment. I'm not very familiar with Google Run -- I think you what you're referring to is called Google Cloud Run ?? -- but to point you in the right direction, under APIs & Services in your Google Cloud Console Account, you'll see the Credentials area. When you click the Create Credentials button, you'll choose Service account instead of the OAuth client ID. You'll also want to enable the Cloud Run API for your project by navigating to the API Library and searching for "Cloud Run API". Click on it and enable the API for your project. Then there are some other steps that include: - When setting up Service account, you'll be asked to grant the necessary permissions to your service account. Select the "Cloud Run Admin" role from the dropdown and click on "Continue". - On the next page, you can optionally grant additional permissions or create a key for the service account. For Bubble.io's API Connector, you don't need to create a key. - Once the service account is created, click on the service account email address to view its details. - In the service account details page, click on the "Add Key" button and select "Create new key". - Choose the key type as "JSON" and click on "Create". This will download a JSON file containing the service account key. - Go back to the Bubble.io API Connector editor and click on the "Configure OAuth" button. - In the "Configure OAuth" dialog, click on "Upload JSON file" and select the JSON file you downloaded in the previous step. - After uploading the JSON file, Bubble.io will automatically extract the required parameters. - Save the OAuth configuration and return to the API Connector editor. Now, you can configure the specific API requests within the API Connector, providing the necessary endpoint, method, and parameters as required by the Cloud Run API. When making API calls to the Cloud Run API, Bubble.io's API Connector will automatically handle the authentication process using the OAuth configuration you set up. Good luck.

[@neko_reco]

Thank you!! I finally got it!!!

[@minimanny54]

There is great info in this video, but I think you'd benefit your viewers by having a script and being very deliberate about where you are clicking

[@NoCodeAcademy]

Hey thank you for the feedback, newer videos are getting better at this.

[@husniheartnetGaming]

Thank you so much sir!

[@frontend_ko]

okay thanks

[@danielhen]

stop the clicking!! its imposable to follow 😵‍💫

[@NoCodeAcademy]

Hey Danial. If it feels like a lot going on, it's because there is! Best for these very techy videos to plan to run through them a few times to digest. 💪Good luck!

[@danielhen]

@@NoCodeAcademy you right, but still I think it will help if you will be more sure about what you want to do and where you need to go. GL 🙏

[@tommathews5484]

Too much stream of consciousness. Gets in the way of understanding.

[@NoCodeAcademy]

Hey thanks for the comment. Yep agreed, this was one of the earlier ones on the channel ✌.

[@bordersj]

After about the 15:00 mark it seems like you got exhausted and just wanted to get the video over with. Explanation just went completely schizophrenic

[@NoCodeAcademy]

Hey thanks for the comment. Haha you're right! This was early on in making really technical API videos, they're much better now if you're interested in other ones like Midjourney, Claude AI or other cool tools you'd want to use in Bubble. Cheers.

[@bordersj]

@@NoCodeAcademy but I also have to say a lot of your videos have saved me a ton of time and grief so overall I appreciate these videos you do!