Definitions of common terms used in Email Automator and the Setup Wizard.
A backend platform that provides a hosted Postgres database, authentication, storage, and APIs. Email Automator uses Supabase as its database and auth layer.
A setup model where you connect your own Supabase project instead of using a shared backend. This keeps your data in your own infrastructure.
The unique identifier for your Supabase project (often shown in the project URL or settings).
The base URL for your Supabase project, used by the app to connect to the database and APIs.
The public API key for your Supabase project. It is safe for client-side use but still subject to Row Level Security (RLS).
A token from your Supabase account that lets the Setup Wizard create or manage projects on your behalf (used in Quick Start).
The Setup Wizard uses your Access Token to automatically create a Supabase project, apply migrations, deploy Edge Functions, and ingest the knowledge base.
You connect an existing Supabase project by providing the Project URL and Anon Key. Migrations can be run by the wizard if an Access Token is provided.
Managed Provisioning creates a new Supabase project for you using an Access Token.
Manual Sync connects to an existing Supabase project using your Project URL and Anon Key.
Database changes that create or update tables, views, functions, and policies. Migrations keep your database schema aligned with the app.
The structure of your database: tables, columns, types, indexes, functions, and policies.
The language used to define and query database structures and data.
When the app’s expected schema version differs from the database’s actual version. The Setup Wizard or migration tool will prompt you to normalize.
The database major version shown in Account Settings. It’s used to guide migrations and should match your Supabase project’s Postgres version.
Reverting a migration. In Supabase, rollbacks are manual and should be used carefully.
A Postgres security feature that restricts which rows a user can read or write. Supabase uses RLS to protect data.
Serverless functions hosted by Supabase. Email Automator uses them for OAuth flows and secure operations.
A powerful Supabase key that bypasses RLS. It must never be exposed to clients.
The anon key is safe for client use and respects RLS. The service role key bypasses RLS and must only be used on trusted servers.
The local app that provides AI services (LLMs, embeddings, TTS) used by Email Automator.
A profile that defines your tone, style, and preferences for AI-generated drafts and responses.
The emotional character of replies (e.g., friendly, formal, direct).
The writing style preferences (e.g., concise, detailed, bullet points).
The overall “sound” of your writing, including phrasing and rhythm.
A standardized sign-off used in replies (name, title, company).
Your job title or role, used to shape response framing.
The organization name used in replies when appropriate.
The primary language for generated drafts.
Serverless functions hosted by Supabase. Email Automator uses them for OAuth flows and secure operations.
The local backend that handles email syncing, AI processing, and automation execution.
Live updates from the database to the app. Used to reflect new emails, sync status, or activity without refreshing.
An AI model used for analysis and generating responses (e.g., categorization, drafting replies).
A model that converts text into vectors for semantic search. Used by the knowledge base and RAG.
Vector representations of text used for semantic search in the knowledge base.
A method that retrieves relevant documentation and feeds it to the AI so responses stay grounded in your docs.
The process of converting documentation into searchable embeddings and storing them in the database.
Converts AI responses into spoken audio.
The provider is the service that generates speech; the voice is the specific speaker/persona within that provider.
An authorization standard that lets the app access your email account without storing your password.
The screen where you grant Email Automator permission to access your email account.
A short-lived token used to call email provider APIs. It expires and is refreshed automatically.
A long-lived token used to obtain new access tokens without re‑authenticating.
Google’s official API for accessing Gmail data and sending emails.
Microsoft’s API for Outlook and Microsoft 365 data (mail, calendar, contacts).
Email protocols. IMAP reads mail; SMTP sends mail. (Email Automator uses provider APIs rather than raw IMAP/SMTP.)
An app configuration in Azure that provides credentials for Microsoft Graph access.
The public identifier for your OAuth app (Google/Microsoft).
A private secret for your OAuth app. Treat it like a password.
The callback URL where the email provider sends users after OAuth authorization.
An OAuth flow where you authenticate in a browser using a short code, often used for desktop apps.
The Microsoft tenant identifier. Use “common” for multi‑tenant or a specific tenant for org‑only access.
Defines how much history to sync (e.g., last X days) and which accounts are included.
Organization constructs in email providers. Labels tag messages; folders organize them into containers.