
Deno Deploy
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

Connect Deno Deploy to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
Enter a Deno Deploy organization access token to sync your apps, revisions, domains, analytics, and runtime logs into the PostHog Data warehouse.
Create an organization access token in your Deno Deploy dashboard under Settings > Access Tokens. The token is scoped to a single organization, so one connection syncs one Deno Deploy organization.
Configuration
| Option | Type | Required |
|---|---|---|
Access token | password | Yes |
Linking Deno Deploy to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select Deno Deploy
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
apps | A Deno Deploy application: a web service that serves traffic within the organization, identified by a unique slug. | Full refresh | — | — |
revisions | A single version (build) of an app's code. When deploying from GitHub, revisions generally map one-to-one to git commits. | Full refresh | — | — |
domains | A custom domain mapped to the organization's deployments, with its verification and TLS certificate state. | Full refresh | — | — |
analytics | Per-app usage metrics in 15-minute buckets (request count, CPU, bandwidth, KV units), reshaped from the columnar API response into one row per time bucket. | Incremental, Full refresh | time | — |
logs | Runtime log lines emitted by an app over a time window. Each row is given a synthesized content-hash id since Deno Deploy runtime logs carry no natural identifier. | Incremental, Full refresh | timestamp | — |