Glean

Glean is an enterprise search and knowledge discovery platform that helps organizations find and access information across all their tools and systems, providing intelligent search capabilities, knowledge graphs, and insights to improve productivity and decision-making.

Power end-to-end data operations for your Glean API with Nexla. Our bi-directional Glean connector is purpose-built for Glean, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Glean or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Glean workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Glean credential, you need to obtain an API token from your Glean workspace settings. The API token is required to authenticate with the Glean API.

To obtain your API token, you need to have a Glean account with admin access. Once you have access to your account, you can manage API tokens via the API tokens page within Workspace Settings. The API token is sent in the Authorization header with the Bearer prefix (e.g., Bearer {token}) for all API requests to the Glean API. For detailed information about API token setup and authentication, refer to the Glean API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Domain	Yes	No	Your Glean domain. Can be found on the URL, such as https://<domain>-be.glean.com/
API Token	Yes	Yes	Admins can manage these API tokens via the API tokens page within Workspace Settings

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Glean

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Glean domain in the Domain field. This is your Glean domain identifier, which can be found in your Glean URL (e.g., if your Glean URL is https://{domain}-be.glean.com/, then {domain} is your domain identifier). The domain is used to construct the full endpoint URLs for API requests.

   Your Glean domain can be found in your Glean URL. The URL format is typically https://{domain}-be.glean.com/ where {domain} is your domain identifier. The domain is used to construct the full endpoint URLs for API requests to your Glean instance. For detailed information about finding your domain, see the Glean API documentation.

4. Enter your Glean API token in the API Token field. This is the API token you obtained from your Glean Workspace Settings. The API token is sent in the Authorization header with the Bearer prefix for all API requests to the Glean API.

   Keep your API token secure and do not share it publicly. The API token provides access to your Glean account and should be treated as sensitive information. Admins can manage API tokens via the API tokens page within Workspace Settings. The API token is sent in the Authorization header with the Bearer prefix for all API requests to the Glean API. For detailed information about obtaining and managing API tokens, see the Glean API documentation.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a destination

Click the + icon on the Nexset that will be sent to the Glean destination, and select the Send to Destination option from the menu. Select the Glean connector from the list of available destination connectors, then select the credential that will be used to connect to the Glean organization, and click Next; or, create a new Glean credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Glean endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Index Document

Adds a document to the index or updates an existing document.

• This endpoint automatically indexes or updates a document in your Glean search index using data from your Nexset. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses POST requests to https://{domain}-be.glean.com/api/index/v1/indexdocument where {domain} is your Glean Domain from the credential configuration. The endpoint URL is automatically constructed based on your Glean domain.
• The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the document data to index.
• Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to index a document. If you need to index multiple documents, you can send multiple records, but each will be processed as a separate request.
• This endpoint does not automatically create a data source to track the responses received from the Glean API after each call.

The request body must be properly formatted JSON that matches the Glean Indexing API specification for indexing documents. The endpoint requires Bearer Token authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about indexing documents, including required fields, field names, and request formats, see the Glean API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to send a test payload. The result will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the destination is configured correctly before saving.

Manual configuration

Glean destinations can also be manually configured to send data to any valid Glean API endpoint, including endpoints not covered by the pre-built templates or when you need custom API configurations. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Glean API endpoints typically follow the pattern https://{domain}-be.glean.com/api/{endpoint_path} where {domain} is your Glean Domain from the credential configuration, and use JSON format for request bodies. The endpoint requires Bearer Token authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. For detailed information about Glean API endpoints and available APIs, see the Glean API documentation.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Glean endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Glean endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.