Project context stays together
Review Convex information beside the project owner, status, tasks, and recent activity instead of treating infrastructure inspection as a separate thread with no business context.
Authorize your Convex team with OAuth so Kato can discover its projects and deployments, then inspect tables, documents, and function logs directly on project records without collecting deploy keys.
Review Convex information beside the project owner, status, tasks, and recent activity instead of treating infrastructure inspection as a separate thread with no business context.
Engineers can inspect technical details while project leads can see deployment health and current work from the same record, reducing handoffs and repeated status explanations.
Connect Convex through its authorization flow, select the project Kato should show, and keep the source system in control of the permissions granted to the connection.
Kato uses Convex's team-scoped OAuth authorization-code flow with PKCE. Projects and cloud deployments are discovered through the Management API, and the encrypted application token authorizes read-only table and log requests. Link an automatically discovered deployment to a project record, then open the Convex panel to browse tables, row data, and recent function logs.
Open a project record before a release check to review linked Convex deployments and connect anything that needs attention to a Kato task or follow-up.
Inspect tables and documents while discussing a customer issue, keeping the technical evidence next to the record and people affected by the investigation.
Review functions and recent logs as part of an engineering workflow, then assign remediation work without losing the project context that prompted the check.
No. The integration retrieves the project information needed for the views you open. Convex remains the system of record for application data, deployments, functions, and logs.
Yes. After authorizing the integration, link the relevant Convex project from the Kato project record so future views resolve to the correct technical environment.
A teammate who can authorize the appropriate Convex account and project should establish the connection. Kato workspace permissions continue to control who can view and manage the linked record.
Last updated Aug 17, 2026