Skip to main content Skip to complementary content

Freshdesk 

Freshdesk is an online cloud-based customer support software providing help desk support.

Freshdesk integration replicates data using the Freshdesk REST API.

See the Schema section for a list of objects available for replication.

Preparing for authentication

To access your data, you need to authenticate the connection with your account credentials.

Information noteMake sure that the account you use has read access to the tables you want to fetch.

Creating the connection

For more information, see Connecting to SaaS applications.

  1. Fill in the required connection properties.
  2. Provide a name for the connection in Connection name.

  3. Select Open connection metadata to define metadata for the connection when it has been created.

  4. Click Create.

Connection settings
SettingDescription
Data gateway

Select a Data Movement gateway if required by your use case.

Information note

This field is not available with the Qlik Talend Cloud Starter subscription, as it does not support Data Movement gateway. If you have another subscription tier and do not want to use Data Movement gateway, select None.

For information on the benefits of Data Movement gateway and use cases that require it, see Qlik Data Gateway - Data Movement.

Start Date

Enter the date, in the format MM/DD/YYYY, from which the data must be replicated from your source to your target.

Subdomain

You can find your subdomain in the URL of your Freshdesk account. If the URL is your-org-name.freshdesk.com, the subdomain is your-org-name.

API KeyAPI key.

Schema

Information note

Schemas and naming conventions can change from version to version. It is recommended to verify your version before continuing.

The schema and info displayed below is for version 1.

Depending on your destination, table and column names may not appear as they are outlined below.

agents

The agents table contains info about the agents in your Freshdesk account.

Replication Method

CDC

Primary Key

id

Replication Key

updated_at

Useful links

Freshdesk documentation

Freshdesk API method

companies

The companies table contains info about the companies your various customers and contacts belong to.

Custom Fields

If applicable, Stitch will replicate custom fields related to companies in Freshdesk.

Replication Method

CDC

Primary Key

id

Replication Key

updated_at

Useful links

Freshdesk documentation

Freshdesk API method

conversations

The conversations table contains info about replies and public/private notes added to the tickets in your Freshdesk account.

Replication Method

CDC

Primary Key

id

Replication Key

updated_at

Useful links

Freshdesk documentation

Freshdesk API method

groups

The groups table contains info about the groups your agents belong to.

Replication Method

CDC

Primary Key

id

Replication Key

updated_at

Useful links

Freshdesk documentation

Freshdesk API method

roles

The roles table contains info about the various roles that can be assigned to team members in your Freshdesk account.

Replication Method

CDC

Primary Key

id

Replication Key

updated_at

Useful links

Freshdesk documentation

Freshdesk API method

satisfaction_ratings

The satisfaction_ratings table contains info about customer satisfaction survey responses, or satisfaction ratings.

Replication Method

CDC

Primary Key

id

Replication Key

updated_at

Useful links

Freshdesk documentation

Freshdesk API method

tickets

The tickets table contains info about the tickets in your Freshdesk account.

Custom Fields

If applicable, Stitch will replicate custom fields related to tickets in Freshdesk.

Replication Method

CDC

Primary Key

id

Replication Key

updated_at

Useful links

Freshdesk API method

time_entries

The time_entries table contains info about the time entries entered by agents working on tickets.

Replication Method

CDC

Primary Key

id

Replication Key

updated_at

Useful links

Freshdesk API method

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!