Source connector

Freshdesk connector

Freshdesk integration for databases, warehouses and BI tools

Customer support helpdesk with tickets, SLAs, and agent workflows. Datrise captures Freshdesk entities such as tickets, contacts, agents, SLA events, and satisfaction scores, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Freshdesk API v2 authenticates with API key, HTTP Basic, incremental runs key on updated_since, and Freshdesk caps calls at Plan-dependent, account-wide: 3,000 API calls per hour on Blossom/Garden plans, 5,000 per hour on Estate/Forest plans, reported via X-RateLimit-Total/X-RateLimit-Remaining headers.

Of the 5 objects, 4 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `freshdesk_tickets`) with a schema derived from the Freshdesk API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Freshdesk pipeline page, and join the waitlist to get the Freshdesk connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Freshdesk data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
tickets	freshdesk_tickets	Upsert by primary key, incremental on updated-at
contacts	freshdesk_contacts	Upsert by primary key, incremental on updated-at
agents	freshdesk_agents	Upsert by primary key, incremental on updated-at
SLA events	freshdesk_sla_events	Append-only, incremental by timestamp
satisfaction scores	freshdesk_satisfaction_scores	Upsert by primary key, incremental on updated-at

Freshdesk API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Freshdesk API v2
Authentication	API key, HTTP Basic — HTTP Basic Auth with the account API key as the username and any string (commonly `X`) as the password; the key is found on the agent's profile page under the API key section.
Pagination	page — List endpoints take `page` (starting at 1) and `per_page` (default 30, max 100); the response `link` header carries the next-page URL when more results remain.
Rate limit	Plan-dependent, account-wide: 3,000 API calls per hour on Blossom/Garden plans, 5,000 per hour on Estate/Forest plans, reported via X-RateLimit-Total/X-RateLimit-Remaining headers
Incremental cursor	updated_since — `updated_since` takes an ISO 8601 timestamp on the List Tickets endpoint and is required to see tickets older than the API's 30-day default window.
Webhooks	Yes — Trigger Webhook action within Automation rules
Bulk export	No
Deletes detectable	Yes — `GET /api/v2/tickets?filter=deleted` (or `filter=spam`) surfaces soft-deleted and spam-marked tickets, which are excluded from normal list results by default

Official API reference

What bites when replicating Freshdesk

The List Tickets endpoint returns only tickets created in the past 30 days unless `updated_since` is explicitly set, so a first-run sync without that parameter silently misses everything older than a month.
List Tickets is hard-capped at a maximum of 300 pages (30,000 tickets) per query regardless of date range, forcing large ticket volumes to be pulled in narrower `updated_since`-bounded chunks chained together.
Deleted and spam-marked tickets are excluded from default list results; a connector must separately query `filter=deleted` and `filter=spam` to detect removals, or it will never see them.
Requesting related data via the `include` parameter consumes an additional 2 API credits per include per record, which can multiply effective rate-limit consumption well beyond the raw request count for enriched pulls.

Compare this against every other documented API

Popular destinations for Freshdesk

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Freshdesk connector FAQ

What Freshdesk data does the connector extract?: 5 objects: tickets, contacts, agents, SLA events and satisfaction scores. Each lands in its own table with types preserved; history-style objects (1: SLA events) load as append-only streams.
Is the Freshdesk integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Freshdesk data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Freshdesk → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Freshdesk pipeline with guided onboarding

Join the waitlist to get priority access for Freshdesk integrations with guided setup, schema-aware mapping, and production-grade incremental sync.