Freshservice
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.
Connect Freshservice to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
Enter your Freshservice domain and API key to pull your Freshservice ITSM data into the PostHog Data warehouse.
Your domain is the subdomain in your Freshservice URL — e.g. acme for acme.freshservice.com.
Your API key is on your Freshservice profile settings page (click your profile picture → Profile settings; the API key is shown in the right sidebar).
Configuration
| Option | Type | Required |
|---|---|---|
Freshservice domain | text | Yes |
API key | password | Yes |
Linking Freshservice to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select Freshservice
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
tickets | A service request or incident raised by a requester and tracked through to resolution. | Incremental, Full refresh | updated_at | — |
problems | A problem record tracking the root cause behind one or more incidents. | Full refresh | — | — |
changes | A change request tracking a planned modification to the IT environment. | Full refresh | — | — |
releases | A release record tracking the rollout of changes to production. | Full refresh | — | — |
requesters | An end user who can raise tickets with the service desk. | Full refresh | — | — |
requester_groups | A group of requesters, used to scope access and automation. | Full refresh | — | — |
agents | A service desk agent who responds to and works on tickets. | Full refresh | — | — |
agent_groups | A group of agents that tickets can be assigned to. | Full refresh | — | — |
agent_roles | A role defining the set of privileges granted to agents. | Full refresh | — | — |
assets | A configuration item (hardware, software, or other tracked asset) in the CMDB. | Full refresh | — | — |
asset_types | A classification for assets in the CMDB (e.g. Hardware, Software, Business Service). | Full refresh | — | — |
software | A software application tracked for software asset management. | Full refresh | — | — |
purchase_orders | A purchase order for procuring assets or services. | Full refresh | — | — |
products | A product in the product catalog that assets can be associated with. | Full refresh | — | — |
vendors | A vendor or supplier that assets and purchase orders are associated with. | Full refresh | — | — |
locations | A physical location (site or office) that assets and users are associated with. | Full refresh | — | — |
departments | A department that groups together requesters within the organization. | Full refresh | — | — |