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 on the Connections page and when selecting a connection for a package.|
|•||API Version - determines which version of Freshdesk API to use - v1 or v2. Note that API v2 version provides access to more Zendesk objects than API v1, and the structure of common objects may be different for different API versions. |
|•||Url - the 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:|
|o||Sign in to your Freshdesk Support Portal|
|o||Click your profile picture in the top right corner of your portal page.|
|o||Go to the Profile settings page.|
|o||Your API key will be available below the change password section to the right.|
|•||Metadata Cache - Determines how often to update cached metadata for the connection. By default, Skyvia caches metadata of available objects for cloud sources. You can configure how often the cache is refreshed automatically or reset in manually on the Connection Details page of the corresponding connection by clicking the Clear link in the Metadata cache parameter in the Parameters pane. The following values are available for this setting:|
|o||Disabled - the metadata cache is not created, and metadata are queried automatically whenever the connection is opened.|
|o||One Hour - the metadata cache expires after one hour since the previous refresh, and it is refreshed after this when the connection is opened.|
|o||One Day - the metadata cache expires after one day since the previous refresh, and it is refreshed after this when the connection is opened.|
|o||One Week - the metadata cache expires after one week since the previous refresh, and it is refreshed after this when the connection is opened.|
|o||One Month - the metadata cache expires after one month since the previous refresh, and it is refreshed after this when the connection is opened.|
|o||Infinite - the cache is never reset automatically. Default value.|