Start establishing a connection to Google Drive in either of the following ways:
- From the Resources menu, select Connections. Then, click + Create connection at the top right.
– or –
- While working in a new or existing integration, you can add an application to a flow simply by clicking Add source or Add destination/lookup.
In the resulting Application list, select Google Drive.
The Create connection pane opens with required and advanced settings.
At this point, you’re presented with a series of options for providing Google Drive authentication.
Name (required): Provide a clear and distinguishable name. Throughout integrator.io imports and exports, you will have the option to choose this new connection, and a unique identifier will prove helpful later when selecting among a list of connections that you’ve created.
Application (required, non-editable): A reminder of the app you’re editing.
Configure your client id and secret
Callback URL (read-only): Copy this integrator.io callback URL to provide directions to Google Drive for where to go after authentication. (This URL should be whitelisted with the authorization server.)
iClient (required): Select the iClient pair that stores the client ID and client secret provided to you by Google Drive. To add an iClient and configure your credentials, click the plus (+) button. Click the edit ( ) button to modify a selected iClient. Be sure to give the iClient a recognizable name for use in any other connections.
Sign in to your Google API Console, and click Create project in your dashboard.
Describe your project and click Create.
From the console options, select OAuth consent screen at the left. Create a consent screen for internal or external users.
App name (required): Enter a name for the Google Drive app you are creating.
User support email (required): Enter your own email address or the email address for someone who can service the app if necessary.
App logo: You can optionally include a logo to display to the end user.
Application home page: Enter your organizations home page URL.
Authorized domains: Click ADD DOMAIN and add celigo.com and integrator.io to the list of domains.
Click SAVE AND CONTINUE.
Select the Credentials menu, click + CREATE CREDENTIALS, and click OAuth client ID.
The Create OAuth client ID page opens.
Application type (required): Select Web application from the drop-down menu.
Name (required): Give the web application a name.
In the Authorized redirect URIs section, click + ADD URI and enter https://integrator.io/connection/oauth2callback.
Select Oauth consent screen and click ADD OR REMOVE SCOPES.
Use the checkboxes in the list to define the resources this app will have access to. When you are satisfied with the scopes you have select, click UPDATE at the bottom of the list. The scopes you select display in the Your sensitive scopes section.
Click SAVE AND CONTINUE.
The Oauth client created screen displays your client ID and client secret.
Copy and paste these values into the integrator.io iClient fields.
Configure scopes (required): Scopes are permissions that the Google Drive API defines to limit the access to your account. To select the scopes for this connection,
- Click the Configure scopes button.
- To access all of the scopes in the API, click the
– or –
Check the scopes you want to add, and click the button.
Before continuing, you have the opportunity to provide additional configuration information, if needed, for the Google Drive connection.
Once you have configured the Google Drive connection, you have a couple options for continuing:
- Save & authorize – click this button to test the connection, commit the new connection so that it will be available to all integrations for your account (and applied to the current source or destination app, if you created it within a flow)
- Cancel – click to exit without saving any new changes
When you select Save & authorize, you are presented with a Google Drive form in a new browser window.
After signing in, review the permissions for the integration and click Allow.
The browser window closes, and the new connection is now successfully added to your account. It will be applied to the current source or destination app, if you created it within a flow. Otherwise, you may proceed to register the connection with an integration.