Integrations

Connect your Google Drive to index specific files directly into the Airis knowledge base. You pick which files to index — Airis never reads your entire Drive. OAuth 2.0 with drive.readonly scope; tokens are AES-256 encrypted at rest.

Setup

Supported file types

File freshness

Airis does not auto-sync Drive files on a schedule — you control which version is in the knowledge base. Use the ↻ Refresh button to re-pull and re-index a file after it has been updated in Drive.

Disconnecting

Clicking Disconnect revokes the OAuth token and removes the connection. Files already indexed into Airis are not deleted automatically — remove them individually from the Drive panel or the Knowledge Base section before disconnecting if you want a clean slate.

Every organisation brings their own LLM API key. Credentials are AES-256 encrypted in OrgSetting and never returned via the API after saving. Switch providers from the admin panel — no restart required.

Embedding models

Airis uses a separate embedding model to convert text into vectors for semantic search. The embedding provider must be configured alongside your LLM provider.

Generate API keys to call Airis programmatically from CI/CD pipelines, internal tools, or scripts. The full key is shown once at creation — Airis stores only the SHA-256 hash.

Scopes

Example

curl -X POST https://api.airis.com/api/v1/chat \
  -H "X-API-Key: airs_live_xxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"message": "What is the Redis config?", "workspaceIds": ["ws_infra"]}'

Add an AI-powered chat bubble to any website you own. Visitors get instant answers from your organisation's knowledge base — scoped to the team you choose. Your internal data stays private; your Airis API key never reaches the browser.

How it works

Visitor browser
  1. loads widget.js  →  GET /embed/widget.js  (served by Airis API)
  2. widget fetches branding  →  GET /embed/config/:chatbotId  (public)
  3. visitor sends message  →  widget calls YOUR backend session endpoint

Your backend  (Express / FastAPI / Spring Boot…)
  4. POST /api/v1/embed/session  (X-API-Key with embed scope)
     ← Airis returns { sessionToken, expiresAt }
  5. your backend returns sessionToken to the browser

Widget (no API key in browser)
  6. POST /embed/chat/stream  Bearer: sessionToken
     ← SSE stream back to visitor

Step 1 — Create a chatbot

Step 2 — Add the widget to your site

Paste this snippet into your HTML before </body>:

<script
  src="https://api.airis.com/embed/widget.js"
  data-chatbot-id="cfg_xxxxxxxxxx"
  data-session-url="https://yoursite.com/api/airis-session"
  defer
></script>

data-session-url — the URL of your own backend endpoint that exchanges your API key for a short-lived session token.

Step 3 — Add the session endpoint to your backend

One endpoint on your server exchanges your API key for a short-lived session token and returns it to the widget. Select your stack:

// Express.js — src/routes/airis-session.js
import express from 'express';

const router = express.Router();

router.post('/api/airis-session', async (req, res) => {
  const response = await fetch('https://api.airis.com/api/v1/embed/session', {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'X-API-Key': process.env.AIRIS_API_KEY,   // embed-scoped key
    },
    body: JSON.stringify({
      chatbotId: process.env.AIRIS_CHATBOT_ID,  // cfg_xxxxxxxxxx
    }),
  });

  if (!response.ok) {
    return res.status(502).json({ error: 'Failed to create session' });
  }

  const { sessionToken, expiresAt } = await response.json();
  res.json({ sessionToken, expiresAt });
});

export default router;

Required API key scope

For air-gapped environments where credentials must never leave your network. The connector Docker image runs inside your infrastructure, reads documents from the folders you point it at, and pushes only processed text chunks to the Airis API — nothing else leaves your network.

docker run -d \
  -e AIRIS_API_KEY=airs_live_xxxxx \
  -e AIRIS_ENDPOINT=https://yourorg.airis.com \
  -e SOURCES=filesystem \
  -e FS_PATHS=/data/docs \
  -v /path/to/docs:/data/docs:ro \
  -e CONNECTOR_INTERVAL_MINUTES=60 \
  airis/connector:latest

BYODB — Bring Your Own Database

Enterprise customers can also provide their own PostgreSQL + pgvector database. Airis validates SSL and pgvector presence, then stores all knowledge vectors on your own infrastructure. Configure at Admin → Settings → Database.