> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking BuildBetter as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/buildbetter

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://app.posthog.com` (app host for links).

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

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.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The BuildBetter connector can link interviews, extractions, persons, and companies to PostHog.

To link BuildBetter:

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.

2.  Click **\+ New source** and then click **Link** next to BuildBetter.

3.  You need an API key from BuildBetter. Go to your [API & MCP settings](https://app.buildbetter.app/settings/org/api-mcp) in BuildBetter and copy your API key.

4.  Back in PostHog, paste the API key in the `API key` field and click **Next**.

5.  On the next page, set up the schemas you want to sync and modify the method and frequency as needed. Once done, click **Import**.

Once the syncs are complete, you can start using BuildBetter data in PostHog.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `interviews` | A recorded interview or call in BuildBetter, with transcript, summaries, and attendees. | Full refresh | — | — |
| `interview_attendees` | A person who attended an interview, linking an interview to the person who took part in it. | Full refresh | — | — |
| `interview_sentences` | A single sentence of an interview transcript, with its speaker and timing. | Full refresh | — | — |
| `interview_tags` | A tag applied to a call, resolving the tag references carried on interviews. | Incremental, Full refresh | interview\_updated\_at | — |
| `interview_types` | The call type of an interview, such as a demo call or a user interview. | Incremental, Full refresh | interview\_updated\_at | — |
| `extractions` | An AI-extracted insight from an interview — a quote with sentiment, topics, and context. | Incremental, Full refresh | created\_at | — |
| `extraction_topics` | A topic assigned to an extraction, resolving the topics attached to an AI-extracted insight. | Incremental, Full refresh | extraction\_created\_at | — |
| `extraction_types` | A signal type assigned to an extraction, such as a pain point or a feature request. | Incremental, Full refresh | extraction\_created\_at | — |
| `documents` | An AI-generated document in BuildBetter, produced from calls or folders. | Incremental, Full refresh | updated\_at | — |
| `persons` | A person tracked in BuildBetter — an interview participant or customer contact. | Incremental, Full refresh | updated\_at | — |
| `companies` | A company tracked in BuildBetter, grouping the people associated with it. | Incremental, Full refresh | updated\_at | — |