Documentation

Operon Docs

Operational reference for setup, connector configuration, review gates, workers, and output delivery.

Manual Intake

Authenticated users can upload files from the dashboard. Text files are extracted inline; PDFs are stored for the OCR worker path.

Gmail and Drive

Use Configuration to connect Google OAuth, discover Gmail labels, choose monitored labels or Drive folders, and save workspace-scoped polling settings.

API and Upload Portal

API, webhook, WhatsApp, Teams, and upload-portal intake use workspace-scoped tokens or signatures before creating workflow runs.

Webhook Intake

Post JSON to /api/connectors/webhook with x-operon-workspace-id. Configure CONNECTOR_WEBHOOK_SECRET to require a shared secret header.

Human Review

Validation failures create review items. Operators can edit fields, approve, reject, rerun extraction, or escalate.

Output Delivery

Completed and approved runs create delivery records for enabled adapters. Configure mappings and credentials, then use test delivery before going live.

Connector Health

Enabled connectors expose health state through /api/connectors/status, backed by connector events and last-error metadata.

Mappings and Audit

Output mappings and recent audit events are exposed through dedicated workspace-scoped APIs for operator visibility.

Analytics

First-party events are validated server-side and persisted when Supabase is configured, while avoiding third-party tracking.

Workers

Run npm run worker with OPERON_APP_URL and WORKER_SECRET to process queued workflow jobs, connector polling, and output retries continuously.

Privacy and Diagnostics

Operational analytics stay first-party with approximate IP data, and workspace owners can copy support diagnostics with sensitive information redacted.