Overview
Client-mode REST API connector for Freshdesk tickets and Freshservice assets.BASE_ADDRESS defaults to https://YOUR_DOMAIN.freshdesk.com. Auth: Basic (API key as username, password X) or Bearer. Pass secrets only at runtime via MQTT JSON placeholders or Hub GET SECRET — never commit real credentials.
Auth
Basic (API key as username, password X) or Bearer. Prefer Hub secrets /GET SECRET. Never hard-code tokens into the .lot.
Basic Syntax
MQTT topics
Request topics underintegrations/freshdesk-and-freshservice/request/...; responses on integrations/freshdesk-and-freshservice/response/....
Template reference
Generated from the shipped broker templatefreshdesk-and-freshservice (-routeCode FRESHDESK_AND_FRESHSERVICE). It lists every event the template defines.
Auth
Basic (API key as username, password X) or Bearer Auth headers used by the template:Authorization: Bearer {value.json.api_key}.
Template parameters
BASE_ADDRESS default: https://YOUR_DOMAIN.freshdesk.com.
Events
Deploy
Get the template card (JSON withtemplate and metadata) from the broker, then deploy the connector:
BASE_ADDRESS already filled in:
-addRoute (do not include ADD METADATA).
Usage example
CallListtickets by publishing a JSON payload to its request topic, and read the reply on the response topic:

