Linking Deno Deploy as a source
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.
This source is currently in alpha. The interface and available tables may change.
The Deno Deploy connector syncs apps, revisions, domains, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Enter a Deno Deploy organization access token to sync your apps, revisions, domains, analytics, and runtime logs.
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.
You'll be asked for:
- Access token: for example
ddo_....
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All Deno Deploy tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Access token | password | Yes |
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 | — |
Troubleshooting
- If the connection fails with an authorization error, the access token is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.