Linking Stack Overflow for Teams 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 Stack Overflow for Teams connector syncs your internal Q&A knowledge base into the PostHog Data warehouse – questions, answers, articles, tags, users, and collections. This is for Stack Overflow for Teams (the private, enterprise knowledge base by Prosus/Stack Exchange), not the public Stack Overflow website.
Once synced, you can query your knowledge base data alongside your product data, join it with other sources, and use it in insights and dashboards.
Prerequisites
You need a Stack Overflow for Teams account with permission to create personal access tokens. You don't need admin access – read-only (Basic) access is sufficient.
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.
When linking Stack Overflow for Teams, you need:
- Team name – the name of your Stack Overflow for Teams team (for example,
engineering). This is the slug that appears in your team's URL atstackoverflowteams.com. - Personal access token – create one under Account Settings → Personal access tokens in your Stack Overflow for Teams account. Scope the token to the team you want to connect. Read-only (Basic) access is sufficient – you don't need to grant write access.
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 Stack Overflow for Teams tables use full refresh only. The Stack Overflow for Teams v3 API doesn't expose reliable server-side timestamp filters, so each sync reloads all data.
| Table | Sync method |
|---|---|
Questions | Full refresh |
Answers | Full refresh |
Articles | Full refresh |
Tags | Full refresh |
Users | Full refresh |
Collections | Full refresh |
Configuration
| Option | Type | Required |
|---|---|---|
Team name | text | Yes |
Personal access token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Questions | A question posted to your Stack Overflow for Teams knowledge base. | Full refresh | — | — |
Answers | An answer posted to a question in your Stack Overflow for Teams knowledge base. | Full refresh | — | — |
Articles | A knowledge-base article (Business/Enterprise tier) in your Stack Overflow for Teams site. | Full refresh | — | — |
Tags | A tag used to categorize questions and articles in your Stack Overflow for Teams site. | Full refresh | — | — |
Users | A user on your Stack Overflow for Teams site. | Full refresh | — | — |
Collections | A curated collection of questions and articles in your Stack Overflow for Teams site. | Full refresh | — | — |
Available tables
| Table | Description |
|---|---|
Questions | Questions posted to your knowledge base, including title, body, tags, score, and view count. |
Answers | Answers posted to questions, including body, score, accepted status, and the parent question ID. |
Articles | Knowledge-base articles (Business/Enterprise tier), including title, body, type, and tags. |
Tags | Tags used to categorize questions and articles, with post counts and watcher counts. |
Users | Users on your team site, including name, email, department, job title, and reputation. |
Collections | Curated collections of questions and articles, including title, description, and tags. |
Note: The
Articlestable is only available on Stack Overflow for Teams Business and Enterprise plans.
Troubleshooting
- Authorization error (401) – your personal access token is invalid or has expired. Create a new token under Account Settings → Personal access tokens in Stack Overflow for Teams, then reconnect.
- Permission error (403) – your personal access token doesn't have access to this team or resource. Check that the token is scoped to the correct team, then reconnect.
- Missing articles – articles are only available on Stack Overflow for Teams Business and Enterprise plans. If your team is on the Basic plan, the
Articlestable won't return data.
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.