Glean
Glean is an enterprise search and knowledge discovery platform that helps organizations find and access information across all their tools and systems. The Glean connector reads search results, documents, people, chats, agents, and other content through Glean's Client API, and sends documents, permissions, users, groups, employees, and teams to Glean's Indexing API.
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
- 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
Glean issues two kinds of API token, and each Glean template works with only one of them:
| Token | Used by |
|---|---|
| Client API token | The 25 data source templates that read from Glean, such as Search, Get Document, and List People. |
| Indexing API token | All destination templates, plus the Get Datasource Config, Get Datasource Status (Beta), and Check Document Access data source templates. |
A Nexla credential holds one token. If you plan to both read from Glean and send data to it, create two credentials: one with a Client API token and one with an Indexing API token. Both kinds of token are sent in the Authorization header as Bearer <token>.
You also need your Glean instance name for the Domain field. It is the part of your Glean API URL before -be.glean.com; for example, if your API URL is https://acme-be.glean.com, the domain is acme.
Create a Client API token
-
In the Glean admin console, open Client API token management, and click Add New Token.
-
Under Permissions, select USER, and enter the User Email of the Glean user whose access the token should have. The templates return what that user can see in Glean.
The connector does not send the
X-Glean-ActAsheader, which Glean requires for global Client API tokens. A token with GLOBAL permissions will not work with this connector; use a user-scoped token. -
Under Scopes, select every scope for the templates you plan to use. To use all of the Client API templates, select
SEARCH,DOCUMENTS,SUMMARIZE,CHAT,AGENTS,TOOLS,ANSWERS,COLLECTIONS,PINS,SHORTCUTS,VERIFICATION,ENTITIES, andPEOPLE. Each template below lists the scope it needs.Glean does not let you change a token's scopes after it is created. If you need a scope later, create a new token with all of the scopes you need, and update the Nexla credential with it.
-
Optionally set an expiration date, and save the token. Glean shows the token only once, so copy it and store it securely.
Super Admins can create user-scoped tokens for any user; Admins and API Token Creators can create them only for themselves. For details, see Glean's Client API authentication guide.
Create an Indexing API token
-
In the Glean admin console, go to Platform > API Tokens, open the Indexing Tokens tab, and click Add API token.
-
Either turn on Has global permissions so the token works with every datasource, or leave it off and list the custom datasources the token may use under Scopes. A datasource-limited token works only with those datasources, so the datasource you enter in a template or send in a record must be one of them.
-
Set Expires On (Glean requires it), and save the token. Glean shows the token only once, so copy it and store it securely.
Setup Admins, Admins, and Super Admins can create global or datasource-limited Indexing tokens; API Token Creators can create datasource-limited tokens only. For details, see Glean's Indexing API authentication guide.
Authenticate
Credentials required
| Field | Required | Secret | Description |
|---|---|---|---|
| Domain | Yes | No | Your Glean instance name: the part of your Glean API URL before -be.glean.com. For https://acme-be.glean.com, enter acme. Do not include -be, https://, or .glean.com. |
| API Token | Yes | Yes | A Glean Client API token (for the data source templates) or Indexing API token (for the destination templates and the three Indexing API data source templates). See Prerequisites. |
Create a credential in Nexla
- After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – Glean

-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field. Include the token kind in the name, for example
Glean (Client API)orGlean (Indexing API), so you can tell the credentials apart later. -
Enter your Glean instance name in the Domain field, for example
acmeif your Glean API URL ishttps://acme-be.glean.com. Nexla adds-be.glean.comto build the request URL.Enter only the instance name. If you enter
acme-beoracme-be.glean.com, Nexla builds a URL with the wrong host (such ashttps://acme-be-be.glean.com), and requests fail. -
Enter the Client API token or Indexing API token in the API Token field. Nexla sends it in the
Authorizationheader asBearer <token>.The API token is sensitive and should be kept secure. If it is exposed, revoke it in the Glean admin console, create a new token, and update this credential.
-
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 data source
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Glean connector tile, then select the credential that will be used to connect to your Glean instance, and click Next; or, create a new Glean credential for use in this flow. Use a credential with a Client API token for all templates except the three under Indexing API reads, which need an Indexing API token.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Glean endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below, grouped by area.
Each template makes a single request per run and returns the records in that response; Nexla does not page through results automatically. Templates with a Cursor setting return one page, sized by Page Size. Each template lists the Client API token scope it needs; a token without that scope gets an authorization error from Glean. Text settings are inserted into the JSON request body as entered, so avoid double quotation marks and backslashes in them.
Search and discovery
Documents
Glean Assistant and chats
Agents and tools
The three agent templates call Glean's Platform API under /api/agents.
Answers, collections, pins, shortcuts, and verifications
People and teams
Indexing API reads
These three templates call the Indexing API, so they need a credential with an Indexing API token, not a Client API token. If the token is limited to specific datasources, enter one of those datasources.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving. Testing Ask Glean Assistant or Summarize Document runs the request in Glean, which generates a new answer or summary each time.
Manual configuration
Glean data sources can also be manually configured to ingest data from any valid Glean API endpoint not covered by the pre-built templates. 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, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers. Client API endpoint URLs take the form https://<domain>-be.glean.com/rest/api/v1/...; see the Glean Client API reference for the available endpoints.
Not yet available as templates:
- Listing documents by facet needs a feature that Glean must enable on your instance.
- Document permissions (reading who can access a document) needs the
DOCPERMISSIONSscope.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Glean data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
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 a credential with an Indexing API token, and click Next; or, create a new Glean credential for use in this flow. Destination templates do not work with a Client API token.
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.
Every destination template sends a POST request to Glean's Indexing API at https://<domain>-be.glean.com/api/index/v1/.... Each record in the Nexset is sent as the JSON body of one request, one record at a time, so shape each record to match the request body that Glean documents for the endpoint. If the Indexing token is limited to specific datasources, every record must name one of them. Templates are marked Side effect when they delete more than the record names.
Documents
Datasources
Datasource users, groups, and memberships
Employees and teams
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. The test sends a real request, so test delete templates with records you can afford to lose.
Manual configuration
Glean destinations can also be manually configured to send data to any valid Glean API endpoint. 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's Indexing API expects JSON request bodies at https://<domain>-be.glean.com/api/index/v1/<endpoint>. Nexla adds the Authorization: Bearer <token> header from the credential. See the Glean Indexing API reference for the available endpoints.
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.