Linking Bluesky 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 Bluesky connector syncs profile, posts, followers, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
None. The Bluesky API is public, so no account or API key is needed.
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.
Sync a Bluesky account's profile, posts, followers, and follows. Uses Bluesky's public AppView API, so you only need the handle or DID you want to track, not an account password or app password.
You'll be asked for:
- Handle or DID: the Bluesky handle (e.g.
jay.bsky.team) or DID of the account to sync.
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 Bluesky tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Description |
|---|---|
Handle or DIDType: text Required: True | The Bluesky handle (e.g. |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Profile | The configured account's public Bluesky profile. | Full refresh | — | — |
Posts | Posts and reposts from the configured account's feed, newest first. | Full refresh | — | — |
Followers | Accounts following the configured account. | Full refresh | — | — |
Follows | Accounts the configured account follows. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the 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.