A Google Drive connector can be configured in SigningHub Admin by providing the three integration keys i.e. Client ID, Client Secret, and API key. 


Obtain the Google Drive Integration Key

  1. Browse https://console.developers.google.com to open the Google developer console.
  2. Log into your Gmail account.
  3. Click the "Select a project" drop down and select the "Create a project.." option.
  4. Specify your project name, i.e. "SigningHub Admin", agree to the terms of service and click the "Create" button.
  5. A new project will be created with the specified name.
  6. Click the "APIs" option from the left menu, and search "Google Picker API" in the search field. Once retrieved, click the API record to enable it.
  7. Click the "Enable API" to enable the Google Picker API.
  8. Similarly, search "Drive API" in the search field and enable it the same way Google Picker API was enabled.
  9. Now click the "Credentials" option from the left menu, then click the "Add Credentials" drop down and select the "OAuth 2.0 client ID" option.
  10. Specify the product name, i.e. SigningHub Admin, and click the "Save" button.
  11. Select the "Web application" option, and click the "Configure consent screen" button. Now specify the "Name" of your SigningHub Desktop Web as "SigningHub". The "Authorized JavaScript Origins" field is used to pull the documents from Google Drive. Specify the URL of your SigningHub Desktop Web here, e.g. "https://web.signinghub.com". 
  12. The "Authorized redirect URIs" field is used to push the documents from your SigningHub Desktop Web to Google Drive. Specify the callback URL of your SigningHub Desktop Web here. For example if your SigningHub Desktop Web is "https://web.signinghub.com" then the callback URL will be  "https://web.signinghub.com/OAuth/GoogleDriveCallBack". Click the "Create" button.
  13. The client ID and client secret of Google Drive are created and shown on the screen. Add these values in your Google Drive connector. Click OK to proceed further.
  14. The client ID and client secret of your web application is saved for future use.
  15. Now click the "Add credentials" drop down and select the "API key" option.
  16. Click the "Browser key" button.
  17. Specify the "Name" of your browser API, i.e. "browser key 1", and click the "Create" button.
  18. The API key of Google Drive is created and shown on the screen. Add it in your Google Drive connector. Click OK.


Create a OneDrive connector

  1. Access the SigningHub Admin portal.
  2. Click the "Configurations"section from the left menu.
  3. Click the "Connectors" tab. The "Connectors" screen will appear.
  4. Click  from the grid header.



  5. A dialog will appear to add the connector details. The connector dialog is comprised of two screens, i.e. Basic Information and Details. Specify the basic information and click the "Next" button to provide the respective connector details. See the below table for fields description.




     
  6. Click the "Finish" button. A new connector will be saved and displayed in the list.


Basic Information

Fields

Description

Name

Specify a unique name for this connector, i.e. My Google Drive. This connector will be used in the configuration of Global Settings.

Provider

Select the provider for this connector, i.e. "Google Drive". 

Purpose

  This field will display the purpose of the selected provider above, i.e. the purpose of "Google Drive" is "Cloud Drive".

Active

Tick this check box to make this connector active. Inactive connectors cannot be configured in the Global Settings.


Details

Fields

Description

Logo

Select an appropriate image in the jpeg, jpg, gif or png format for the connector's logo that will be displayed on the login screen.

Client ID

  Specify the registered client ID that has been provided by Google Drive during account configuration, e.g. "04586340-uc46ggb7obrikmapn0or2ubignrarrri.apps.googleusercontent.com". 
  SigningHub Desktop Web will use this ID to communicate with the Google Drive server for push and pull activities. See details as how to get the client ID.

Client Secret

  Specify the client secret that has been provided by Google Drive during account configuration, e.g. "hniZYHqPEcKy6H25-LjzSX0Q". See details as how to get the client secret.

App Key

  Specify the API key that has been provided by Google Drive ( during account configuration) to connect to the Google Drive server, e.g. "SyBmGnqiKFzM1P-JLemHgl4juCYGBXjylTU". See details as how to get the API key.

Allow Multiple Files Selection

  Tick this check box to enable the end users to import multiple files from Google Drive.


Configure the Google Drive Connector as Default in the SigningHub Global Settings

  1. Click the "Configurations" option from the left menu.
  2. Click the "Global Settings" option.
  3. Global Settings will appear, select the "Default Connectors" option from the top right drop down. 
  4. Configure these settings as required and click the "Save" button from the screen bottom. 
  5. Select the default Google Drive connector for SigningHub Desktop Web. The selected connector will be used to pull the Google Drive content (documents) directly into SigningHub Desktop Web. The Google Drive connectors are managed through the connectors section, see details.

 



Enable your cloud drives 

  1. Access the SigningHub Web portal.
  2. Click your profile drop down menu (available at the top right corner).
  3. Click the "My Settings" option. 
  4. Click the "Cloud Drives" option from the left menu.
  5. Click the "Enable" option against the Google Drive cloud drive.



  6. A pop-up will appear asking for the authentication of the cloud drive. Provide your credentials and click Login.
  7. Upon successful authentication, the cloud drive will be enabled, and will start appearing in the Post Processing screens.
  8. To pull document from Google Drive, go to “Start New Workflow” and click on the Google Drive icon to upload document.
  9. Document will be pushed to the Google Drive account (if post processing was set during workflow) that has been configured, once a workflow will be completed.


See Also