Convex integration: connect projects and cloud deployments to Polylane
Connect Convex projects and cloud deployments to Polylane with a team token. Read function logs and deployment metrics to investigate backend failures.
Get started for freeHow to set up Convex
The checked guide does not publish an end-to-end setup duration. Discovery begins after token validation.
- Open Convex Dashboard → Team Settings → Access Tokens and create a team access token.
- Paste the complete token into Convex’s connection form in Polylane. A project token or deploy key cannot list team projects.
- Connect after validation. One token connects one team; inspect each project and its cloud deployments in the account.
Permissions and access
Team access tokens grant team management access; there is no read-only team token selector in the Polylane flow. Inventory reads projects and deployments. Log and metric reads mint a short-lived deploy key scoped to that read, use it for one call, then delete it. The connection therefore needs management capability even though those investigation calls read telemetry.
Discovery, refresh and the connected view
Projects and cloud deployments refresh every 15 minutes, including production, preview, development and custom deployment classes with their URLs and regions. Local deployments on developer machines are deliberately excluded. Function logs and deployment metrics are read through investigation tools; audit logs require a paid Convex plan, and free teams fall back to logs and graph context.
Disconnect and revoke access
Disconnect the team in Polylane, then delete the team access token in Convex Dashboard → Team Settings → Access Tokens. Use manual Sync while connected to pick up a newly deployed project sooner.
Provider credentials and Polylane’s access mode are separate. Where write-capable tools exist, the connected account’s Settings page offers a Read-only switch. Turning it off permits writes subject to review and confirmation, but cannot add permissions to the provider credential. Agent-connected Kubernetes clusters stay read-only.
In the graph.
Every Convex resource Polylane picks up sits in the graph with its connections, config and history.
Project Deployment Tools for the investigation.
What Polylane can do with Convex while it investigates. Every call is recorded in the transcript.
convexApi Call any Convex Management API endpoint that lacks a dedicated tool
convexGetLogs Get function execution logs for a Convex deployment
convexListTables List the tables of a Convex deployment with their inferred document shapes
convexReadTable Read documents from a Convex table, newest or oldest first
convexRunQuery Run a one-off read-only query against a Convex deployment
convexQueryMetrics Query function metrics for a Convex deployment
Convex setup and troubleshooting
Common questions.
How does Polylane connect to Convex?
Open Convex Dashboard → Team Settings → Access Tokens and create a team access token. Paste the complete token into Convex’s connection form in Polylane. A project token or deploy key cannot list team projects. Connect after validation. One token connects one team; inspect each project and its cloud deployments in the account.
What does Polylane sync from Convex?
Projects and cloud deployments refresh every 15 minutes, including production, preview, development and custom deployment classes with their URLs and regions. Local deployments on developer machines are deliberately excluded. Function logs and deployment metrics are read through investigation tools; audit logs require a paid Convex plan, and free teams fall back to logs and graph context.