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

# Linking Freshsales as a source

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

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

## On this page

- [Adding a data source](#adding-a-data-source)
- [Available tables](#available-tables)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)

![](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

Enter your Freshsales domain and API key to pull your Freshsales (Freshworks CRM) data into the PostHog data warehouse.

## 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 Freshsales.
3.  In Freshsales, go to **Profile settings → API settings** to find both credentials:
    -   **Freshsales domain** is your bundle alias — the subdomain of your Freshsales URL (for example `yourcompany` for `yourcompany.myfreshworks.com`).
    -   **API key** is sent as `Token token=<key>`. The key only exposes data the associated user can access, so make sure that user can read the objects you want to sync.
4.  Back in PostHog, enter your **Freshsales domain** and **API key**, then click **Next**.
5.  Select the tables you want to sync, set the sync method and frequency, then click **Import**.

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

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `contacts` | Contacts | Full refresh |
| `sales_accounts` | Sales accounts | Full refresh |
| `deals` | Deals | Full refresh |
| `leads` | Leads (not present on all accounts) | Full refresh |
| `sales_activities` | Sales activities | Full refresh |
| `open_tasks` | Open tasks | Full refresh |
| `completed_tasks` | Completed tasks | Full refresh |
| `past_appointments` | Past appointments | Full refresh |
| `upcoming_appointments` | Upcoming appointments | Full refresh |

**Full refresh** tables reload all data on each sync.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Freshsales domain` | text | Yes |
| `API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `contacts` | A person tracked in the CRM as a potential or existing customer. | Full refresh | — | — |
| `sales_accounts` | A company or organization tracked in the CRM. | Full refresh | — | — |
| `deals` | A sales opportunity tracked through the CRM's pipeline stages. | Full refresh | — | — |
| `leads` | An unqualified prospect not yet converted to a contact (legacy lead-based accounts). | Full refresh | — | — |
| `sales_activities` | A logged sales activity (call, email, meeting) recorded against a record. | Full refresh | — | — |
| `open_tasks` | A task that is still open (incomplete). | Full refresh | — | — |
| `completed_tasks` | A task that has been completed. | Full refresh | — | — |
| `past_appointments` | An appointment whose scheduled time is in the past. | Full refresh | — | — |
| `upcoming_appointments` | An appointment scheduled for the future. | Full refresh | — | — |
| `owners` | A user in the Freshsales portal. Resolves the owner\_id carried on contacts, accounts, deals, tasks and sales activities. | Full refresh | — | — |
| `deal_stages` | A stage in a deal pipeline. Resolves the deal\_stage\_id carried on deals. | Full refresh | — | — |
| `deal_pipelines` | A deal pipeline configured in the portal. Resolves the deal\_pipeline\_id carried on deals. | Full refresh | — | — |
| `lifecycle_stages` | A lifecycle stage configured in the portal. Resolves the lifecycle\_stage\_id carried on contacts and accounts. | Full refresh | — | — |
| `contact_statuses` | A contact status configured in the portal. Resolves the contact\_status\_id carried on contacts. | Full refresh | — | — |
| `territories` | A sales territory configured in the portal. Resolves the territory\_id carried on contacts, accounts and deals. | Full refresh | — | — |
| `lead_sources` | A lead source configured in the portal. Resolves the lead\_source\_id carried on contacts and deals. | Full refresh | — | — |
| `sales_activity_types` | A sales activity type configured in the portal. Resolves the sales\_activity\_type\_id carried on sales activities. | Full refresh | — | — |
| `sales_activity_outcomes` | An outcome that can be recorded on a sales activity. Resolves the sales\_activity\_outcome\_id carried on sales activities. | Full refresh | — | — |
| `lists` | A marketing list of contacts. | Full refresh | — | — |
| `list_contacts` | Membership of contacts in marketing lists. One row per contact per list, with the contact's details. | Full refresh | — | — |