> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt # Linking Hyros as a source Canonical URL: https://posthog.com/docs/data-pipelines/sources/hyros > **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 Hyros connector syncs leads, sales, calls, 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. See the [Hyros API documentation](https://api-docs.hyros.com) for how to create the credentials this source needs. You'll be asked for: - **API key**: find this in Hyros under Settings > Profile. ## 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. All Hyros tables are full refresh. Each sync replaces the contents of the table. ## Configuration | Option | Description | | --- | --- | | `API key` **Type:** password **Required:** True | Find this in Hyros under Settings > Profile. | ## Supported tables | Table | Description | Sync method | Incremental field | Primary key | | --- | --- | --- | --- | --- | | `Leads` | A person Hyros has attributed to a source, with their tags, stage and first/last touch attribution. | Incremental, Full refresh | lastUpdatedDate | — | | `Sales` | A sale attributed to a lead, with pricing, refund state, and first/last touch attribution. | Incremental, Full refresh | creationDate | — | | `Calls` | A phone call attributed to a lead, with its qualification state and attribution. | Incremental, Full refresh | creationDate | — | | `Subscriptions` | A recurring subscription attributed to a lead, with its billing state and attribution. | Incremental, Full refresh | startDate | — | | `Sources` | A traffic source Hyros tracks, either organic or tied to an ad platform account. | Full refresh | — | — | | `Tags` | A tag created in Hyros, with the count of leads currently carrying it. | Full refresh | — | — | | `Keywords` | A keyword tracked against a Google Ads ad group. | Full refresh | — | — | | `Stages` | A lead stage defined in the account, with the count of leads currently in it. | Full refresh | — | — | | `AdAccounts` | An ad account connected to Hyros, such as a Meta or Google Ads account. | Full refresh | — | — | | `Ads` | An individual ad from a connected ad platform, with the Hyros source it is tracked by. | Full refresh | — | — | | `Products` | A product sold in the account, with its price and cost of goods. | Full refresh | — | — | | `SaleConversionPaths` | A sale with the ordered source touches it was attributed with, up to the sale date. | Incremental, Full refresh | creationDate | — | | `CallConversionPaths` | A call with the ordered source touches it was attributed with, up to the call date. | Incremental, Full refresh | creationDate | — | | `LeadConversionPaths` | A lead with its full ordered list of source touches. | Full refresh | — | — | ## Troubleshooting - If the connection fails with an authorization error, the API key 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.