Freshdesk (Edge)

Last updated on Nov 14, 2026

Freshdesk is a customer support platform from Freshworks. Support teams use it to manage tickets from multiple channels, maintain a knowledge base, and measure customer satisfaction.

Hevo uses the Freshdesk API to replicate the tickets, conversations, contacts, companies, agents, automation rules, surveys, knowledge base, and discussions of your Freshdesk account to the Destination of your choice. To ingest data, you must provide Hevo with the API key of a Freshdesk agent and the subdomain of your Freshdesk account.


Supported Features

Feature Name Supported
Capture deletes Yes
History mode No
Custom data (user-configured tables & fields) Yes, the custom fields of tickets, contacts, and companies
Data blocking (skip objects and fields) Yes
Resync (objects and Pipelines) Yes
API configurable Yes

Handling of Deletes

Hevo captures the deletes of the Freshdesk objects as follows:

Deletes Captured Objects
In each run, by comparing the data All objects, except Contact.

Hevo ingests all the records of these objects in each run, and marks the records that are no longer returned by Freshdesk as deleted by setting the value of the metadata column __hevo__marked_deleted to True. For example, a company that you delete in Freshdesk is marked as deleted in the next run.
Through the source data Contact and Ticket History.

Hevo also ingests the contacts and tickets that are deleted in Freshdesk, and the value of the deleted column of these records is set to True. A contact that you permanently delete in Freshdesk is no longer returned by Freshdesk and remains in the Destination.

Source Considerations

  • If the agent whose API key you use does not have access to an object, for example, because the agent’s role or your Freshdesk plan does not include it, Hevo marks the object as inaccessible and continues to ingest data for the other objects.

  • Hevo ingests all the tickets in each run, with 100 tickets per API request, and reads the conversations of each updated ticket with a separate API request. As a result, the number of API requests in each run increases with the number of tickets.

  • Hevo creates a table in the Destination only for the objects that have data. For example, if you do not use the Freshdesk forums, the Discussion Category, Discussion Forum, Discussion Topic, and Discussion Comment tables are not created.


Limitations

  • Hevo supports only the Freshdesk domains, such as acme.freshdesk.com, and not custom domains.

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Nov-05-2026 2.54 New document.

Tell us what went wrong