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

# Linking Unstructured as a source

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

> **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 Unstructured connector syncs metadata from your [Unstructured](https://unstructured.io) platform account – workflows, job runs, per-job processing details and failed files, notifications, and source/destination connectors – into the PostHog data warehouse so you can monitor document pipeline health alongside the rest of your data.

Unstructured is a document ETL platform that turns raw files (PDFs, Office documents, emails, and more) into RAG-ready structured data.

## Prerequisites

-   An [Unstructured platform](https://platform.unstructuredapp.io) account (a free tier is available).
-   An Unstructured API key. The key has account-wide read access, so no extra scopes are required.

## 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 Unstructured, you'll need:

-   **API key** – sign in to the [Unstructured platform dashboard](https://platform.unstructuredapp.io), open **API Keys**, and generate a new key. Copy the key and paste it into the **API key** field in PostHog.

Leave **API host** blank unless Unstructured provisioned your account with a custom API URL, in which case enter that origin (for example `https://platform.unstructuredapp.io`).

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

The `notifications` table supports incremental sync on `created_at`. Every other table syncs as a full refresh: workflows and connectors are mutable configuration objects, and jobs have no server-side time filter. These are low-volume inventory tables, so a full refresh each sync always reflects the current state.

The `job_details` and `job_failed_files` tables make one request for each job on every sync. `job_failed_files` skips jobs that report no failed files. `job_details` is off by default, so turn it on only when you need per-node processing counts.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |
| `API host` | text | No |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `workflows` | Workflows that define how Unstructured ingests, processes, and routes documents from sources to destinations. | Full refresh | — | — |
| `jobs` | Individual runs of a workflow at a point in time, including status and runtime. | Full refresh | — | — |
| `sources` | Source connectors that ingest files or data into Unstructured from an external location. | Full refresh | — | — |
| `destinations` | Destination connectors that send Unstructured's processed data to an external location. | Full refresh | — | — |
| `job_details` | Processing details of each job: per-node document counts, overall outcome, and progress. | Full refresh | — | — |
| `job_failed_files` | Files that failed to process in a job, with the workflow node that failed each one and the error. | Full refresh | — | — |
| `notifications` | Platform notification events, such as a job that started, completed, or failed. | Incremental, Full refresh | created\_at | — |

## Troubleshooting

-   **Invalid API key** – regenerate the key in the Unstructured platform dashboard and reconnect. The key is account-wide, so a valid key can read every table.
-   **Custom API host** – if your account uses a custom API URL, make sure the **API host** field matches the origin Unstructured gave you. The scheme is forced to HTTPS.

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.