Flarite Docs

Appwrite Integration

Manage your Appwrite project — users, databases, collections, functions, and storage — conversationally.

What you can do

  • Identity — List and manage users (create, update, block, delete).
  • Databases — Browse databases, collections, and document schemas.
  • Documents — List and inspect documents in any collection.
  • Functions — List, inspect, and invoke Cloud Functions.
  • Storage — Browse Storage buckets and manage files.
  • Messaging — View messaging topics and targets.
  • Multi-Instance — Supports both Appwrite Cloud and self-hosted instances.

Getting your Appwrite API Key

  1. Open your Appwrite Console (cloud.appwrite.io or your self-hosted URL).
  2. Select your project.
  3. Go to Settings → API keys.
  4. Click "Create API key".
  5. Give it a name like "Flarite" and select the scopes you need. For read access, the minimum recommended scopes are:
    users.read
databases.read
collections.read
documents.read
functions.read
storage.read
buckets.read
  6. For full management capability, add the corresponding .write scopes.
  7. Copy the API key.

Back in Flarite → Appwrite → API Tokens, fill in:

  • API Key — your Appwrite API key
  • Project ID — found in your Appwrite Console under Project Settings → Project ID (e.g. 64f9b3d2e4b0a1c2d3e4f5a6)
  • Endpoint URL — leave blank for Appwrite Cloud (https://cloud.appwrite.io/v1). For self-hosted, enter your instance URL.
✨
TipIf you're self-hosting Appwrite, Flarite works the same way — just provide your instance URL in the Endpoint field. Example: https://appwrite.mycompany.com/v1

Example prompts

"List all users in my Appwrite project"

"Show me the last 10 users who signed up"

"List all databases and their collections"

"How many documents are in the 'orders' collection?"

"Show me all storage buckets and their sizes"

"List all cloud functions and when they were last deployed"

Notes on permissions

  • Flarite uses the Appwrite Server API — all operations bypass client-side permission checks and run at the API key's scope level.
  • Destructive operations (deleting users, documents, files) require explicit confirmation in Flarite before they proceed.
  • The API key you provide should follow the principle of least privilege — only grant the scopes Flarite actually needs.