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

# Linking SolarWinds Service Desk as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/solarwinds-service-desk

> **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)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](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 SolarWinds Service Desk connector syncs incidents, problems, changes, and more into the PostHog data warehouse, so you can analyze them alongside your product data.

## Prerequisites

Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.

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

Enter your SolarWinds Service Desk JSON web token to pull your service desk data.

You can generate a token in SolarWinds Service Desk under **Setup → Users & Access → Users** - open the user and use **Actions → Generate JSON Web Token**. The token inherits that user's role, so it needs read access to the records you want to sync, and requests stop working if that user is ever disabled.

SolarWinds Service Desk runs independent regional stacks that do not share data - pick the region your account is on.

You'll be asked for:

-   **Region**: choose between US (api.samanage.com), EU (apieu.samanage.com) and APJ (apiau.samanage.com).
-   **JSON web token**

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

Some SolarWinds Service Desk tables sync incrementally, so later runs only fetch new or updated rows. The rest are full refresh.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Region` | select | Yes |
| `JSON web token` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `incidents` | Help desk incidents and service requests, including state, priority, assignment, requester, and SLA violation details. | Incremental, Full refresh | updated\_at | — |
| `problems` | Problem records tracking root causes behind one or more incidents, with symptoms, workarounds, and linked records. | Full refresh | — | — |
| `changes` | Change management records with plans, state, priority, and links to related incidents, problems, and releases. | Full refresh | — | — |
| `releases` | Release records grouping changes that are deployed together. | Full refresh | — | — |
| `solutions` | Knowledge base solution articles, with their content and attachments. | Full refresh | — | — |
| `catalog_items` | Service catalog items users can request through the service portal. | Full refresh | — | — |
| `users` | Users of the service desk account, with contact details, site, department, and role information. | Full refresh | — | — |
| `groups` | Groups used for assignment and notifications, with their memberships. | Full refresh | — | — |
| `departments` | Departments records can be associated with (incidents, assets, users). | Full refresh | — | — |
| `sites` | Physical sites/locations records can be associated with. | Full refresh | — | — |
| `hardwares` | Hardware assets (computers) tracked in asset management, with hardware specs, network details, and ownership. | Full refresh | — | — |
| `other_assets` | Non-computer assets (peripherals, furniture, equipment) tracked in asset management. | Full refresh | — | — |
| `categories` | Categories and subcategories used to classify incidents, problems, and changes. | Full refresh | — | — |
| `configuration_items` | Configuration items (CMDB records) and the incidents, problems, changes, and releases that reference them. | Full refresh | — | — |
| `audits` | Audit trail entries that record each change to service desk records, such as state and assignment changes. | Full refresh | — | — |
| `time_tracks` | Time logged against incidents, one row per time entry. | Full refresh | — | — |

## Troubleshooting

-   If the connection fails with an authorization error, the JSON web token 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](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.