Linking Upstash 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 Upstash connector syncs redis databases, redis stats, teams, 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 your Upstash account email and a management API key to pull your Upstash Redis databases, usage stats, teams, and vector indexes.
Create a management API key in the Upstash console under Account > Management API. The Developer API is only available to native Upstash accounts (not Vercel or Fly.io marketplace accounts).
You'll be asked for:
- Account email: for example
you@example.com. - Management API key
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 Upstash tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Account email | Yes | |
Management API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
redis_databases | Every Upstash Redis database on the account, with its configuration, plan, region, and state. | Full refresh | — | — |
redis_stats | Usage and billing statistics for each Redis database: daily and monthly commands, bandwidth, storage, latency percentiles, and cache hit/miss counts. One row per database. | Full refresh | — | — |
teams | Teams the account belongs to. | Full refresh | — | — |
vector_indexes | Upstash Vector indexes on the account, with their configuration, plan, and per-plan limits. | Full refresh | — | — |
audit_logs | Chronological record of actions taken on the account and its databases (creations, deletions, config changes), with the actor and originating IP. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the management API key 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.