Freshdesk integration

Customer Support · 45 actions · API key auth

Customer support helpdesk platform for managing tickets, contacts, agents, and knowledge base articles via the Freshdesk REST API.

Put Freshdesk to work View Freshdesk integration docs

Overview

The ModuleX Freshdesk integration lets a ModuleX agent operate Freshdesk on your behalf — running create, update and remove actions across tickets, all tickets and note to tickets — directly from a plain-English request, using your organization's own Freshdesk credentials. No pre-built workflow is required: the agent picks the right Freshdesk action for the task.

Freshdesk is a customer support platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Freshdesk action — or, when you want a repeatable process, the composer assembles a Freshdesk workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive Freshdesk in plain English

Type what you want. A ModuleX agent picks the right Freshdesk action — or chains several — and runs it. No workflow to build.

Create a new support ticket in Freshdesk
resolves tocreate_ticket
Find the ticket I describe and update it
resolves toget_ticketupdate_ticket
Close a ticket by setting its status to Closed (5)
resolves toclose_ticket
Show me the all tickets that match what I describe
resolves tolist_all_tickets

Use cases

What you can automate with Freshdesk

Find the right ticket and update it in one promptget_ticketupdate_ticket
Pull a list of all tickets for a reportlist_all_tickets
Add a note to ticket on the flyadd_note_to_ticket
Remove a ticket tag you no longer needremove_ticket_tags
Set a ticket priority without opening the dashboardset_ticket_priority
Assign a ticket to agent to the right ownerassign_ticket_to_agent

At a glance

Freshdesk integration at a glance

VendorFreshdesk

CategoryCustomer Support

Actions available45

AuthenticationAPI key

Uses your own credentialsYes

Works with the assistantYes

Works in the composerYes

Multi-step / tool-chainingYes

Technical referenceView docs

Integration version1.0.0

Last updatedJun 2026

Reference

All 45 Freshdesk actions

Tickets5

create_ticket

Create a new support ticket in Freshdesk

get_ticket

Retrieve a specific ticket by its ID

update_ticket

Update an existing ticket's properties

close_ticket

Close a ticket by setting its status to Closed (5)

forward_ticket

Forward a ticket to an external email address

All Tickets1

list_all_tickets

List tickets in Freshdesk with optional filtering

Note to Tickets1

add_note_to_ticket

Add a private or public note to a ticket

Ticket Tags3

add_ticket_tags

Add tags to an existing ticket

remove_ticket_tags

Remove tags from an existing ticket

set_ticket_tags

Replace all tags on a ticket with the specified set

Ticket Priorities1

set_ticket_priority

Set the priority of a ticket

Ticket Status1

set_ticket_status

Set the status of a ticket

Ticket to Agents1

assign_ticket_to_agent

Assign a ticket to a specific agent

Ticket to Groups1

assign_ticket_to_group

Assign a ticket to a specific group

Contacts3

create_contact

Create a new contact in Freshdesk

get_contact

Retrieve a contact by their ID

update_contact

Update an existing contact's properties

Companies2

create_company

Create a new company in Freshdesk

list_companies

List all companies in Freshdesk

Agents4

create_agent

Create a new agent in Freshdesk

update_agent

Update an existing agent's properties

get_agent

Retrieve a single agent by their ID

list_agents

List all agents in Freshdesk with optional filtering

Replies1

create_reply

Create a reply to a ticket

To Forwards1

reply_to_forward

Reply to a previously forwarded ticket email

Threads1

create_thread

Create a collaboration thread on a ticket

Message for Threads1

create_message_for_thread

Create a message in a collaboration thread

Ticket Conversations1

list_ticket_conversations

List all conversations (notes, replies) for a ticket

Ticket Fields3

list_ticket_fields

List all ticket fields configured in Freshdesk

create_ticket_field

Create a new custom ticket field

update_ticket_field

Update a custom ticket field

Solution Articles5

create_solution_article

Create a knowledge base article in a folder

get_solution_article

Retrieve a knowledge base article by its ID

update_solution_article

Update a knowledge base article

delete_solution_article

Delete a knowledge base article

search_solution_article

Search knowledge base articles by keyword

Solution Categories1

list_solution_categories

List all knowledge base solution categories

Category Folders1

list_category_folders

List all folders within a solution category

Folder Articles1

list_folder_articles

List all articles within a solution folder

All Folders1

list_all_folders

List all canned response folders

Folder Canned Responses2

list_folder_canned_responses

List all canned responses in a specific folder

get_folder_canned_responses

Get detailed canned responses from a folder

Canned Responses1

get_canned_response

Retrieve a specific canned response by ID

Email Configs1

list_email_configs

List all email configurations

Roles1

list_roles

List all agent roles

See full parameters and response schemas in the Freshdesk integration docs

Two ways

Two ways to use Freshdesk in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right Freshdesk action and runs it — no workflow to build.

Compose a workflowNeed it to happen every time? Describe the process and the composer wires Freshdesk into a repeatable workflow you can run on a schedule, from chat, or as an API.

Security

Connecting Freshdesk

API keyFreshdesk uses API-key authentication. You provide your own Freshdesk secret key; ModuleX encrypts it and scopes it to your organization, so your whole team can use Freshdesk without re-authenticating.

Step-by-step setup in the Freshdesk docs

Pairs well with Freshdesk

Agents often chain Freshdesk with these — connect them once and the agent can use all of them in a single task.

Intercom13 actions

FAQ

Freshdesk + ModuleX FAQ

A ModuleX agent can run any of Freshdesk's 45 actions — across tickets, all tickets, note to tickets and ticket tags — from a plain-English request, using your organization's own Freshdesk credentials.

No. The agent selects the right Freshdesk action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

Via your own Freshdesk API key, stored encrypted and scoped to your organization.

45, spanning tickets, all tickets, note to tickets and ticket tags.

Freshdesk runs on your own credentials, so any Freshdesk usage is billed by Freshdesk directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Freshdesk to work in ModuleX.

Connect Freshdesk once with your own credentials and let your agent run all 45 actions on demand.

Put Freshdesk to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →