Glean

🚀 Quickstart

Connect to Glean with Nango using a Glean-issued token. See Glean (OAuth) if you want Glean’s OAuth Authorization Server flow instead.

Create the integration

In Nango (free signup), go to Integrations -> Configure New Integration -> Glean.

Authorize Glean

Go to Connections -> Add Test Connection -> Authorize, then enter your Server URL and API Token (see the connect guide below). Later, you’ll let your users do the same directly from your app.

Call the Glean API

Let’s make your first request to the Glean Client API (search). Replace the placeholders below with your secret key, integration ID, and connection ID:

cURL
Node

curl "https://api.nango.dev/proxy/rest/api/v1/search" \
  -X POST \
  -H "Authorization: Bearer <NANGO-SECRET-KEY>" \
  -H "Provider-Config-Key: <INTEGRATION-ID>" \
  -H "Connection-Id: <CONNECTION-ID>" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "quarterly reports",
    "pageSize": 10
  }'

Install Nango’s backend SDK with npm i @nangohq/node. Then run:

import { Nango } from '@nangohq/node';

const nango = new Nango({ secretKey: '<NANGO-SECRET-KEY>' });

const res = await nango.post({
    endpoint: '/rest/api/v1/search',
    providerConfigKey: '<INTEGRATION-ID>',
    connectionId: '<CONNECTION-ID>',
    data: {
        query: 'quarterly reports',
        pageSize: 10
    }
});

console.log(res.data);

Or fetch credentials with the Node SDK or API.✅ You’re connected! Check the Logs tab in Nango to inspect requests.

Implement Nango in your app

Follow our Auth implementation guide to integrate Nango in your app.To obtain your own production credentials, follow the connect guide linked below.

📚 Glean integration guides

Nango-maintained guides for common use cases.

How do I link my Glean account? Finding your Server URL and generating an API token

Official docs: Glean Developer Portal

🧩 Pre-built syncs & actions for Glean

Enable them in your dashboard. Extend and customize to fit your needs. No pre-built syncs or actions available yet.

Not seeing the integration you need? Build your own independently.

API gotchas

Global tokens require an extra header, added per-request. This integration assumes a user-scoped token, which only needs the bearer token. If you use a global token instead, Glean also requires an X-Glean-ActAs: user@company.com header on every request identifying which user to act as. The Connect UI has an optional Act As field for storing this email on the connection, but Nango doesn’t attach it to requests automatically — read it back from the connection (via the Node SDK or API) and pass it as X-Glean-ActAs via the headers option on nango.proxy()/nango.post() calls.

Gong OAuth Glean (OAuth)

⌘I

Overview

900+ APIs & Integrations

🚀 Quickstart

📚 Glean integration guides

🧩 Pre-built syncs & actions for Glean

API gotchas

​🚀 Quickstart

​📚 Glean integration guides

​🧩 Pre-built syncs & actions for Glean

​API gotchas

🚀 Quickstart

📚 Glean integration guides

🧩 Pre-built syncs & actions for Glean

API gotchas