Configure once
CatOps owns the platform developer setup, so tenant admins only click connect.
Back to product
External systems
Integrations and Connected Operations
CatOps is being structured so outside systems can connect without making tenants manage developer consoles. Integrations are tenant-scoped, status-aware, and designed to keep credentials encrypted on the server.
What is included
The working parts behind this feature.
- Tenant-scoped IntegrationConfig records with encrypted settings and connection status
- Google Calendar OAuth with read-only calendar access, refresh tokens, calendar selection, and disconnect
- Integration settings page with status cards and user-friendly connection flows
- Webhook routes and Stripe billing integration infrastructure
- QuickBooks-ready quote accounting fields for future estimate, invoice, PO, deposit, and payment tracking
Workflow
How it moves through CatOps.
Authorize per tenant
Each tenant connects its own account and tokens stay scoped to that tenant.
Use safely
Start with read-only or explicit-action integrations before automating external changes.
Expand later
Use the same connection model for deeper accounting, calendar, and workflow syncs.
Why it matters
Tenant-friendly connection UX
Server-side encrypted credential storage
Clear path toward QuickBooks-backed accounting visibility