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

# Linking TestDino as a source

**Alpha release**

This source is currently in **alpha**. The interface and available tables may change.

![](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 TestDino connector syncs test runs, manual test suites, and manual test cases from your TestDino project into PostHog.

## Prerequisites

You need a TestDino account with a personal access token and a project ID. The token must have access to the project you want to sync.

## Adding a data source

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 TestDino.

3.  You need a personal access token from TestDino. In your TestDino account, go to **User Settings** > **Personal Access Tokens** and create a new token. Make sure the token has access to your project.

4.  Back in PostHog, enter the following:

    -   **Personal access token** – paste your token (starts with `td_pat_...`)
    -   **Project ID** – your TestDino project ID (e.g., `project_abc123`). Only letters, numbers, underscores, and hyphens are allowed.
5.  Click **Next**, select the tables you want to sync, and click **Import**.

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

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Personal access token` | password | Yes |
| `Project ID` | text | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `test_runs` | Automated test runs with their status, timing, test statistics, and Git metadata. | Full refresh | — | — |
| `manual_suites` | Manual test suites with their hierarchy and modification details. | Full refresh | — | — |
| `manual_cases` | Manual test cases with their classification, automation status, steps, and suite details. | Full refresh | — | — |

## Sync methods

All three tables – `test_runs`, `manual_suites`, and `manual_cases` – use full refresh sync only. Incremental sync isn't available because TestDino's start-time filters can't detect later status changes (e.g., a run that moves from "running" to "passed").

## Limitations

-   **Manual cases** – TestDino's API doesn't paginate the manual test cases endpoint. If your project has 1,000 or more manual test cases, the import fails. Disable the `manual_cases` table if this applies to your project.
-   **API version** – the connector is pinned to TestDino API v1.

For more details, see the [TestDino API reference](https://docs.testdino.com/api-reference/conventions).

### Still have questions?

Ask PostHog AI

### Was this page useful?

HelpfulCould be better