Integrations / Freshservice

Freshservice

Freshservice IT service management for tickets, requesters, agents, assets, changes, problems, and service desk automation.

OAuth 2.0

Indexes

Actions

Events

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events Yes

Before you connect

Prerequisites

A Freshservice account you can administer.

Account admin who can approve OAuth or create API keys.

Vendor setup

Get the credential

Prefer Connect in Telara

Settings → Integrations → Freshservice. If Telara offers OAuth, click Connect and approve access. You do not create a Freshworks OAuth app.

Or create an API key

In Freshservice, click your profile picture → Profile Settings. Copy the API Key shown there. Freshservice uses HTTP Basic: the key is the username and the password is X (or empty, matching the form).

Paste in Telara

On the Connect form, enter your Freshservice domain (the subdomain) and the API key if you are not using OAuth.

In Telara

Connect in Telara

OAuth 2.0

Freshworks/Freshservice OAuth app for external apps. Scope IDs are selected from the Freshworks app/OAuth credential setup; Telara requests broad Freshservice scopes and enforces tenant/user policy internally.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Basic auth

Freshservice API key auth over Basic Auth. Use the API key as username and any non-empty password, with domain as the account subdomain.

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for

Domain
API key

Knowledge

What gets indexed

Resource	Coverage
Tickets	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Tickets	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Tickets.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

ITSM vs Freshdesk are different products and different domains.

Agents who cannot see a workspace’s tickets will produce an empty list.