Out of the box, Fusebit's Google Integration uses our own demonstration application in Google. This is only done to make it easier for you to get started, however you will need to register your own Google App for use in Production.
Google also requires a fairly extensive review process before publishing an application. Choose your scopes wisely, to simplify the process of publishing your app.
Go to https://console.cloud.google.com/ and create an account, if necessary.
Create a new project using the project drop-down in the top left:
New Project option in the dialog:
Fill in the dialog window with the name of your project, and click Create.
- Select the project, and choose the Library option from the API & Services side bar:
- Then enter 'Drive' in the search window, and select the Google Drive API option, and click 'Enable':
- Select the
OAuth consent screenfrom the left menu:
Internalfor this app. You can change this as the application gets further developed or is ready to be deployed.
Fill in the name of the application, your email, and the required developer support email at the bottom. Leave the rest of the fields, including the App domain, empty for now.
In the scopes screen, select the
Add or Remove Scopesoption:
and then enter
drive.readonly into the search window.
- Select the
https://www.googleapis.com/auth/drive.readonlyoption and then enable it by clicking the check box associated with the item.
Update button at the bottom to commit the change. Then click
Save and Continue at the bottom of the
Back to Dashboard, then select the
Credentialsbar on the left:
Create Credentials option, followed by the OAuth Client Id option.
Web applicationas the application type, and enter in a name:
In a new tab, open the Fusebit management portal and select the
Enable production credentialstoggle, and then copy the OAuth2 Redirect URL using the icon on the right:
Add that value to your
Authorized redirect URI list in the Google App configuration window.
Google's App Restrictions
In the future, when you look at publishing your App so that your customers can make use of it directly, Google will require a fairly invasive and intensive review process. One of the requirements at that point is that you're able to demonstrate ownership of the domain to which you are redirecting users, in addition to your root domain.
Traditionally, this is solved by adding a
302 Redirectendpoint on your backend that is hardcoded to redirect the user to a specific Fusebit OAuth2 Redirect URL. Since Google is the only service that requires this particular action, it's fairly straightforward to add an endpoint.
Create button at the bottom.
- Copy the Client ID and Client Secret into the Fusebit Google Connector configuration, from this dialog:
Into this configuration panel:
- Add the desired
https://www.googleapis.com/auth/drive.readonlyscope to the list of scopes in the Fusebit configuration:
- Save the Fusebit Connector Configuration
At this point, you should be able to use the new connector with your integration!
Updated about 1 month ago