search mobile facets autocomplete spellcheck crawler rankings weights synonyms analytics engage api customize documentation install setup technology content domains user history info home business cart chart contact email activate analyticsalt analytics autocomplete cart contact content crawling custom documentation domains email engage faceted history info install mobile person querybuilder search setup spellcheck synonyms weights engage_search_term engage_related_content engage_next_results engage_personalized_results engage_recent_results success add arrow-down arrow-left arrow-right arrow-up caret-down caret-left caret-right caret-up check close content conversions-small conversions details edit grid help small-info error live magento minus move photo pin plus preview refresh search settings small-home stat subtract text trash unpin wordpress x alert case_deflection advanced-permissions keyword-detection predictive-ai sso

Google Drive Connector Guide

Ingest all of your Google Drive files into Enterprise Search.

This includes spreadsheets, docs, slides, and your Drive files.

The Google Drive Connector requires that you create an OAuth App within Google.

Configuration

Login to Google's developer console: https://console.developers.google.com.

You will need to create a project, then add the Google Drive API to it.

After logging in, click Create where requested:

Google Drive - You are greeted with a create prompt.
Google's menus are very straight forward. Sort of like a point and click adventure. Each new screen introduces a modal guiding you what to do. This picture shows a create prompt. It's a gray bar, with some nice, cleanly arranged text.

Fill in the project information in a way that best suits your organization.

Make sure that you create this app with a trusted and stable Google account!

We recommend creating a team-owned account for only this app. If access is lost, we cannot help.

Next you will be asked to search among many different APIs.

Use the search bar to find the Google Drive API:

Google Drive - Search for Google Drive API
There are a ton of APIs you can setup. So many that it is better to search via the search bar than to try to parse them all with your eyes or ears.

Click on it, and then click Enable:

Google Drive - You've found Google Drive. Enable it.
The Google Drive API has a nice page which explains more about it. The image shows an Enable button in said page.

You will be prompted to Create Credentials:

Google Drive - Create project credentials.
This is another guided prompt. Gray, clean, asking for credentials.

Select Google Drive API as the API you are using. You will call it from Web browser to access User data:

Google Drive - Select Developer Settings from within the main settings menu.
A few choices before you can configure your application. The menu has multi-select options. Mostly text. Well written. Their technical writers are pretty good.

After clicking on What credentials do I need?, you will need to setup OAuth access to the API you have chosen.

Fill it out like so:

  • Application type: Web application.
  • Name: Whichever feels best for you. Enterprise Search makes sense, keeps things clear.
  • Authorized JavaScript origins: http://127.0.0.1:3002
  • Authorized redirect url: You'll need two: (1) http://localhost:3002/ent/org/sources/google_drive/create and (2) http://localhost:3002/ent/sources/google_drive/create.
Google Drive - Select Developer Settings from within the main settings menu.
t's a menu with a fair amount of text and input parameters. The guide explains the options well. Or, well in my opinion. You may disagree. And that's cool (smiley face).

Once you have filled everything in, click Create.

Your new credentials will appear:

Google Drive - Select Developer Settings from within the main settings menu.
Credentials! It's a bunch of cryptic strings in a box with adequate warning about the sensitivity of credentials and various other limitations.

Keep them secret!

The app can stay in developer mode. You do not need to publish it.

You may be asked to create an OAuth consent screen at some point in the set-up process.

Click on Credentials from the main developer menu, then Oauth consent screen submenu.

  • Application type: Internal.
  • Application name: Whatever you'd like. Enterprise Search makes sense.
  • Application logo: How about the Enterprise Search logo?

Right click and save-as, if you'd like:

It's all colourful, sleek, and sophisticated. A partial, sunlike circle with a convex-like bubble coming out of the right side connects to what looks like a convex green eye. It's pretty radical.

It will look like so:

Google Drive - Select your scopes.
Credentials! It's a bunch of cryptic strings in a box with adequate warning about the sensitivity of credentials and various other limitations.

Before clicking save, you will also need to add scopes:

Google Drive - Add a name and a logo.
Credentials! It's a bunch of cryptic strings in a box with adequate warning about the sensitivity of credentials and various other limitations.

Now, click Save.

For the final steps, you must return back to Enterprise Search.

Login to Enterprise Search.

Within the administrative dashboard, click Settings on the sidebar.

Navigate to Content Source Connectors:

Google Drive - Click Sources within the sidebar.
A picture of the sidebar within the administrative dashboard. The item

Select the Google Drive Connector and click Setup.

Fill in the Client ID and Client Secret then click Save Changes:

Google Drive - Add the tokens to Enterprise Search.
Two simple text boxes, one green button. It's not our finest view, but it does the job.

Content Source Connector, created! Click Settings if you ever need to change tokens or remove the Connector.

Google Drive - A successful configuration.
Content source... added. Nice work.

Now, click Sources within the sidebar.

Google Drive - Click Sources within the sidebar.
A picture of the sidebar within the administrative dashboard. The item

Click Add under the Google Drive source.

First, you'll need to click I understand.

Why the hurdle? We want to make it clear that you're adding a public source.

All of its contents will be accessible by those with the right permissions.

If you're comfortable with that, click the button:

Google Drive - Understanding the nature of public sources.
It's a button that says I understand. Seems annoying, but you'd be amazed at the things that happen.

After that, you'll be asked to connect to Google Drive:

Google Drive - Forward, for OAuth.
Connect the Connector!

You'll then be presented with an OAuth screen from Google Drive.

Once you accept, you have added Google Drive as a content source to your organization.

Congratulations! It's time to search.

You can now make the source available to various groups and scale its relevance priority.


Enjoying the beta? Something broken? Lost? Please send us your feedback or visit the Enterprise Search community.