The CData Sync App provides a straightforward way to continuously pipeline your Freshdesk data to any database, data lake, or data warehouse, making it easily available for Analytics, Reporting, AI, and Machine Learning.
The Freshdesk connector can be used from the CData Sync application to pull data from Freshdesk and move it to any of the supported destinations.
The Sync App leverages the Freshdesk API to enable bidirectional access to Freshdesk.
For required properties, see the Settings tab.
For connection properties that are not typically required, see the Advanced tab.
Freshdesk makes use of basic authentication. To connect to data, set the following connection properties:
Domain=domainValue
This section details a selection of advanced features of the Freshdesk Sync App.
The Sync App supports the use of user defined views, virtual tables whose contents are decided by a pre-configured user defined query. These views are useful when you cannot directly control queries being issued to the drivers. For an overview of creating and configuring custom views, see User Defined Views .
Use SSL Configuration to adjust how Sync App handles TLS/SSL certificate negotiations. You can choose from various certificate formats;. For further information, see the SSLServerCert property under "Connection String Options" .
Configure the Sync App for compliance with Firewall and Proxy, including Windows proxies and HTTP proxies. You can also set up tunnel connections.
For further information, see Query Processing.
By default, the Sync App attempts to negotiate TLS with the server. The server certificate is validated against the default system trusted certificate store. You can override how the certificate gets validated using the SSLServerCert connection property.
To specify another certificate, see the SSLServerCert connection property.
To authenticate to an HTTP proxy, set the following:
Set the following properties:
This section shows the available API objects and provides more information on executing SQL to Freshdesk APIs.
Tables describes the available tables. Tables are statically defined to model Tickets, Conversations, Agents, and more.
The Sync App models the data in Freshdesk as a list of tables in a relational database that can be queried using standard SQL statements.
| Name | Description |
| Agents | Update, delete, and query from agents table |
| BusinessHours | Query from BusinessHours table |
| CannedResponses | Create, update and query from CannedResponses table |
| CannedResponsesFolder | Query from CannedResponsesFolder table |
| Companies | Create, update, delete, and query from companies table |
| Contacts | Create, update, delete, and query from contacts table |
| Conversations | Delete, and query from conversations table |
| Groups | Create, update, delete, and query from groups table |
| Mailboxes | Create, update, delete, and query from Mailboxes table |
| Products | Query from products table |
| Roles | Query from roles table |
| Skills | Create, update, delete, and query from skills table |
| SLAPolicies | Query, Create and Update SLAPolicies table |
| Surveys | Query from surveys table |
| TicketCreationAutomationRules | Create, update, delete, and query from TicketCreationAutomationRules table |
| TicketFields | Query from ticketFields table |
| Tickets | Create, update, delete, and query from tickets table |
| TicketUpdatesAutomationRules | Create, update, delete, and query from TicketUpdatesAutomationRules table |
| TimeEntries | Create, update, delete, and query from TimeEntries table |
| TimeTriggersAutomationRules | Create, update, delete, and query from TimeTriggersAutomationRules table |
Update, delete, and query from agents table
The Sync App will use the Freshdesk API to process WHERE clause conditions built with the following columns and operators. Most of the columns support server side filtering with the following operators: =,>,<,<=,>=,AND,OR. The rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM Agents WHERE Id = 100
Note: To query Agents table, All Agent APIs other than the Currently Authenticated Agent API require admin privileges.
Following is an example of how to update an agent:
UPDATE Agents SET GroupIdsAggregate = '111' WHERE Id = 100
Following is an example of how to delete an agent:
DELETE FROM Agents WHERE Id = 100
| Name | Type | ReadOnly | Description |
| Id [KEY] | Bigint | False |
ID of the agent. |
| Available | Boolean | True |
Indicates if agent is taking new tickets. |
| GroupIdsAggregate | String | False |
Group IDs associated with the agent. |
| Occasional | Boolean | True |
True if this is an occasional agent. |
| RoleIdsAggregate | String | False |
Role IDs associated with the agent. |
| Signature | String | True |
Signature of the agent in HTML format. |
| SkillIdsAggregate | String | True |
Skill ids associated with the agent. |
| TicketScope | Integer | True |
Ticket permission of the agent (1 -> Global Access, 2 -> Group Access, 3 -> Restricted Access). |
| AgentActive | Boolean | True |
Whether or not the agent has been verified. |
| AgentEmail | String | True |
Email address of the agent. |
| AgentJobTitle | String | True |
Job title of the agent. |
| AgentLanguage | String | True |
Language of the agent. |
| AgentLastLogin | Datetime | True |
Last login date of the agent. |
| AgentMobile | String | True |
Mobile phone number of the agent. |
| AgentName | String | True |
Name of the agent. |
| AgentPhone | String | True |
Telephone number of the agent. |
| AgentTimeZone | String | True |
Time zone of the agent. |
| AgentCreatedAt | Datetime | True |
Created at datetime of the agent. |
| AgentUpdatedAt | Datetime | True |
Updated at datetime of the agent. |
| CreatedAt | Datetime | True |
Agent creation timestamp. |
| UpdatedAt | Datetime | True |
Agent updated timestamp. |
| AvailableSince | Datetime | True |
Timestamp that denotes when the agent became available/unavailable. |
Query from BusinessHours table
Note: Only users with admin privileges can access the following Table.
Following is an example to select all entries from BusinessHours table:
SELECT * FROM BusinessHours
You can also select a specific entry from BusinessHours table:
SELECT * FROM BusinessHours WHERE Id = 100
| Name | Type | ReadOnly | Description |
| Id [KEY] | Bigint | False |
Business hour ID. |
| Description | String | True |
Description of the business hour. |
| Name | String | True |
Name of the business hour. |
| IsDefault | Boolean | True |
True if this is the default business hour. |
| TimeZone | String | True |
Denotes the time zone of the business hour. |
| business_hours | String | True |
Collection of start time and end time of days of a week. |
| CreatedAt | Datetime | True |
Business hour creation timestamp. |
| UpdatedAt | Datetime | True |
Business hour updated timestamp. |
Create, update and query from CannedResponses table
Note: Only users with admin privileges can access the following Table.
To query the CannedResponses table, FolderId should be mentioned in the WHERE clause. For example:
SELECT * FROM CannedResponses WHERE FolderId = 100
FolderId, Visibility, Title and ContentHTML are mandatory columns for Inserting into CannedResponses tables. For example:
INSERT INTO CannedResponses (Title, ContentHTML, Visibility, FolderId) VALUES (Sample response, 'this is also a new sample response', 0, 100)
Following is an example to update a row in CannedResponses table:
UPDATE CannedResponses SET Title = 'Updated title' WHERE Id = 100
| Name | Type | ReadOnly | Description |
| Id [KEY] | Bigint | False |
ID of the canned response. |
| Content | String | True |
Plaintext version of the canned response content. |
| ContentHTML | String | False |
HTML version of the canned response content. |
| Title | String | False |
Title of the canned response. |
| FolderId | Bigint | False |
Id of CannedResponseFolder containing this canned response. |
| Visibility | Int | False |
Denotes the visibility of the canned response. Possible values are: 0- If it is visible to all agents, 1- If it is personal. |
| CreatedAt | Datetime | True |
Canned response creation timestamp. |
| UpdatedAt | Datetime | True |
Canned response updated timestamp. |
Query from CannedResponsesFolder table
Note: Only users with admin privileges can access the following Table.
Following is an example to select all entries from CannedResponsesFolder table:
SELECT * FROM CannedResponsesFolder
You can also select a specific entry from CannedResponsesFolder table:
SELECT * FROM CannedResponsesFolder WHERE Id = 100
Name is a mandatory columns for Inserting into CannedResponsesFolder table.
INSERT INTO CannedResponsesFolder (Name) VALUES (directoryA)
Following is an example to update CannedResponsesFolder:
UPDATE CannedResponsesFolder SET Name = 'updated name' WHERE Id = 100
| Name | Type | ReadOnly | Description |
| Id [KEY] | Bigint | False |
ID of the canned response folder. |
| Name | String | False |
Name of the canned response folder. |
| Personal | Boolean | False |
Set true if the folder can be accessed only by you. |
| ResponsesCount | Int | False |
Number of canned responses in the folder. |
| CreatedAt | Datetime | True |
Canned response folder creation timestamp. |
| UpdatedAt | Datetime | True |
Canned response folder updated timestamp. |
Create, update, delete, and query from companies table
The Sync App will use the Freshdesk API to process WHERE clause conditions built with the following columns and operators. Most of the columns support server side filtering with the following operators: =,>,<,<=,>=,AND,OR. The rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM Companies WHERE CreatedAt >= '2017-10-01' AND CreatedAt <= '2017-10-07'
The API allows only a subset of columns to be used as filter criteria in the WHERE clause. The following columns can be used:
Note: To filter all companies created on a specific day (e.g: 2019-09-23), query should be structured as:
WHERE CreatedAt >= '2019-09-22' AND CreatedAt <= '2019-09-24'
Name is mandatory for creating a new company. Following is an example of creating a new company:
INSERT INTO Companies (Name, Description) VALUES ('Example', 'Example description of new company')
Following is an example of how to update a company:
UPDATE Companies SET Description = 'New description' WHERE Id = 786
Following is an example of how to delete from Companies table:
DELETE FROM Companies WHERE Id = 786
| Name | Type | ReadOnly | Description |
| AccountTier | String | False |
Classification based on how much value the company brings to your business. |
| CreatedAt | Datetime | True |
Company creation timestamp. |
| Description | String | False |
Description of the company. |
| DomainsAggregate | String | False |
Domains associated with the company. |
| HealthScore | String | False |
The strength of your relationship with the company. |
| Id [KEY] | Bigint | False |
ID of the company. |
| Industry | String | False |
The industry the company serves in. |
| Name | String | False |
Name of the company. |
| Note | String | False |
Any notes about the company. |
| RenewalDate | Date | False |
Date when your contract or relationship with the company is due for renewal. |
| UpdatedAt | Datetime | True |
Company updated timestamp. |
Create, update, delete, and query from contacts table
The Sync App will use the Freshdesk API to process WHERE clause conditions built with the following columns and operators. Most of the columns support server side filtering with the following operators: =,>,<,<=,>=,AND,OR. The rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM Contacts WHERE Active = false AND (Email = '[email protected]' OR CompanyId = 1)
The API allows only a subset of columns to be used as filter criteria in the WHERE clause. The following columns can be used:
Note: To filter all contacts created on a specific day (e.g: 2019-09-23), query should be structured as:
WHERE CreatedAt >= '2019-09-22' AND CreatedAt <= '2019-09-24'
Name and Email are mandatory for creating a new contact. Following is an example of creating a new contact:
INSERT INTO Contacts (Name, Email, Language) VALUES ('Example', '[email protected]', 'English')
Following is an example of how to update a contact:
UPDATE Contacts SET Active = true WHERE Id = 786
Following is an example of how to delete from Contacts table:
DELETE FROM Contacts WHERE Id = 786
| Name | Type | ReadOnly | Description |
| Active | Boolean | False |
True if contact has been verified. |
| Address | String | False |
Address of the contact. |
| CompanyId | Bigint | False |
Id of primary company of the contact. |
| CreatedAt | Datetime | True |
Contact creation timestamp. |
| Deleted | Boolean | False |
True if the contact has been deleted. |
| Description | String | False |
A short description of the contact. |
| String | False |
Email of the contact. | |
| Id [KEY] | Bigint | False |
ID of the contact. |
| JobTitle | String | False |
Job title of the contact. |
| Language | String | False |
Language of the contact. |
| Name | String | False |
Name of the contact. |
| OtherEmailsAggregate | String | False |
Additional emails associated with the contact. |
| Phone | String | False |
Telephone number of the contact. |
| Mobile | String | False |
Mobile number of the contact. |
| TimeZone | String | False |
Time zone of the contact. |
| Tag | String | False |
Tag associated with the contact. |
| UpdatedAt | Datetime | True |
Contact updated timestamp. |
| ViewAllTickets | Boolean | False |
True if the contact can see all tickets that are associated with the company to which he belong. |
| State | String | False |
State of the contact. |
Delete, and query from conversations table
To query the Conversations table, TicketId should be mentioned in the WHERE clause. For example:
SELECT * FROM Conversations WHERE TicketId = 100
Note: The Conversations table can only be filtered on TicketId.
Following is an example of how to delete from the Conversations table:
DELETE FROM Conversations WHERE Id = 786
| Name | Type | ReadOnly | Description |
| Id [KEY] | Bigint | False |
ID of the conversation. |
| Body | String | False |
Content of the conversation in HTML. |
| BodyText | String | False |
Content of the conversation. |
| FromEmail | String | False |
Email address the message was sent from. |
| Incoming | Boolean | False |
True if a particular conversation should appear as being created from outside (i.e., not through web portal) |
| Private | Boolean | False |
True if the note is private |
| SupportEmail | String | False |
Email address from which replies are sent. |
| Source | Integer | False |
Denotes the type of conversation. |
| TicketId | Integer | False |
Ticket id to which conversation is added. |
| ToEmailsAggregate | String | False |
Email addresses of agents/users who need to be notified about this conversation |
| UserId | Bigint | False |
ID of the agent who added conversation. |
| CreatedAt | Datetime | True |
Conversation creation timestamp. |
| UpdatedAt | Datetime | True |
Conversation updated timestamp. |
Create, update, delete, and query from groups table
The Sync App will use the Freshdesk API to process WHERE clause conditions built with the following columns and operators. Most of the columns support server side filtering with the following operators: =,>,<,<=,>=,AND,OR. The rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM Groups WHERE Id = 100
Note: Only users with admin privileges can access this Table.
Name is a mandatory column for inserting into Groups table. For example:
INSERT INTO Groups (Name, Description, AutoTicketAssign) VALUES ('Example', 'Example Description...', false)
Following is an example of how to update a group:
UPDATE Groups SET Description = 'New description...' WHERE Id = 100
Following is an example of how to delete from Groups table:
DELETE FROM Groups WHERE Id = 786
| Name | Type | ReadOnly | Description |
| AgentIdsAggregate | String | False |
IDs of the agents in the group. |
| AutoTicketAssign | Integer | False |
Whether automatic ticket assignment is enabled or not, and which type. |
| BusinessHourId | Bigint | False |
Unique ID of the business hour of the group. |
| CreatedAt | Datetime | True |
Group created timestamp. |
| Description | String | False |
Description of the group. |
| EscalateTo | Bigint | False |
ID of user to whom an escalation email is sent. |
| Id [KEY] | Bigint | False |
ID of the group. |
| Name | String | False |
Name of the group. |
| UnassignedFor | String | False |
Time after which escalation email is sent. |
| UpdatedAt | Datetime | True |
Group updated timestamp. |
Create, update, delete, and query from Mailboxes table
Note: Only users with admin privileges can access the following Table.
Following is an example to select all entries from Mailboxes table:
SELECT * FROM Mailboxes
The API allows only a subset of columns to be used as filter criteria in the WHERE clause. The filters listed can also be combined using AND OR. The following columns can be used:
SupportEmail and MailboxType are mandatory to Insert into Mailboxes table. For instance:
INSERT INTO Mailboxes (SupportEmail, Name, MailboxType) VALUES ('[email protected]', 'Test', 'freshdesk_mailbox')
UPDATE Mailboxes SET Name = 'Test mailbox' WHERE Id = 786
Following is an example of how to delete from the Mailboxes table:
DELETE FROM Mailboxes WHERE Id = 786
| Name | Type | ReadOnly | Description |
| Id [KEY] | Bigint | False |
Unique ID of the email mailbox. |
| AccessType | String | False |
Denotes if the mailbox is to be used for incoming, outgoing or both.Takes the values 'incoming', 'outgoing' or 'both'. |
| Active | Boolean | True |
True if the mailbox is verified and activated. |
| Authentication | String | False |
Denotes the type of authentication that should be used authenticate the mailbox. It can be plain/login/CRAM-MD5. |
| CustomMailbox | String | False |
Mandatory if the mailbox is of the type custom mailbox. This field contains the incoming and/or outgoing configurations of the mailbox based on what access type is set. |
| DefaultReplyEmail | Boolean | False |
True if the email associated to a product, is the primary email. |
| DeleteFromServer | Boolean | False |
If set to true, Freshdesk is given the permission to delete the email from the mailbox after the ticket is created. |
| FailureCode | String | True |
Denotes the failure message if any in the custom incoming mailbox. |
| ForwardEmail | String | True |
Denotes the email address to which your support emails gets forwarded. |
| FreshdeskMailbox | String | True |
If the mailbox is of the type Freshdesk mailbox this field contains the forward email to which your support emails gets forwarded. |
| GroupId | Bigint | False |
Denotes the group ID to which the email is associated. |
| Incoming | String | False |
Contains the incoming configuration of the custom mailbox. |
| MailServer | String | False |
Denotes the server used by incoming and/or outgoing configurations of the mailbox. |
| MailboxType | String | False |
Denotes if the mailbox uses a Freshdesk mailbox or a custom mailbox setup by the customer. It takes the values 'freshdesk_mailbox' or 'custom_mailbox'. |
| Name | String | False |
Name of the email mailbox. |
| Outgoing | String | True |
Contains the outgoing configuration of the custom mailbox. |
| Password | String | False |
Denotes the password that will be used to authenticate the custom mailbox. |
| Port | Int | False |
Denotes the port used by incoming and/or outgoing configurations of the mailbox. |
| ProductId | Bigint | False |
Denotes the product ID to which the email is associated. |
| SupportEmail | String | False |
Denotes your support email address. |
| UseSSL | Boolean | False |
Denotes if the incoming and/or outgoing configuration should use ssl while authenticating the mailbox. |
| Username | String | False |
username. |
| CreatedAt | Datetime | True |
Mailbox creation timestamp. |
| UpdatedAt | Datetime | True |
Mailbox updated timestamp. |
Query from products table
Note: Only users with admin privileges can access the following Table.
Following is an example to select all entries from Products table:
SELECT * FROM Products
You can also select a specific entry from Products table:
SELECT * FROM Products WHERE Id = 100
| Name | Type | ReadOnly | Description |
| Id [KEY] | Bigint | False |
Product ID. |
| Description | String | True |
Description of the product. |
| Name | String | True |
Name of the product. |
| CreatedAt | Datetime | True |
Product creation timestamp. |
| UpdatedAt | Datetime | True |
Product updated timestamp. |
Query from roles table
The Sync App will use the Freshdesk API to process WHERE clause conditions built with the following columns and operators. Most of the columns support server side filtering with the following operators: =,>,<,<=,>=,AND,OR. The rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM Roles WHERE Id = 100
Note: Only users with admin privileges can access the following Table. Following is an example of selecting a role:
| Name | Type | ReadOnly | Description |
| Id [KEY] | Bigint | False |
Role ID. |
| Description | String | False |
Description of the role. |
| Name | String | False |
Name of the role. |
| Default | Boolean | False |
Indicates if role is default. |
| CreatedAt | Datetime | True |
Role creation timestamp. |
| UpdatedAt | Datetime | True |
Role updated timestamp. |
Create, update, delete, and query from skills table
Following is an example to select all entries from Skills table:
SELECT * FROM Skills
You can also select a specific entry from Skills table:
SELECT * FROM Skills WHERE Id = 73000001322
Name is mandatory for creating a new skill. Following is an example of creating a new skill:
INSERT INTO Skills (Name) VALUES ('Example')
Following is an example of how to update a skill:
UPDATE Skills SET Name = 'New name' WHERE Id = 73000001322
Following is an example of how to delete from Skills table:
DELETE FROM Skills WHERE Id = 73000001322
| Name | Type | ReadOnly | Description |
| Id [KEY] | Bigint | False |
ID of the skill. |
| Name | String | False |
Name of the skill. |
| Rank | String | True |
Position/Rank of the skill. |
| Agents | String | False |
Agents associated with the skill. |
| MatchType | String | True |
Match type for conditions. |
| Conditions | String | False |
Conditions of the skill. |
| CreatedAt | Datetime | True |
Skills creation timestamp. |
| UpdatedAt | Datetime | True |
Skills updated timestamp. |
Query, Create and Update SLAPolicies table
Note: Only users with admin privileges can access the following Table.
Following is an example to select all entries from SLAPolicies table:
SELECT * FROM SLAPolicies
You can also select a specific entry from SLAPolicies table:
SELECT * FROM SLAPolicies WHERE Id = 100
| Name | Type | ReadOnly | Description |
| Id [KEY] | Bigint | False |
Business hour ID. |
| active | Boolean | False |
True if the SLA policy is active. |
| Description | String | False |
Description of the business hour. |
| IsDefault | Boolean | False |
True if this is the default business hour. |
| Name | String | False |
Name of the business hour. |
| Position | Int | False |
Denotes the order of the SLA policy. If you have configured multiple SLA policies, the first one with matching conditions will be applied to a ticket. |
| SLATarget | String | False |
Key value pair containing the object and the array of object IDs denoting the priorities and the applicable conditions. 'priority_4' - urgent, 'priority_3' - high, 'priority_2' - medium, 'priority_1' - low is mandatory and needs to be passed in the same order. |
| ApplicableTo | String | False |
Key value pair containing the 'company_ids', 'group_ids', 'sources', 'ticket_types', 'product_ids' denoting the conditions based on which the SLA policy is to be applied. One of them is mandatory |
| Escalation | String | False |
Nested collection of key value pairs containing the 'response' and 'resolution' denoting who to escalate to and when. One of them is mandatory |
| CreatedAt | Datetime | True |
Creation timestamp. |
| UpdatedAt | Datetime | True |
Updated timestamp. |
Query from surveys table
Following is an example to select all entries from Surveys table:
SELECT * FROM Surveys
You can also select a specific entry from Surveys table:
SELECT * FROM Surveys WHERE Id = 73000092562
| Name | Type | ReadOnly | Description |
| Id [KEY] | Bigint | False |
Survey ID. |
| Title | String | True |
Title of the survey. |
| Questions | String | False |
Questions associated with the survey. |
| CreatedAt | Datetime | True |
Survey creation timestamp. |
| UpdatedAt | Datetime | True |
Survey updated timestamp. |
Create, update, delete, and query from TicketCreationAutomationRules table
Note: Only users with admin privileges can access the following Table.
Following is an example to select all entries from TicketCreationAutomationRules table:
SELECT * FROM TicketCreationAutomationRules
The API allows only a subset of columns to be used as filter criteria in the WHERE clause. The filters listed can also be combined using AND OR. The following columns can be used:
Name, Actions, and Conditions are mandatory to Insert into TicketCreationAutomationRules table. For instance:
INSERT INTO TicketCreationAutomationRules (Name, Actions, Conditions) VALUES ('Test', '[{"field_name": "status", "value": 5}]', '[{"name": "condition_set_1", "match_type": "any", "properties": [{"field_name": "to_email", "resource_type": "ticket", "operator": "contains", "value": ["@lyftron.com"]}]}]')
UPDATE TicketCreationAutomationRules SET Name = 'Test2' WHERE Id = '2043002030021'
Following is an example of how to delete from the TicketCreationAutomationRules table:
DELETE FROM TicketCreationAutomationRules WHERE Id = '2043002030021'
| Name | Type | ReadOnly | Description |
| Id [KEY] | Bigint | False |
Unique ID of the TicketCreationAutomationRule. |
| Actions | String | False |
Actions of the TicketCreationAutomationRule. |
| Active | Boolean | False |
Active of the TicketCreationAutomationRule. |
| AffectedTicketsCount | Int | False |
AffectedTicketsCount of the TicketCreationAutomationRule. |
| Conditions | String | False |
Conditions of the TicketCreationAutomationRule. |
| Name | String | False |
Name of the TicketCreationAutomationRule. |
| Outdated | Boolean | True |
Outdated of the TicketCreationAutomationRule. |
| Position | Int | False |
Position of the TicketCreationAutomationRule. |
| Summary | String | True |
Summary of the TicketCreationAutomationRule. |
| CreatedAt | Datetime | True |
TicketCreationAutomationRule creation timestamp. |
| UpdatedAt | Datetime | True |
TicketCreationAutomationRule updated timestamp. |
Query from ticketFields table
Note: Users whose credentials (identified by the API key) are used to access the Table should be authorised to either view the ticket fields or create a new ticket.
The Sync App will use the Freshdesk API to process WHERE clause conditions built with the following columns and operators. Most of the columns support client side filtering with the following operators: =,>,<,<=,>=,AND,OR. The rest of the filter is executed server side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM TicketFields WHERE Type = 'default_requester'
The Freshdesk API allows only the following column(s) to be used as filter criteria in the WHERE clause:
Label, LabelForCustomers and Type are mandatory columns for Inserting into TicketFields table.
INSERT INTO TicketFields (Label, LabelForCustomers, Type) VALUES ('labelA', 'labelA', custom_text)
Following is an example to update TicketFields:
UPDATE TicketFields SET Label = 'updated label' WHERE Id = 100
Following is an example to delete a TicketFields:
DELETE FROM TicketFields WHERE Id = 100
| Name | Type | ReadOnly | Description |
| Id [KEY] | Bigint | True |
ID of the ticket field. |
| Choices | String | False |
List of values supported by the field. |
| CreatedAt | Datetime | True |
Ticket field creation timestamp. |
| CustomersCanEdit | Boolean | False |
Set to true if the field can be updated by customers. |
| Default | Boolean | True |
Set to true if the field is not a custom field. |
| Description | String | True |
Description of the ticket field |
| DisplayedToCustomers | Boolean | False |
Set to true if the field is displayed in the customer portal. |
| Label | String | False |
Display name for the field (as seen by agents). |
| LabelForCustomers | String | False |
Display name for the field (as seen in the customer portal). |
| Name | String | True |
Name of the ticket field. |
| NestedTicketFields | String | True |
Applicable only for dependent fields, this contain details of nested fields. |
| PortalCc | Boolean | True |
Applicable only for the requester field. Set to true if customer can add additional requesters to a ticket. |
| PortalCcTo | String | True |
Applicable only if portal_cc is set to true. Value will be 'all' when a customer can add any requester to the CC list and 'company' when a customer can add only company contacts to the CC list. |
| Position | Integer | False |
Position in which the ticket field is displayed in the form. |
| RequiredForAgents | Boolean | False |
Set to true if the field is mandatory for Agents. |
| RequiredForClosure | Boolean | False |
Set to true if the field is mandatory for closing the ticket. |
| RequiredForCustomers | Boolean | False |
Set to true if the field is mandatory in the customer portal. |
| Type | String | False |
For custom ticket fields, type of value associated with the field will be given (Available values are: custom_text, custom_paragraph, custom_checkbox, custom_number, custom_date, custom_decimal, nested_field, custom_dropdown, encrypted_text, secure_text) |
| UpdatedAt | Datetime | True |
Ticket field updated timestamp. |
Create, update, delete, and query from tickets table
The Sync App will use the Freshdesk API to process WHERE clause conditions built with the following columns and operators. Most of the columns support server side filtering with the following operators: =,>,<,<=,>=,AND,OR. The rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM Tickets WHERE Status = 2 AND (Priority = 1 OR Type = 'Other')
The API allows only a subset of columns to be used as filter criteria in the WHERE clause. The following columns can be used:
Email, Subject, Description, GroupId, Status and Priority are mandatory columns for Inserting/Creating a new ticket.
Every ticket uses fixed numerical values to denote its Status and Priority. Numerical values are given as:
Status:
Priority:
A new ticket can be inserted as following:
INSERT INTO Tickets (Description, Subject, Email, GroupId, Status, Priority) VALUES ('Details about the issue...', 'New support needed...', '[email protected]', 12345, 3, 2)
Following is an example to update a ticket:
UPDATE Tickets SET Priority = 1 WHERE Id = 100
Following is an example to delete a ticket:
DELETE FROM Tickets WHERE Id = 100
| Name | Type | ReadOnly | Description |
| Id [KEY] | Integer | False |
Unique ID of the ticket. |
| AssociationType | String | False |
Association type of the ticket. |
| Archived | Boolean | False |
Whether or not the ticket has been archived. |
| Attachments | String | False |
attachments associated with ticket. |
| CcEmailsAggregate | String | False |
Email address added in cc field. |
| CompanyId | Bigint | False |
ID of the company to which ticket belongs. |
| CreatedAt | Datetime | False |
Ticket creation timestamp. |
| CustomFields | String | False |
Key value pairs containing the names and values of custom fields |
| Deleted | Boolean | False |
Whether or not the ticket has been deleted. |
| Description | String | False |
HTML content of the ticket. |
| DescriptionText | String | False |
Text content of the ticket. |
| DueBy | Datetime | False |
Timestamp that denotes when the ticket is due to be resolved. |
| String | False |
Email address of the requester. | |
| EmailConfigId | Bigint | False |
ID of the email config used for the ticket. |
| FacebookId | String | False |
Facebook ID of the requester. |
| FirstResponseDueBy | Datetime | False |
Time when first response is due. |
| FirstReSponseEscalated | Boolean | False |
If ticket has been escalated as result of response. |
| FwdEmailsAggregate | String | False |
Email address while forwarding a ticket. |
| GroupId | Bigint | False |
Group ID to which the ticket has been assigned. |
| IsEscalated | Boolean | False |
If ticket has been escalated for some reason. |
| Name | String | False |
Name of the requester. |
| Phone | String | False |
Phone number of the requester. |
| Priority | Integer | False |
Priority of the ticket. |
| ProductId | Bigint | False |
ID of the product associated with the ticket. |
| ReplyCcEmailsAggregate | String | False |
Email address added while replying. |
| RequesterId | Bigint | False |
ID of the requester of the ticket. |
| ResponderId | Bigint | False |
ID of the agent assigned to the ticket. |
| Source | Integer | False |
Channel throught which ticket was created. |
| Spam | Boolean | False |
If ticket has been marked as spam. |
| Status | Integer | False |
Status of the ticket. |
| Subject | String | False |
Subject of the ticket. |
| TagsAggregate | String | False |
Tags associated with ticket. |
| ToEmailsAggregate | String | True |
Email address to which ticket was sent. |
| Type | String | False |
Category/type of the ticket. |
| UpdatedAt | Datetime | True |
Ticket updated timestamp. |
| AgentRespondedAt | Datetime | True |
Timestamp for when agent last responded to the ticket |
| RequesterRespondedAt | Datetime | True |
Timestamp for when Customer last responded to the ticket |
| FirstRespondedAt | Datetime | True |
Timestamp for when agent first responded to the ticket |
| StatusUpdatedAt | Datetime | True |
Timestamp for when status of the ticket was updated |
| ReopenedAt | Datetime | True |
Timestamp for when the ticket was reopened |
| ResolvedAt | Datetime | True |
Timestamp for when the ticket was resolved |
| ClosedAt | Datetime | True |
Timestamp for when the ticket was closed |
| PendingSince | Datetime | True |
Timestamp since the ticket is pending |
Create, update, delete, and query from TicketUpdatesAutomationRules table
Note: Only users with admin privileges can access the following Table.
Following is an example to select all entries from TicketUpdatesAutomationRules table:
SELECT * FROM TicketUpdatesAutomationRules
The API allows only a subset of columns to be used as filter criteria in the WHERE clause. The filters listed can also be combined using AND OR. The following columns can be used:
Name, Actions, Conditions, Performer, and Events are mandatory to Insert into TicketUpdatesAutomationRules table. For instance:
INSERT INTO TicketUpdatesAutomationRules (Name, Actions, Conditions, Performer, Events) VALUES ('Test', '[{"field_name": "status", "value": 5}]', '[{"name": "condition_set_1", "match_type": "any", "properties": [{"field_name": "to_email", "resource_type": "ticket", "operator": "contains", "value": ["@lyftron.com"]}]}]', '{"type": 1}', '[{"field_name": "reply_sent"}]')
UPDATE TicketUpdatesAutomationRules SET Name = 'Test2' WHERE Id = '2043002030021'
Following is an example of how to delete from the TicketUpdatesAutomationRules table:
DELETE FROM TicketUpdatesAutomationRules WHERE Id = '2043002030021'
| Name | Type | ReadOnly | Description |
| Id [KEY] | Bigint | False |
Unique ID of the TicketUpdatesAutomationRule. |
| Actions | String | False |
Actions of the TicketUpdatesAutomationRule. |
| Active | Boolean | False |
Active of the TicketUpdatesAutomationRule. |
| AffectedTicketsCount | Int | False |
AffectedTicketsCount of the TicketUpdatesAutomationRule. |
| Conditions | String | False |
Conditions of the TicketUpdatesAutomationRule. |
| Events | String | False |
Events of the TicketUpdatesAutomationRule. |
| Name | String | False |
Name of the TicketUpdatesAutomationRule. |
| Outdated | Boolean | True |
Outdated of the TicketUpdatesAutomationRule. |
| Performer | String | False |
Performer of the TicketUpdatesAutomationRule. |
| Position | Int | False |
Position of the TicketUpdatesAutomationRule. |
| Summary | String | True |
Summary of the TicketUpdatesAutomationRule. |
| CreatedAt | Datetime | True |
TicketUpdatesAutomationRule creation timestamp. |
| UpdatedAt | Datetime | True |
TicketUpdatesAutomationRule updated timestamp. |
Create, update, delete, and query from TimeEntries table
Following is an example to select all entries from TimeEntries table:
SELECT * FROM TimeEntries
The API allows only a subset of columns to be used as filter criteria in the WHERE clause. The following columns can be used:
TicketId is mandatory to INSERT into the TimeEntries table. For instance:
INSERT INTO TimeEntries (TicketId, Note, AgentId) VALUES ('255', 'Invoice Information', '122')
Note:
UPDATE TimeEntries SET Billable = 'true' WHERE Id = 786
Note:
Following is an example of how to delete from the TimeEntries table:
DELETE FROM TimeEntries WHERE Id = 786
| Name | Type | ReadOnly | Description |
| Id [KEY] | Bigint | False |
Unique ID of the time entry. |
| AgentId | Bigint | False |
The ID of the agent to whom this time-entry is associated. |
| Billable | Boolean | False |
Set to true if the time entry is billable. |
| ExecutedAt | Datetime | False |
Time at which this time-entry was added/created. |
| Note | String | False |
Description of the time entry. |
| StartTime | Datetime | False |
The time at which the time-entry is added or the time of the last invoked 'start-timer' action using a toggle. |
| TicketId | Bigint | True |
The ID of the ticket to which this time entry is associated. |
| TimeSpent | String | False |
The duration in hh:mm format. |
| TimerRunning | Boolean | False |
True if the timer is currently running. |
| CreatedAt | Datetime | True |
Time Entry created timestamp. |
| UpdatedAt | Datetime | True |
Time Entry updated timestamp. |
Create, update, delete, and query from TimeTriggersAutomationRules table
Note: Only users with admin privileges can access the following Table.
Following is an example to select all entries from TimeTriggersAutomationRules table:
SELECT * FROM TimeTriggersAutomationRules
The API allows only a subset of columns to be used as filter criteria in the WHERE clause. The filters listed can also be combined using AND OR. The following columns can be used:
Name, Actions, and Conditions are mandatory to Insert into TimeTriggersAutomationRules table. For instance:
INSERT INTO TimeTriggersAutomationRules (Name, Actions, Conditions) VALUES ('Test', '[{"field_name": "status", "value": 5}]', '[{"name": "condition_set_1", "match_type": "any", "properties": [{"field_name": "to_email", "resource_type": "ticket", "operator": "contains", "value": ["@lyftron.com"]}]}]')
UPDATE TimeTriggersAutomationRules SET Name = 'Test2' WHERE Id = '2043002030021'
Following is an example of how to delete from the TimeTriggersAutomationRules table:
DELETE FROM TimeTriggersAutomationRules WHERE Id = '2043002030021'
| Name | Type | ReadOnly | Description |
| Id [KEY] | Bigint | False |
Unique ID of the TimeTriggersAutomationRule. |
| Actions | String | False |
Actions of the TimeTriggersAutomationRule. |
| Active | Boolean | False |
Active of the TimeTriggersAutomationRule. |
| AffectedTicketsCount | Int | False |
AffectedTicketsCount of the TimeTriggersAutomationRule. |
| Conditions | String | False |
Conditions of the TimeTriggersAutomationRule. |
| Name | String | False |
Name of the TimeTriggersAutomationRule. |
| Outdated | Boolean | True |
Outdated of the TimeTriggersAutomationRule. |
| Position | Int | False |
Position of the TimeTriggersAutomationRule. |
| Summary | String | True |
Summary of the TimeTriggersAutomationRule. |
| CreatedAt | Datetime | True |
TimeTriggersAutomationRule creation timestamp. |
| UpdatedAt | Datetime | True |
TimeTriggersAutomationRule updated timestamp. |
Views are similar to tables in the way that data is represented; however, views are read-only.
Queries can be executed against a view as if it were a normal table.
| Name | Description |
| CustomObjects | Retrieve the available Custom Objects in FreshDesk. |
| TicketActivities | Query the TicketActivities view. |
| TicketProperties | Query the TicketProperties view. |
Retrieve the available Custom Objects in FreshDesk.
Following is an example to select all entries from the CustomObjects table:
SELECT * FROM CustomObjects
You can also select a specific entry from the CustomObjects table:
SELECT * FROM CustomObjects WHERE Id = 11704
| Name | Type | Description |
| Name | String | Name of the custom object. |
| Id [KEY] | Bigint | Id of the custom object. |
| Fields | String | Fields of the custom object. |
| Description | String | Description of the custom object. |
Query the TicketActivities view.
Following is an example to select all entries from the TicketActivities table:
SELECT * FROM TicketActivities
| Name | Type | Description |
| TicketId | Bigint | Ticket Id of the ticket activity. |
| PerformerId | Bigint | Performer Id of the ticket activity. |
| PerformerType | String | Performer Type of the ticket activity. |
| PerformedAt | Datetime | Performed At of the ticket activity. |
| Status | String | Status of the ticket activity. |
| AgentId | Bigint | Agent Id of the ticket activity. |
| Group | String | Status of the ticket activity. |
| Priority | String | Priority of the ticket activity. |
| RequesterId | Bigint | Requester Id of the ticket activity. |
| TicketType | String | Ticket Type of the ticket activity. |
| Source | String | Source of the ticket activity. |
Query the TicketProperties view.
Following is an example to select all entries from the TicketProperties table:
SELECT * FROM TicketProperties
| Name | Type | Description |
| TicketId | Bigint | Ticket Id of the ticket property. |
| Subject | String | Subject of the ticket property. |
| Status | String | Status of the ticket property. |
| Priority | String | Priority of the ticket property. |
| Source | String | Source of the ticket property. |
| TicketType | String | Ticket type of the ticket property. |
| AssociationType | String | Association type of the ticket property. |
| AgentName | String | Agent name of the ticket property. |
| ResolutionDueBy | Datetime | Resolution Due By of the ticket property. |
| FirstAssignedDate | Datetime | First Assigned Date of the ticket property. |
| CreatedDate | Datetime | Created Date of the ticket property. |
| FirstResponseDueBy | Datetime | First Response Due By of the ticket property. |
| AgentReplyCount | Bigint | Agent Reply Count of the ticket property. |
| CustomerReplyCount | Bigint | Customer Reply Count of the ticket property. |
| LastUpdatedDate | Datetime | Last Updated Date of the ticket property. |
| ResolvedDate | Datetime | Resolved Date of the ticket property. |
| ClosedDate | Datetime | Closed Date of the ticket property. |
| FirstResponseDate | Datetime | First Response Date of the ticket property. |
| ReferenceNumber | String | Reference Number of the ticket property. |
| RequesterName | String | Requester name of the ticket property. |
| RequesterEmail | String | Requester email of the ticket property. |
| RequesterType | String | Requester type of the ticket property. |
| RequesterLanguage | String | Requester language of the ticket property. |
| CompanyName | String | Company name of the ticket property. |
| GroupName | String | Group name of the ticket property. |
| AssignType | String | Assign type of the ticket property. |
| Product | String | Product of the ticket property. |
| FirstAssignedGroup | String | First Assigned Group of the ticket property. |
| LastUpdatedAgent | String | Last Updated Agent of the ticket property. |
| FirstAssignedAgent | String | First Assigned Agent of the ticket property. |
| AgentEmail | String | Agent email of the ticket property. |
| TicketsAge | Bigint | Tickets Age of the ticket property. |
| FirstResponseGroup | String | First Response Group of the ticket property. |
| FirstAssignTimeInCalendarHours | Bigint | First Assign Time In Calendar Hours of the ticket property. |
| FirstResponseTimeInCalendarHours | Bigint | First Response Time In Calendar Hours of the ticket property. |
| FirstResponseTimeInBusinessHours | Bigint | First Response Time In Business Hours of the ticket property. |
| IsSpam | Boolean | Is Spam of the ticket property. |
| ResolutionTimeInCalendarHours | Bigint | Resolution Time In Calendar Hours of the ticket property. |
| ResolutionTimeInBusinessHours | Bigint | Resolution Time In Business Hours of the ticket property. |
| NoOfGroupReassignsTillDate | Bigint | No Of Group Reassigns Till Date of the ticket property. |
| NoOfTimesReopened | Bigint | No Of Times Reopened of the ticket property. |
| IsTrash | Boolean | Is Trash of the ticket property. |
| LastAssignedDate | Datetime | Last Assigned Date of the ticket property. |
| FirstAssignTimeInBusinessHours | Bigint | First Assign Time In Business Hours of the ticket property. |
| NoOfAgentReassignsTillDate | Bigint | No Of Agent Reassigns Till Date of the ticket property. |
| AgentLanguage | String | Agent language of the ticket property. |
| AgentTimezone | String | Agent timezone of the ticket property. |
| InternalGroupName | String | Internal group name of the ticket property. |
| InternalAgentName | String | Internal agent name of the ticket property. |
| StatusSLATimer | Boolean | Status SLA Timer of the ticket property. |
| TicketsResolvedWithinFCR | String | Tickets Resolved Within FCR of the ticket property. |
| TicketsResolvedWithinSLA | String | Tickets Resolved Within SLA of the ticket property. |
| TicketsFirstRespondedWithinSLA | String | Tickets First Responded Within SLA of the ticket property. |
| FirstResponseAgent | String | First Response Agent of the ticket property. |
| TicketsNextRespondedWithinSLA | String | Tickets Next Responded Within SLA of the ticket property. |
| SkillName | String | Skill Name of the ticket property. |
| SurveyResultsEmotion | String | Survey Results Emotion of the ticket property. |
| SurveyResultsSurveyStatus | String | Survey Results Survey Status of the ticket property. |
| SurveyResultsChoices | String | Survey Results Choices of the ticket property. |
| SurveyResultsRespondedDate | Datetime | Survey Results Responded Date of the ticket property. |
| SurveyResultsSurveyName | String | Survey Results Survey Name of the ticket property. |
| SurveyResultsSentVia | String | Survey Results Sent Via of the ticket property. |
| SurveyResultsSurveyCreatedDate | Datetime | Survey Results Survey Created Date of the ticket property. |
| SurveyResultsQuestion | String | Survey Results Question of the ticket property. |
| SurveyResultsAgentName | String | Survey Results Agent Name of the ticket property. |
| SurveyResultsGroupName | String | Survey Results Group Name of the ticket property. |
| SurveyResultsCustomer | String | Survey Results Customer of the ticket property. |
| SurveyResultsDefaultSurvey | String | Survey Results Default Survey of the ticket property. |
| SurveyResultsSurveySentDate | Datetime | Survey Results Survey Sent Date of the ticket property. |
| SurveyUpdatedDate | Datetime | Survey Updated Date of the ticket property. |
| SurveySentDate | Datetime | Survey Sent Date of the ticket property. |
| SurveySurveyStatus | String | Survey Survey Status of the ticket property. |
| SurveySurveyName | String | Survey Survey Name of the ticket property. |
| SurveyDefaultSurvey | String | Survey Default Survey of the ticket property. |
| TicketThemeKeywords | String | Ticket Theme Keywords of the ticket property. |
| TicketThemeName | String | Ticket Theme Name of the ticket property. |
| TagName | String | Tag Name of the ticket property. |
| ContactsType | String | Contacts Type of the ticket property. |
| ContactsEmail | String | Contacts Email of the ticket property. |
| ContactsName | String | Contacts Name of the ticket property. |
| ContactsLanguage | String | Contacts Language of the ticket property. |
| ContactsTimeZone | String | Contacts Time Zone of the ticket property. |
| ContactsMobile | String | Contacts Mobile of the ticket property. |
| ContactsMobileNumber | String | Contacts Mobile Number of the ticket property. |
| CompanyIndustry | String | Company Industry of the ticket property. |
| CompanyRenewalDate | Datetime | Company Renewal Date of the ticket property. |
| CompanyAccountTier | String | Company Account Tier of the ticket property. |
| CompanyHealthScore | String | Company Health Score of the ticket property. |
| CannedResponseUsedAt | Datetime | Canned Response Used At of the ticket property. |
| CannedResponseTicketID | String | Canned Response Ticket ID of the ticket property. |
| CannedResponseCannedResponseTitle | String | Canned Response Canned Response Title of the ticket property. |
| CannedResponseNoteType | String | Canned Response Note Type of the ticket property. |
| CannedResponseAgent | String | Canned Response Agent of the ticket property. |
| CannedResponseAgentType | String | Canned Response Agent Type of the ticket property. |
| CannedResponseCannedResponseVisibility | String | Canned Response Canned Response Visibility of the ticket property. |
| CannedResponseCannedResponseCreatedAt | Datetime | Canned Response Canned Response Created At of the ticket property. |
| CannedResponseAgentGroup | String | Canned Response Agent Group of the ticket property. |
| CannedResponseFolder | String | Canned Response Folder of the ticket property. |
| CannedResponseCannedResponseUpdatedAt | Datetime | Canned Response Canned Response Updated At of the ticket property. |
| CannedResponseCannedResponseAuthor | String | Canned Response Canned Response Author of the ticket property. |
The connection string properties are the various options that can be used to establish a connection. This section provides a complete list of the options you can configure in the connection string for this provider. Click the links for further details.
For more information on establishing a connection, see Establishing a Connection.
| Property | Description |
| Domain | Domain is used for accessing your Freshdesk account. |
| APIKey | The API key used for accessing your Freshdesk account. |
| Property | Description |
| SSLServerCert | Specifies the certificate to be accepted from the server when connecting using TLS/SSL. |
| Property | Description |
| FirewallType | Specifies the protocol the provider uses to tunnel traffic through a proxy-based firewall. |
| FirewallServer | Identifies the IP address, DNS name, or host name of a proxy used to traverse a firewall and relay user queries to network resources. |
| FirewallPort | Specifies the TCP port to be used for a proxy-based firewall. |
| FirewallUser | Identifies the user ID of the account authenticating to a proxy-based firewall. |
| FirewallPassword | Specifies the password of the user account authenticating to a proxy-based firewall. |
| Property | Description |
| ProxyAutoDetect | Specifies whether the provider checks your system proxy settings for existing proxy server configurations, rather than using a manually specified proxy server. |
| ProxyServer | The hostname or IP address of the proxy server that you want to route HTTP traffic through. |
| ProxyPort | The TCP port on your specified proxy server (set in the ProxyServer connection property) that has been reserved for routing HTTP traffic to and from the client. |
| ProxyAuthScheme | Specifies the authentication method the provider uses when authenticating to the proxy server specified in the ProxyServer connection property. |
| ProxyUser | The username of a user account registered with the proxy server specified in the ProxyServer connection property. |
| ProxyPassword | The password associated with the user specified in the ProxyUser connection property. |
| ProxySSLType | The SSL type to use when connecting to the proxy server specified in the ProxyServer connection property. |
| ProxyExceptions | A semicolon separated list of destination hostnames or IPs that are exempt from connecting through the proxy server set in the ProxyServer connection property. |
| Property | Description |
| LogModules | Specifies the core modules to include in the log file. Use a semicolon-separated list of module names. By default, all modules are logged. |
| Property | Description |
| Location | Specifies the location of a directory containing schema files that define tables, views, and stored procedures. Depending on your service's requirements, this may be expressed as either an absolute path or a relative path. |
| BrowsableSchemas | Optional setting that restricts the schemas reported to a subset of all available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC . |
| Tables | Optional setting that restricts the tables reported to a subset of all available tables. For example, Tables=TableA,TableB,TableC . |
| Views | Optional setting that restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC . |
| Property | Description |
| FetchTicketsUpdatedSince | Use FetchTicketsUpdatedSince to query tickets older than 30 days. Note: TicketStats must be set to True. |
| IgnoreSurplusResults | Use IgnoreSurplusResults to ignore results beyond 300 which have same CreatedAt value. |
| IncludeCustomObjects | Whether to include custom objects or not. |
| MaxRows | Specifies the maximum rows returned for queries without aggregation or GROUP BY. |
| Other | Specifies additional hidden properties for specific use cases. These are not required for typical provider functionality. Use a semicolon-separated list to define multiple properties. |
| PseudoColumns | Specifies the pseudocolumns to expose as table columns. Use the format 'TableName=ColumnName;TableName=ColumnName'. The default is an empty string, which disables this property. |
| RowScanDepth | Set this property to control the number of rows scanned when TypeDetectionScheme is set to RowScan. |
| TicketPropertiesURL | Use TicketPropertiesURL to query ticket properties. |
| TicketsOrderByField | Determines which ticket field to order by. |
| TicketsOrderByType | Determines which ticket field to order by. |
| TicketStats | Use TicketsStats to retrieve stats attributes of a ticket, which are not normally available. |
| Timeout | Specifies the maximum time, in seconds, that the provider waits for a server response before throwing a timeout error. The default is 60 seconds. Set to 0 to disable the timeout. |
| TypeDetectionScheme | Determines how to determine the data type of columns. |
| UserDefinedViews | Specifies a filepath to a JSON configuration file defining custom views. The provider automatically detects and uses the views specified in this file. |
Domain is used for accessing your Freshdesk account.
Domain is used for accessing your Freshdesk account. For example, in your URL: https://{domainValue}.freshdesk.com, thus connection string should be:
Domain=domainValue
The API key used for accessing your Freshdesk account.
The API key used for accessing your Freshdesk account. The API key can be found in Freshdesk by going to Profile Settings -> API Key.
This section provides a complete list of the SSL properties you can configure in the connection string for this provider.
| Property | Description |
| SSLServerCert | Specifies the certificate to be accepted from the server when connecting using TLS/SSL. |
Specifies the certificate to be accepted from the server when connecting using TLS/SSL.
If using a TLS/SSL connection, this property can be used to specify the TLS/SSL certificate to be accepted from the server. Any other certificate that is not trusted by the machine is rejected.
This property can take the following forms:
| Description | Example |
| A full PEM Certificate (example shortened for brevity) | -----BEGIN CERTIFICATE----- MIIChTCCAe4CAQAwDQYJKoZIhv......Qw== -----END CERTIFICATE----- |
| A path to a local file containing the certificate | C:\cert.cer |
| The public key (example shortened for brevity) | -----BEGIN RSA PUBLIC KEY----- MIGfMA0GCSq......AQAB -----END RSA PUBLIC KEY----- |
| The MD5 Thumbprint (hex values can also be either space or colon separated) | ecadbdda5a1529c58a1e9e09828d70e4 |
| The SHA1 Thumbprint (hex values can also be either space or colon separated) | 34a929226ae0819f2ec14b4a3d904f801cbb150d |
If not specified, any certificate trusted by the machine is accepted.
Use '*' to signify to accept all certificates. Note that this is not recommended due to security concerns.
This section provides a complete list of the Firewall properties you can configure in the connection string for this provider.
| Property | Description |
| FirewallType | Specifies the protocol the provider uses to tunnel traffic through a proxy-based firewall. |
| FirewallServer | Identifies the IP address, DNS name, or host name of a proxy used to traverse a firewall and relay user queries to network resources. |
| FirewallPort | Specifies the TCP port to be used for a proxy-based firewall. |
| FirewallUser | Identifies the user ID of the account authenticating to a proxy-based firewall. |
| FirewallPassword | Specifies the password of the user account authenticating to a proxy-based firewall. |
Specifies the protocol the provider uses to tunnel traffic through a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Note: By default, the Sync App connects to the system proxy. To disable this behavior and connect to one of the following proxy types, set ProxyAutoDetect to false.
The following table provides port number information for each of the supported protocols.
| Protocol | Default Port | Description |
| TUNNEL | 80 | The port where the Sync App opens a connection to Freshdesk. Traffic flows back and forth via the proxy at this location. |
| SOCKS4 | 1080 | The port where the Sync App opens a connection to Freshdesk. SOCKS 4 then passes theFirewallUser value to the proxy, which determines whether the connection request should be granted. |
| SOCKS5 | 1080 | The port where the Sync App sends data to Freshdesk. If the SOCKS 5 proxy requires authentication, set FirewallUser and FirewallPassword to credentials the proxy recognizes. |
To connect to HTTP proxies, use ProxyServer and ProxyPort. To authenticate to HTTP proxies, use ProxyAuthScheme, ProxyUser, and ProxyPassword.
Identifies the IP address, DNS name, or host name of a proxy used to traverse a firewall and relay user queries to network resources.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Specifies the TCP port to be used for a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Identifies the user ID of the account authenticating to a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Specifies the password of the user account authenticating to a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
This section provides a complete list of the Proxy properties you can configure in the connection string for this provider.
| Property | Description |
| ProxyAutoDetect | Specifies whether the provider checks your system proxy settings for existing proxy server configurations, rather than using a manually specified proxy server. |
| ProxyServer | The hostname or IP address of the proxy server that you want to route HTTP traffic through. |
| ProxyPort | The TCP port on your specified proxy server (set in the ProxyServer connection property) that has been reserved for routing HTTP traffic to and from the client. |
| ProxyAuthScheme | Specifies the authentication method the provider uses when authenticating to the proxy server specified in the ProxyServer connection property. |
| ProxyUser | The username of a user account registered with the proxy server specified in the ProxyServer connection property. |
| ProxyPassword | The password associated with the user specified in the ProxyUser connection property. |
| ProxySSLType | The SSL type to use when connecting to the proxy server specified in the ProxyServer connection property. |
| ProxyExceptions | A semicolon separated list of destination hostnames or IPs that are exempt from connecting through the proxy server set in the ProxyServer connection property. |
Specifies whether the provider checks your system proxy settings for existing proxy server configurations, rather than using a manually specified proxy server.
When this connection property is set to True, the Sync App checks your system proxy settings for existing proxy server configurations (no need to manually supply proxy server details).
This connection property takes precedence over other proxy settings. Set to False if you want to manually configure the Sync App to connect to a specific proxy server.
To connect to an HTTP proxy, see ProxyServer. For other proxies, such as SOCKS or tunneling, see FirewallType.
The hostname or IP address of the proxy server that you want to route HTTP traffic through.
The Sync App only routes HTTP traffic through the proxy server specified in this connection property when ProxyAutoDetect is set to False. If ProxyAutoDetect is set to True, which is the default, the Sync App instead routes HTTP traffic through the proxy server specified in your system proxy settings.
The TCP port on your specified proxy server (set in the ProxyServer connection property) that has been reserved for routing HTTP traffic to and from the client.
The Sync App only routes HTTP traffic through the proxy server port specified in this connection property when ProxyAutoDetect is set to False. If ProxyAutoDetect is set to True, which is the default, the Sync App instead routes HTTP traffic through the proxy server port specified in your system proxy settings.
For other proxy types, see FirewallType.
Specifies the authentication method the provider uses when authenticating to the proxy server specified in the ProxyServer connection property.
The authentication type can be one of the following:
For all values other than "NONE", you must also set the ProxyUser and ProxyPassword connection properties.
If you need to use another authentication type, such as SOCKS 5 authentication, see FirewallType.
The username of a user account registered with the proxy server specified in the ProxyServer connection property.
The ProxyUser and ProxyPassword connection properties are used to connect and authenticate against the HTTP proxy specified in ProxyServer.
After selecting one of the available authentication types in ProxyAuthScheme, set this property as follows:
| ProxyAuthScheme Value | Value to set for ProxyUser |
| BASIC | The user name of a user registered with the proxy server. |
| DIGEST | The user name of a user registered with the proxy server. |
| NEGOTIATE | The username of a Windows user who is a valid user in the domain or trusted domain that the proxy server is part of, in the format user@domain or domain\user. |
| NTLM | The username of a Windows user who is a valid user in the domain or trusted domain that the proxy server is part of, in the format user@domain or domain\user. |
| NONE | Do not set the ProxyPassword connection property. |
The Sync App only uses this username if ProxyAutoDetect is set to False. If ProxyAutoDetect is set to True, which is the default, the Sync App instead uses the username specified in your system proxy settings.
The password associated with the user specified in the ProxyUser connection property.
The ProxyUser and ProxyPassword connection properties are used to connect and authenticate against the HTTP proxy specified in ProxyServer.
After selecting one of the available authentication types in ProxyAuthScheme, set this property as follows:
| ProxyAuthScheme Value | Value to set for ProxyPassword |
| BASIC | The password associated with the proxy server user specified in ProxyUser. |
| DIGEST | The password associated with the proxy server user specified in ProxyUser. |
| NEGOTIATE | The password associated with the Windows user account specified in ProxyUser. |
| NTLM | The password associated with the Windows user account specified in ProxyUser. |
| NONE | Do not set the ProxyPassword connection property. |
For SOCKS 5 authentication or tunneling, see FirewallType.
The Sync App only uses this password if ProxyAutoDetect is set to False. If ProxyAutoDetect is set to True, which is the default, the Sync App instead uses the password specified in your system proxy settings.
The SSL type to use when connecting to the proxy server specified in the ProxyServer connection property.
This property determines when to use SSL for the connection to the HTTP proxy specified by ProxyServer. You can set this connection property to the following values :
| AUTO | Default setting. If ProxyServer is set to an HTTPS URL, the Sync App uses the TUNNEL option. If ProxyServer is set to an HTTP URL, the component uses the NEVER option. |
| ALWAYS | The connection is always SSL enabled. |
| NEVER | The connection is not SSL enabled. |
| TUNNEL | The connection is made through a tunneling proxy. The proxy server opens a connection to the remote host and traffic flows back and forth through the proxy. |
A semicolon separated list of destination hostnames or IPs that are exempt from connecting through the proxy server set in the ProxyServer connection property.
The ProxyServer is used for all addresses, except for addresses defined in this property. Use semicolons to separate entries.
Note that the Sync App uses the system proxy settings by default, without further configuration needed. If you want to explicitly configure proxy exceptions for this connection, set ProxyAutoDetect to False.
This section provides a complete list of the Logging properties you can configure in the connection string for this provider.
| Property | Description |
| LogModules | Specifies the core modules to include in the log file. Use a semicolon-separated list of module names. By default, all modules are logged. |
Specifies the core modules to include in the log file. Use a semicolon-separated list of module names. By default, all modules are logged.
This property lets you customize the log file content by specifying the logging modules to include. Logging modules categorize logged information into distinct areas, such as query execution, metadata, or SSL communication. Each module is represented by a four-character code, with some requiring a trailing space for three-letter names.
For example, EXEC logs query execution, and INFO logs general provider messages. To include multiple modules, separate their names with semicolons as follows: INFO;EXEC;SSL.
The Verbosity connection property takes precedence over the module-based filtering specified by this property. Only log entries that meet the verbosity level and belong to the specified modules are logged. Leave this property blank to include all available modules in the log file.
For a complete list of available modules and detailed guidance on configuring logging, refer to the Advanced Logging section in Logging.
This section provides a complete list of the Schema properties you can configure in the connection string for this provider.
| Property | Description |
| Location | Specifies the location of a directory containing schema files that define tables, views, and stored procedures. Depending on your service's requirements, this may be expressed as either an absolute path or a relative path. |
| BrowsableSchemas | Optional setting that restricts the schemas reported to a subset of all available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC . |
| Tables | Optional setting that restricts the tables reported to a subset of all available tables. For example, Tables=TableA,TableB,TableC . |
| Views | Optional setting that restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC . |
Specifies the location of a directory containing schema files that define tables, views, and stored procedures. Depending on your service's requirements, this may be expressed as either an absolute path or a relative path.
The Location property is only needed if you want to either customize definitions (for example, change a column name, ignore a column, etc.) or extend the data model with new tables, views, or stored procedures.
If left unspecified, the default location is %APPDATA%\\CData\\FreshDesk Data Provider\\Schema, where %APPDATA% is set to the user's configuration directory:
| Platform | %APPDATA% |
| Windows | The value of the APPDATA environment variable |
| Linux | ~/.config |
Optional setting that restricts the schemas reported to a subset of all available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC .
Listing all available database schemas can take extra time, thus degrading performance. Providing a list of schemas in the connection string saves time and improves performance.
Optional setting that restricts the tables reported to a subset of all available tables. For example, Tables=TableA,TableB,TableC .
Listing all available tables from some databases can take extra time, thus degrading performance. Providing a list of tables in the connection string saves time and improves performance.
If there are lots of tables available and you already know which ones you want to work with, you can use this property to restrict your viewing to only those tables. To do this, specify the tables you want in a comma-separated list. Each table should be a valid SQL identifier with any special characters escaped using square brackets, double-quotes or backticks. For example, Tables=TableA,[TableB/WithSlash],WithCatalog.WithSchema.`TableC With Space`.
Note: If you are connecting to a data source with multiple schemas or catalogs, you must specify each table you want to view by its fully qualified name. This avoids ambiguity between tables that may exist in multiple catalogs or schemas.
Optional setting that restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC .
Listing all available views from some databases can take extra time, thus degrading performance. Providing a list of views in the connection string saves time and improves performance.
If there are lots of views available and you already know which ones you want to work with, you can use this property to restrict your viewing to only those views. To do this, specify the views you want in a comma-separated list. Each view should be a valid SQL identifier with any special characters escaped using square brackets, double-quotes or backticks. For example, Views=ViewA,[ViewB/WithSlash],WithCatalog.WithSchema.`ViewC With Space`.
Note: If you are connecting to a data source with multiple schemas or catalogs, you must specify each view you want to examine by its fully qualified name. This avoids ambiguity between views that may exist in multiple catalogs or schemas.
This section provides a complete list of the Miscellaneous properties you can configure in the connection string for this provider.
| Property | Description |
| FetchTicketsUpdatedSince | Use FetchTicketsUpdatedSince to query tickets older than 30 days. Note: TicketStats must be set to True. |
| IgnoreSurplusResults | Use IgnoreSurplusResults to ignore results beyond 300 which have same CreatedAt value. |
| IncludeCustomObjects | Whether to include custom objects or not. |
| MaxRows | Specifies the maximum rows returned for queries without aggregation or GROUP BY. |
| Other | Specifies additional hidden properties for specific use cases. These are not required for typical provider functionality. Use a semicolon-separated list to define multiple properties. |
| PseudoColumns | Specifies the pseudocolumns to expose as table columns. Use the format 'TableName=ColumnName;TableName=ColumnName'. The default is an empty string, which disables this property. |
| RowScanDepth | Set this property to control the number of rows scanned when TypeDetectionScheme is set to RowScan. |
| TicketPropertiesURL | Use TicketPropertiesURL to query ticket properties. |
| TicketsOrderByField | Determines which ticket field to order by. |
| TicketsOrderByType | Determines which ticket field to order by. |
| TicketStats | Use TicketsStats to retrieve stats attributes of a ticket, which are not normally available. |
| Timeout | Specifies the maximum time, in seconds, that the provider waits for a server response before throwing a timeout error. The default is 60 seconds. Set to 0 to disable the timeout. |
| TypeDetectionScheme | Determines how to determine the data type of columns. |
| UserDefinedViews | Specifies a filepath to a JSON configuration file defining custom views. The provider automatically detects and uses the views specified in this file. |
Use FetchTicketsUpdatedSince to query tickets older than 30 days. Note: TicketStats must be set to True.
When TicketStats = true, all requests (including filtering request) would be sent to the 'List all' endpoint. The 'List all' endpoint only retrieves the tickets created in the last 30 days, unless FetchTicketsUpdatedSince is set to a specifed date. Set FetchTicketsUpdatedSince to a specified date to retrieve tickets created past the last 30 days. (Example: FetchTicketsUpdatedSince=2022-01-01 or FetchTicketsUpdatedSince=2022-01-01T00:00:00Z)
Use IgnoreSurplusResults to ignore results beyond 300 which have same CreatedAt value.
By default, FreshDesk API only returns upto 300 results matching a specific filter. Paging mechanism of the driver uses CreatedAt attribute as a filter, thus more than 300 results with same CreateAt value will cause paging to fail. IgnoreSurplusResults will cause these surplus results to be ignored without causing an exception and keep retrieving results.
Whether to include custom objects or not.
If set to TRUE, the custom objects are retrieved. Note: You must have the Custom Objects feature enabled to use this property.
Specifies the maximum rows returned for queries without aggregation or GROUP BY.
This property sets an upper limit on the number of rows the Sync App returns for queries that do not include aggregation or GROUP BY clauses. This limit ensures that queries do not return excessively large result sets by default.
When a query includes a LIMIT clause, the value specified in the query takes precedence over the MaxRows setting. If MaxRows is set to "-1", no row limit is enforced unless a LIMIT clause is explicitly included in the query.
This property is useful for optimizing performance and preventing excessive resource consumption when executing queries that could otherwise return very large datasets.
Specifies additional hidden properties for specific use cases. These are not required for typical provider functionality. Use a semicolon-separated list to define multiple properties.
This property allows advanced users to configure hidden properties for specialized scenarios. These settings are not required for normal use cases but can address unique requirements or provide additional functionality. Multiple properties can be defined in a semicolon-separated list.
Note: It is strongly recommended to set these properties only when advised by the support team to address specific scenarios or issues.
Specify multiple properties in a semicolon-separated list.
| DefaultColumnSize | Sets the default length of string fields when the data source does not provide column length in the metadata. The default value is 2000. |
| ConvertDateTimeToGMT | Determines whether to convert date-time values to GMT, instead of the local time of the machine. |
| RecordToFile=filename | Records the underlying socket data transfer to the specified file. |
Specifies the pseudocolumns to expose as table columns. Use the format 'TableName=ColumnName;TableName=ColumnName'. The default is an empty string, which disables this property.
This property allows you to define which pseudocolumns the Sync App exposes as table columns.
To specify individual pseudocolumns, use the following format: "Table1=Column1;Table1=Column2;Table2=Column3"
To include all pseudocolumns for all tables use: "*=*"
Set this property to control the number of rows scanned when TypeDetectionScheme is set to RowScan.
Determines the number of rows used to determine the column data types.
Setting a high value may decrease performance. Setting a low value may prevent the data type from being determined properly, especially when there is null data.
Use TicketPropertiesURL to query ticket properties.
Set TicketPropertiesURL to the API URL that is found on the Schedule page of the created Scheduled Export. To find this, go to Reports/Schedule an export/Click on the name of the Schedule and the URL is under the Receive via API section.
Determines which ticket field to order by.
| CreatedAt | Setting to CreatedAt will add CreatedAt as an order by field to the request. |
| UpdatedAt | Setting to UpdatedAt will add UpdatedAt as an order by field to the request. |
Determines which ticket field to order by.
| DESC | Setting to DESC will add desc as the order by type to the request. |
| ASC | Setting to ASC will add asc as the order by type to the request. |
Use TicketsStats to retrieve stats attributes of a ticket, which are not normally available.
When TicketStats = true, all requests (including filtering request) would be sent to the 'List all' endpoint. This would slightly affect the performance by handling filtering client-side, but would retrieve stats attributes of each ticket. 'List all' endpoint only retrieves the tickets created in the last 30 days.
Specifies the maximum time, in seconds, that the provider waits for a server response before throwing a timeout error. The default is 60 seconds. Set to 0 to disable the timeout.
This property controls the maximum time, in seconds, that the Sync App waits for an operation to complete before canceling it. If the timeout period expires before the operation finishes, the Sync App cancels the operation and throws an exception.
The timeout applies to each individual communication with the server rather than the entire query or operation. For example, a query could continue running beyond 60 seconds if each paging call completes within the timeout limit.
Setting this property to 0 disables the timeout, allowing operations to run indefinitely until they succeed or fail due to other conditions such as server-side timeouts, network interruptions, or resource limits on the server. Use this property cautiously to avoid long-running operations that could degrade performance or result in unresponsive behavior.
Determines how to determine the data type of columns.
| None | Setting TypeDetectionScheme to None will return all columns as the string type. |
| RowScan | Setting TypeDetectionScheme to RowScan will scan rows to heuristically determine the data type. The RowScanDepth determines the number of rows to be scanned. |
Specifies a filepath to a JSON configuration file defining custom views. The provider automatically detects and uses the views specified in this file.
This property allows you to define and manage custom views through a JSON-formatted configuration file called UserDefinedViews.json. These views are automatically recognized by the Sync App and enable you to execute custom SQL queries as if they were standard database views. The JSON file defines each view as a root element with a child element called "query", which contains the SQL query for the view. For example:
{
"MyView": {
"query": "SELECT * FROM Tickets WHERE MyColumn = 'value'"
},
"MyView2": {
"query": "SELECT * FROM MyTable WHERE Id IN (1,2,3)"
}
}
You can define multiple views in a single file and specify the filepath using this property. For example: UserDefinedViews=C:\Path\To\UserDefinedViews.json. When you use this property, only the specified views are seen by the Sync App.
Refer to User Defined Views for more information.