In this document, you will find detailed info about Freshservice Endpoint Type. This Endpoint Type is a self-service type, so users can add them without a need to reach out to ONEiO Support.
|Status||Sets the status of the endpoint. Active / Suspended|
|Freshservice root URL||The base address of your Freshservice. You can test the HTTP connection by clicking the Test Connection button. Note that this function does not test the authentication, only if ONEiO can reach the endpoint.|
|Name||Name of the endpoint. It is recommended to use short names since this name is used in displays throughout ONEiO.|
|Timezone||The timezone used in Freshservice.|
Date time pattern ONEiO uses to read DateTime fields and how ONEiO sends out DateTime fields. Shown only for reference.
|[YourFreshservice] -> ONEiO|
|Receiver address||The address to insert to Freshservice's HTTP target Url. The targets are different when operating in QA or Production.|
|Username||Username (and password) to be used in Freshservice's webhook's Callback Url. You can reset/retrieve a password in edit mode.|
|ONEiO -> [YourFreshservice]|
|API Token||The API Token of the integration user.|
|Unrecoverable HTTP error codes||List of numeric HTTP response codes that are to be handled as non-recoverable when sending messages to Freshservice's API. If ONEiO receives an error code that is not on the list, it will retry the message automatically. If ONEiO receives an error code that IS on this list, the message will result in an error.|
To integrate with Freshservice, you can use only fixed Entity types. This is due to the fact that the entities available are depended on available APIs in Freshservice. Currently supported entity types: