Generating a Google Client ID & API Key


Connecting to Google Drive with SuperSync Files



In order to setup a connection to Google Drive, you will need to generate a Google Client ID and API Key. SCS Cloud has opted not to setup a managed Google Connector instead allowing administrators to control their own security settings and manage their own API Keys. 


This just means a few more setup steps to get started but they only need to be done once.


First need to login to the developer console here:


https://console.cloud.google.com/




Creating the Project



Make sure to select your correct organization account/domain in the top left under which the shared Google Drive resides. 


Once the correct organization is showing you can select "APIs & Services" from the home page. 

 




On the credentials page, create a new Project for the SuperSync connector:





Give the project a name and make sure the correct Organization is selected and then click the create button. 


Adding Access to Google Drive


To add access for Google Drive, click on the Enabled APIs and Services menu and then click the link to Enable APIs and Services.




Use the search bar to find the Google Drive API and click on the tile. 


From here you can enable it for the project by clicking the Enable button. 






Generating an API Key



Once the Project has completed generating, you can navigate back to the Credentials Screen and choose the menu to Create Credentials. 




Select API Key.




The generated API Key will be required to enter into NetSuite at a later point. 



After generating the key you can open the entry to further configure it. 





Restrict the key usage to websites and make sure to make an entry to restrict it to just the NetSuite domain. Even better is to restrict it to your specific account subdomain on NetSuite.




You can optionally restrict the key to only be able to use the Google Drive API incase other APIs are enabled for the project in the future for other integrations. 




Generating an OAuth Client ID



The last step in the Google configs in the developer console is to generate a Client ID. This can be done back on the Credentials page by selecting OAuth client ID





You may first be prompted to setup a consent screen as part of this. Click the Configure Consent Screen button. 





Select Internal user types and click Create.


 



You will need to configure the "Appinformation. You can name this as you like depending on what will make the most sense to the users. You can use the SuperSync Files brand name and logo (which can be provided) or as an alternative you can just name the app after your company name and "NetSuite". This is what users will see when they need to Authorize the App to Connect to Google from NetSuite. 


Make sure to set the Authorized Domain correctly. Again, it is better to enter the account ID subdomains for your production and Sandbox accounts separately rather than the general NetSuite domain.



Once setting up the consent screen is complete, you can take the final step of actually generating the Client ID - jump back to the Credentials Menu as shown at the top of this section and select a new OAuth Client ID.


When the next screen comes up, choose Web Application




When you are prompted to enter the JavaScript Origins and redirect URIs, again use you NetSuite account domains. 




In the top right hand side of the page, your Client ID will be shown. Make sure to note this down to enter back into NetSuite along with the API Key copied earlier. When done click Save. 






Adding Credentials to NetSuite


The Client ID and API Key need to be updated in NetSuite by going to the menu under SuperSync Files >  Configs > Connections


You can create a new connection record and paste in the API Key and Client ID. You will also need the base folder ID for the Google Drive Shared folder that all files will reside in (blue arrow). This is covered separately.






Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article