OnFire handbook
Run, configure and integrate the current OnFire ticket system.
OnFire runs a customer portal (ToC) and an internal support dashboard (ToB) in one Cloudflare Worker. The optional email agent is a separate transport Worker. D1 stores business records, R2 stores images and source documents/raw mail, and Vectorize indexes structured product knowledge.
Install and operate
- Quick start: local D1, demo accounts and both web surfaces.
- Deployment: resources, domains, secrets and Worker order.
- Operations: release checks, logs, backups and recovery.
Configure the workspace
- Access and roles: live scope, teams and support-agent membership.
- Account security: password, Passkey, TOTP and login protection.
- Types and forms: routing trees, immutable versions and internal states.
- Ticket workflow: numbers, assignment, SLA, replies and closure.
- Languages: product languages and stored translations.
- Email: inbound adapters, threading, templates and durable transport.
- Notifications: personal endpoints and inherited rules.
- AI and knowledge: scoped credentials, task routes and knowledge rebuilding.
- Spam filter specifications: genuine-support policy and model/API contracts.
Integrate
- Customer portal: product keys, identity resolver and
/supportproxy. - Account API keys: explicit REST operations and live discovery.
- MCP and WebMCP: remote OAuth delegation and logged-in browser tools.
These pages describe the current source, including the pending decision-filter changes. An existing installation needs the matching migrations and Worker build before new behavior is available. Enabling an AI feature requires configured credentials; uploading a source document does not automatically extract/index it.