Freshservice
Integrate Freshservice to retrieve your CMDB inventory
The Freshservice connector allows you to retrieve your Freshservice CMDB inventory (assets, hardware characteristics, users, and locations) directly into OverView.
Objective
The Freshservice connector retrieves the following information:
- CMDB asset inventory (workstations, servers, VMs, network equipment, mobile devices, printers)
- Hardware characteristics (serial number, maker, model, processor, memory, disk space)
- Network information (hostname, domain, IP address, MAC address)
- Operating system and version
- Users assigned to assets (requesters and agents: first name, last name, email, job title)
- Locations (site, address, city, country, zip code)
- Metadata: department, group, asset tag, asset state, criticity (derived from impact)
Prerequisites
- A Freshservice account with a role granting read access to the CMDB and to users
- The API key of that account
- Network connectivity from OverView to your Freshservice instance (
https://<your-domain>.freshservice.com)
Information to provide in OverView
| Field | Description |
|---|---|
| Domain | Freshservice subdomain (e.g., acme for acme.freshservice.com) |
| API Key | API key of the Freshservice service account |
| API URL | Custom API base URL (optional — overrides the domain-based URL) |
Procedure
Step 1 — Create a service account (recommended)
- Log in to your Freshservice instance with an administrator account.
- Go to Admin > User Management > Agents.
- Create an agent dedicated to the integration (for example
OverView Connector). - Assign it a read-only role covering assets, users, and reference objects (see Required Permissions).
Step 2 — Retrieve the API key
- Log in with the service account created in the previous step.
- Click your avatar in the top-right corner, then Profile settings.
- In the right-hand panel, under Your API Key, click View API Key and copy the key.
The API key is bound to the logged-in agent and inherits its permissions. If the account is deactivated or its role changes, the import will fail or return incomplete data.
Step 3 — Configure the connector in OverView
- In OverView, go to Data Sources Settings > Sources.
- Select Freshservice and click Configure.
- Fill in the fields:
- Domain: your subdomain, without
.freshservice.com(e.g.,acme) - API Key: the key copied in step 2
- API URL: only fill this in if your instance uses a custom API URL
- Domain: your subdomain, without
- Click Save Configuration.
Required Permissions
The account associated with the API key must have read access to the following API v2 endpoints:
| Endpoint | Purpose |
|---|---|
/agents/me | Credentials validation |
/assets | Asset inventory (with include=type_fields) |
/asset_types | Asset type labels |
/departments | Departments |
/locations | Locations and addresses |
/vendors | Makers |
/products | Product models |
/groups | Groups |
/requesters | Users (requesters) |
/agents | Users (agents) |
Official Documentation
For additional information, refer to the Freshservice API v2 documentation.
Alternative: file import through DropPoint
The API access described above is the recommended method for this connector. Where it is not available (a segregated network, a version or licence without API, an export you already produce), OverView accepts file exports, to be uploaded to the bucket dedicated to Freshservice.
Bucket : s3://freshservice/
Example : s3://freshservice/export.csv
The procedure is described in the OverView DropPoint guide: generating credentials, configuring the client, then sending files from the OverView web interface, the AWS CLI or an SDK. Its examples come pre-filled with this bucket when you follow this link.