On this page

Glean connector

Index your DevRev objects into Glean. This snap-in functions as a connector with Glean, the enterprise search tool, making DevRev objects discoverable and enabling searches using a wide range of filters.


For more information, refer to the Glean connector snap-in on the DevRev marketplace.


  1. Create a Glean datasource by following the steps provided under "Option 1: Using the Glean custom app setup page.

    a. Choose a unique name for the datasource.

    b. Select "Published content" as the datasource category.

    c. Enter a display name.

    d. Skip the icon entry, as the snap-in will overwrite it with the DevRev logo for easy recognition.

    e. In the URL regex field, enter: ^https://app.devrev.ai/.*

    f. Ensure the "Email is used to reference users [...]" box is unchecked.

    g. Click the "Publish" button to create the custom app.

  2. Create a Glean API token by following the instructions provided here. Under Scopes, enter the unique name you assigned to the datasource in the previous step.

  3. In DevRev's marketplace, click the Install button to register the snap-in with your organization.

  4. In the DevRev app, setup the connection in Settings > Snap-ins > Connections at the top.

    • Search and select an existing connection or create a new one by clicking + Connection.
    • Select Snap-in Secret from the dowpdown list.
    • Provide a name and enter the API token on the "Secret" input box. Ensure to toggle on Make public to share the connection publicly with your organization.

Configure the snap-in

  1. In the Configuration tab, select the connection containing Glean's API token that was just created.

  2. Enter the datasource unique name, display name, and your Glean's instance name. You can find the latter in the URL when accessing your organization's Glean platform. Enter the value before -be.glean.com. For example, if your url is "app.glean.com/some-name-be.glean.com", enter "some-name".

  3. Decide which DevRev object types should be indexed and discorevable in Glean. Set the toggles based on your preferences.

  4. Determine if there are any custom fields associated with specific object types that should be visible as filters in Glean's UI. While stock fields and object types are automatically enabled as filters, custom fields require their display names for indexing. Add a configuration input for each custom field that needs to be indexed.

  5. Save your changes and proceed to install the snap-in. It will run on a schedule, indexing objects into Glean accordingly.