What’s supported
Supported actions
This connector supports:- Read Actions, including full historic backfill. Please note that incremental read is supported only for
companies
,tickets
andcontacts
currently. For all other objects, a full read of the Freshdesk instance will be done per scheduled read. - Write Actions.
- Proxy Actions, using the base URL
https://{{.workspace}}.freshdesk.com
.
Supported Objects
The Freshdesk connector supports reading from the following objects:- agents
- business_hours
- canned_response_folders
- companies
- company-fields
- contacts
- contact-fields
- email_configs
- groups
- mailboxes
- products
- roles
- scenario_automations
- sla_policies
- skills
- tickets
- ticket-fields
- ticket-forms
- time_entries
- agents
- canned_responses
- canned_response_folders
- companies
- company-fields
- contacts
- contact-fields
- contact-activities
- groups
- mailboxes
- skills
- sla_policies
- thread
- tickets
- ticket-fields
- ticket-forms
Example integration
To define an integration for Freshdesk, create a manifest file that looks like this:Using the connector
This connector uses Basic Auth, which means that you do not need to set up a Provider App before getting started. (Provider apps are only required for providers that use OAuth2 Authorization Code grant type.) To start integrating with Freshdesk:- Create a manifest file like the example above.
- Deploy it using the amp CLI.
- Embed the InstallIntegration UI component. The UI component will prompt the customer for their username, password and domain.
- Start making Proxy Calls, and Ampersand will automatically attach the correct header required by Basic Auth. Please note that this connector’s base URL is
https://{{.workspace}}.freshdesk.com
.