Skip to content
← Back to documentation
Technical Reference

Freshdesk

Customer support software

CategoryCustomer Support
Authenticationcustom
Version0.3.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Freshdesk with Flows360

Customer support software

Use the Freshdesk connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and no declared triggers.

Available actions

  • Get Tickets
  • Get Contact from ID
  • Get Ticket Status
  • Get Freshdesk Contacts
  • Get All Tickets By Status
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Freshdesk
  • Package: @activepieces/piece-freshdesk@0.3.0
  • Exact artifact digest: sha256:27b94c6a8065caed2d4f640885ca903aadd98f038d48ba043ef27d64e02e77db
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Get Tickets (get_tickets), Get Ticket instances from Freshdesk. Classification: read.
  • Get Contact from ID (get_contact_from_id), Get contacts details from Freshdesk using ID number. Classification: read.
  • Get Ticket Status (get_ticket_status), Get Ticket status from Freshdesk. Returns ticket_status, assigned_status, assigned_id Classification: read.
  • Get Freshdesk Contacts (get_contacts), Get contact details from Freshdesk for all (optional filtered) contacts. Classification: read.
  • Get All Tickets By Status (get_all_tickets_by_status), Get All Tickets by selected status from Freshdesk. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects6
Supported actions6
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Base URL Required
  • API Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Get Tickets Yes No Get Ticket instances from Freshdesk.
Get Contact from ID Yes No Get contacts details from Freshdesk using ID number.
Get Ticket Status Yes No Get Ticket status from Freshdesk. Returns ticket_status, assigned_status, assigned_id
Get Freshdesk Contacts Yes No Get contact details from Freshdesk for all (optional filtered) contacts.
Get All Tickets By Status Yes No Get All Tickets by selected status from Freshdesk.
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Get Tickets · Read

Get Ticket instances from Freshdesk.

get_tickets · Risk: low · Retry: safe

Get Contact from ID · Read

Get contacts details from Freshdesk using ID number.

get_contact_from_id · Risk: low · Retry: safe

Inputs

  • contactid · string · Required, The ID number of the contact
Get Ticket Status · Read

Get Ticket status from Freshdesk. Returns ticket_status, assigned_status, assigned_id

get_ticket_status · Risk: low · Retry: safe

Inputs

  • ticketid · string · Required, The Ticket ID to return status
Get Freshdesk Contacts · Read

Get contact details from Freshdesk for all (optional filtered) contacts.

get_contacts · Risk: low · Retry: safe

Inputs

  • filter_type · string · Optional, Select one and provide the value.
  • filter_value · string · Optional, Provide value if previous option selected!
  • filter_status · string · Optional, Can filter by state: blocked, deleted, unverified or verified.
  • per_page · number · Required, Freshdesk calls this per_page - set to 0 for all, if specified maximum is 100
Get All Tickets By Status · Read

Get All Tickets by selected status from Freshdesk.

get_all_tickets_by_status · Risk: low · Retry: safe

Inputs

  • status_filter · array · Required, Select one or status values
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Setup

Setup

  1. Add the Freshdesk connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Base URL (base_url), required.
  • API Token (access_token), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-freshdesk@0.3.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Freshdesk connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-freshdesk@0.3.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.