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

# Linking BoldDesk as a source

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

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

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

![](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 BoldDesk connector syncs your help desk data – tickets, ticket updates, ticket worklogs, contacts, contact groups, agents, satisfaction ratings, groups, and brands – into PostHog, so you can analyze support activity alongside your product data.

## Prerequisites

You need a BoldDesk account with API access. You'll need your BoldDesk subdomain and an API key.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  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 BoldDesk, you'll need:

-   **Subdomain** – the subdomain of your BoldDesk account. For `https://yourcompany.bolddesk.com/`, the subdomain is `yourcompany`. If you use a custom domain, enter your `bolddesk.com` subdomain instead.
-   **API key** – create one in BoldDesk under **Profile → API keys** (`https://yourcompany.bolddesk.com/agent/personal-settings`). The API key reads the same tickets and records as the agent who created it.

## 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_at` timestamp). 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](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `BoldDesk subdomain` | text | Yes |
| `API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `tickets` | A support ticket in BoldDesk. | Incremental, Full refresh | lastUpdatedOn | — |
| `ticket_updates` | A reply or note added to a BoldDesk ticket. | Incremental, Full refresh | updatedOn | — |
| `ticket_worklogs` | Time an agent logged against a BoldDesk ticket. | Incremental, Full refresh | lastModifiedOn | — |
| `contacts` | A customer contact in BoldDesk. | Incremental, Full refresh | lastModifiedOn | — |
| `contact_groups` | A contact group in BoldDesk, usually a customer company. | Incremental, Full refresh | lastModifiedOn | — |
| `agents` | An agent (help desk user) in BoldDesk. | Incremental, Full refresh | lastModifiedOn | — |
| `satisfaction_ratings` | A customer satisfaction (CSAT) rating given on a BoldDesk ticket. | Incremental, Full refresh | lastModifiedDate | — |
| `groups` | An agent group in BoldDesk. | Full refresh | — | — |
| `brands` | A brand (separate help desk portal) in BoldDesk. | Full refresh | — | — |

### Table details

| Table | Description | Sync method |
| --- | --- | --- |
| `tickets` | Support tickets | Incremental |
| `ticket_updates` | Replies and notes added to tickets | Incremental |
| `ticket_worklogs` | Time logged against tickets | Incremental |
| `contacts` | Customer contacts | Incremental |
| `contact_groups` | Contact groups (usually customer companies) | Incremental |
| `agents` | Help desk users | Incremental |
| `satisfaction_ratings` | Customer satisfaction (CSAT) ratings | Incremental |
| `groups` | Agent groups | Full refresh |
| `brands` | Help desk portals | Full refresh |

**Incremental** tables sync only new or updated records on each run. **Full refresh** tables reload all data on each sync.

## Troubleshooting

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.