Connect to Google services using a custom OAuth client

to connect some restricted google services, like google drive or google sheets , to make, you need to create your own project in google cloud platform and a custom oauth client the following procedure is intended for personal use ( @gmail and @googlemail com users) internal use (google workspace users who prefer to use a custom oauth client) to connect, you must have a https //accounts google com/signin configure a google cloud platform project t o configure a google cloud platform project, follow these five steps /#create a google cloud platform project /#enable apis /#configure your oauth consent screen /#create your client credentials /#establish the connection inmake create a google cloud platform project to create a project in your google cloud console log in to the https //console cloud google com/ using your google credentials on the welcome page, click create or select a project in the next window, click new project in the upper right corner change the default project name and project id , if needed select the location for your project, and click create on the top panel, next to the google cloud logo, click select a project in the next window, click the project you just created you'll now see the google cloud platform project you've created o n the top panel, next to the google cloud logo to create a new project or work in the existing one, you need to have the serviceusage services enable permission if you don’t have this permission, ask the google cloud platform project owner or project iam admin to grant it to you enable apis to turn on the apis your google application needs in the left sidebar of the google cloud platform, click apis & services > library search for the api you need for your project (e g , google sheets, google drive, etc ) for the information on apis for particular apps, look for the required app in the https //apps make com/ click the relevant api (e g , google sheets api) c lick enable your api is now enabled configure your oauth consent screen to set up the oauth consent screen in the left sidebar of the google cloud platform, click apis & services > oauth consent screen click get started in the overview section u nder app information , enter make as the app name, enter your gmail address, and click next under audience , select external , and click next for more information regarding user types, refer to https //support google com/cloud/answer/9110914#exceptions ver reqts under contact information , enter your gmail address, and click next under finish , agree to the https //developers google com/terms/api services user data policy?authuser=1 , and click continue , then create in the next window, click create oauth client you'll be redirected to the clients tab you can skip it for now or refer to the /#create your client credentials section to configure it i n the branding section u nder authorized domains, click +add domain a dd make com and integromat com click save in the audience section click publish app to update the project status to in production if you want the project to remain in the testing publishing status, click +add users and enter your gmail address under test users publishing status testing if you keep your project in the testing status, you will be required to reauthorize your connection in make every week to avoid weekly reauthorization, update the project status to in production in production if you update your project to the in production status, you will not be required to reauthorize the connection weekly to do that, go to the google auth platform , the audience section, and click publish app if you see the notice needs verification , you can choose whether to go through the https //support google com/cloud/answer/13463073?authuser=1\&visit id=638718595933013017 1855034908\&rd=1 for the app or to connect to your unverified app currently, connecting to unverified apps works in make, but we cannot guarantee that google will allow connections to unverified apps for an indefinite period for more information regarding the publishing status, refer to the publishing status section of https //support google com/cloud/answer/10311615#zippy= in the data access section under data access , click add or remove scopes under update selected scopes , s earch for and select the required scopes from the list alternatively, enter the required scopes one by one and click add to table under manually add scopes click update for the google sheets app, for example, you'd need to add the following scopes https //www googleapis com/auth/spreadsheets https //www googleapis com/auth/drive e ach app, however, requires its own set of scopes to find the correct scopes, go to the app's page in the https //apps make com/ and refer to the configure your oauth consent screen section click save your oauth consent is now configured create your client credentials to generate the client id and client secret needed for authentication in the left sidebar of the google cloud platform, click apis & services > oauth consent screen go to the clients section, and click +create client under create oauth client id in the application type dropdown, select web application in the name field, update the name of your oauth client this will help you identify it in the console afterward under the authorized redirect uris, click + add uri and enter the required redirect uri f or the google sheets app, for example, you would need https //www integromat com/oauth/cb/google/ each app, however, requires different redirect uris to find the correct one, go to the app's page in the https //apps make com/ and refer to the create your client credentials section click create you'll see a message that the oauth client has been created c opy your client id and client secret values, and store them in a safe place you will use these values in the client id and client secret fields in make establish the connection in make to establish the connection in make log in to your {{product name}} account, add a google app module to your {{scenario singular lowercase}} , and click create a connection optional in the connection name field, enter a name for the connection switch on the advanced settings toggle and enter your google cloud platform project client credentials click sign in with google if prompted, authenticate your account, grant all requested permissions, and confirm access you've successfully created the connection and can now use the google app modules in your {{scenario plural lowercase}} if you want to make changes to your connection in the future, follow the steps https //help make com/connect an application#tn2pj common problems \[403] access not configured t his error message may appear when you haven't enabled the corresponding api in your google cloud platform to enable the api, c omplete the steps explained /#enable apis if the problem persists, delete the previous connection and connect your google app to {{product name}} with your oauth credentials once again authorization error error 403 access denied this error message may appear if you keep your google project in the testing status and haven't added a test user email address associated with the google account you want to connect to make as a test user to add the test user or change the status of your app, complete the step 3 explained /#configure your oauth consent screen then go to connections in the left sidebar in {{product name}} , and click the reauthorize button if the problem persists, delete the previous connection and connect your google app to {{product name}} with your oauth credentials once again failed to verify connection 'my google restricted connection' status code error 400 this error message may appear if y our connection has expired and is no longer valid you need to reauthorize the connection this error affects non google workspace accounts for more details, please refer to the https //developers google com/identity/protocols/oauth2#expiration due to google's updated security policy, unpublished apps can only have a 7 day authorization period after the oauth security token expires, the connection is no longer authorized, and any module relying on it will fail solution 1 to avoid weekly reauthorization , you can update the publishing status of your project if you update your project to the in production status, you will not be required to reauthorize the connection weekly to c hange the status of your project to in production , follow the step 5 explained /#configure your oauth consent screen here's a summary in the left sidebar of the google cloud platform, click apis & services > oauth consent screen switch to the audience section, and click publish app to update the project status to in production if you see the notice needs verification , you can choose whether to go through the https //support google com/cloud/answer/13463073?visit id=638357423877979226 2405331664\&rd=1#exceptions ver reqts for the app or to connect to your unverified app currently, connecting to unverified apps works in make, but we cannot guarantee that google will allow connections to unverified apps for an indefinite period solution 2 if you keep your project in the testing status, you will be required to reauthorize your connection in make every week to reauthorize your google connection log in to make in the left sidebar, click connections find your google connection and click the reauthorize button error message it is not possible to use restricted scopes with customer @gmail com accounts this error message may appear if you haven't added the required scopes for your google app to add the scopes, complete steps 6 and 7, as explained /#configure your oauth consent screen error 400 redirect uri mismatch this error message can appear if you haven't added the required redirect uris for your google app verify you're using the required r edirect uris as explained in step 4 /#create your client credentials it may also happen that google doesn't instantly recognize the redirect uri used for the authentication once verified that you're using the proper redirect uris, wait for some time after creating your google cloud platform project then, try to connect the google app with your custom oauth credentials once again error 403 insufficient permission verify you've added all the required scopes in the google cloud platform project for the app you're using, as explained in step 6 /#configure your oauth consent screen then, r eauthorize your google connection by following these steps log in to make in the left sidebar, click connections find your google connection and click the reauthorize button 100 logins limit per day has been reached according to the https //developers google com/identity/protocols/oauth2#expiration , there’s a limit of 100 refresh tokens per google account per oauth 2 0 client id if the limit is reached, creating a new refresh token automatically invalidates the oldest refresh token without warning this limit does not apply to service accounts this happens rarely, but when it does, we recommend creating another oauth client