Linking Freshsales as a source
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.
Contents
Enter your Freshsales domain and API key to pull your Freshsales (Freshworks CRM) data into the PostHog data warehouse.
Adding a data source
- Go to the sources tab of the data pipeline section in PostHog.
- Click + New source and then click Link next to Freshsales.
- 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
yourcompanyforyourcompany.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.
- Freshsales domain is your bundle alias — the subdomain of your Freshsales URL (for example
- Back in PostHog, enter your Freshsales domain and API key, then click Next.
- 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 | — | — |
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 | — | — |