Connecting to Freshdesk
Freshdesk is a cloud customer support ticketing system.
Data integration: Skyvia supports importing data to and from Freshdesk, exporting Freshdesk data to CSV files, replicating Freshdesk data to relational databases, and synchronizing Freshdesk data with other cloud apps and relational databases.
Backup: Skyvia Backup supports Freshdesk backup.
Query: Skyvia Query supports Freshdesk.
Freshdesk-Specific Features and Limitations
Skyvia does not support custom Freshdesk fields having double quotation marks in their name.
To connect to Freshdesk, you need to specify the url to connect to, API version to use, and API key.
You need to specify the following parameters for Freshdesk connection:
- Name — connection name that will be used to identify the connection in the objects list and when selecting a connection for a package.
- API Version — Freshdesk API to use (v1 or v2). Note that API v2 version provides access to more Freshdesk objects than API v1, and structure of common objects may be different for different API versions.
- Url — address of your Freshdesk subdomain.
API Key — an automatically generated key that is used for connecting to Freshdesk. To find your API key, perform the following actions:
- Sign in to your Freshdesk Support Portal
- Click your profile picture in the top right corner of your portal page.
- Go to the Profile settings page.
- Your API key will be available below the change password section to the right.
Metadata Cache — this parameter determines how often the cached metadata are updated. By default, Skyvia caches metadata of available objects in cloud sources. When creating a connection, you can configure how often cache is refreshed or, when the connection already exists, you can reset it manually on the Connection Editor page by clicking the Clear Cache button. The following values are available for this setting:
- Disabled — metadata cache is not created; metadata are queried automatically whenever the connection is opened.
- One Hour — metadata cache expires one hour after the last refresh; it is refreshed when the connection is opened again.
- One Day — metadata cache expires one day after the last refresh; it is refreshed when the connection is opened again.
- One Week — metadata cache expires one week after the last refresh; it is refreshed when the connection is opened again.
- One Month — metadata cache expires one month after the last refresh; it is refreshed when the connection is opened again.
- Infinite — cache is never reset automatically. Default value.