Your help desk or ticket system

Freshdesk

Freshdesk, made by Freshworks, is listed here as a help desk or ticket system.

Freshdesk is the support desk in Freshworks' family of business software, where a support team answers customer tickets in a shared inbox, breaks bigger requests into threads and tasks, and can bring external collaborators into a ticket. Its ticket dispatch hands out new tickets by round-robin, by agent load or by what each agent is trained in, a team can keep several SLA policies at once, and agents are scheduled with business hours, shifts and an out-of-office scheduler. Customers help themselves through a customer portal, community forums and a knowledge base that keeps article versions, and managers follow pre-defined reports, custom real-time dashboards and an agent availability dashboard.

What it lets a workflow do

Every workflow template below works from what Freshdesk gives it and changes nothing in Freshdesk.

Workflows that use it

No workflow template names Freshdesk yet. These are written for a help desk or ticket system, not for Freshdesk by name.

  • Customer satisfaction detractor follow-up Workflow template

    Works from an export from a help desk or ticket system.

    Can see: tickets and their notes. Can change: nothing.

  • Evaluation unit trial review Workflow template

    Works from an export from a help desk or ticket system.

    Can see: support history rows with ticket id, date, summary and status. Can change: nothing.

  • Help article from a resolved issue Workflow template

    Works from an export from a help desk or ticket system.

    Can see: the resolved ticket thread with internal notes. Can change: nothing.

  • Help centre gap review Workflow template

    Works from an export from a help desk or ticket system.

    Can see: each ticket's topic, subject, article sent and resolution. Can change: nothing.

  • Policy answers from the handbook Workflow template

    Works from an export from a help desk or ticket system.

    Can see: staff questions typed or exported from the help desk. Can change: nothing.

  • Service inbox routing plan Workflow template

    Teams doing this work typically use a help desk or ticket system.

    Can see: queue names and owners. Can change: nothing.

  • Stale ticket sweep Workflow template

    Works from an export from a help desk or ticket system.

    Can see: open-ticket export. Can change: nothing.

  • Support escalation brief Workflow template

    Works from an export from a help desk or ticket system.

    Can see: ticket history export. Can change: nothing.

  • Support service level definition Workflow template

    Works from an export from a help desk or ticket system.

    Can see: ticket export with created, first reply and resolved times. Can change: nothing.

  • Support ticket triage Workflow template

    Works from an export from a help desk or ticket system.

    Can see: queue export of new or unassigned tickets. Can change: nothing.

Teams whose workflow templates use a help desk or ticket system:

How it connects

Each connector below is one we know of, with who publishes it, where and when we found it, and its trust level.

Published by its maker

  • Connector from the maker of Freshdesk

    A connector an AI assistant can use.

    Published by Freshworks, as the maker's own page states.

    Found in the maker's own documentation on 11 November 2026. Last checked on 12 November 2026.

    ListedFound in a named public source on a stated date. We have not reviewed or used it.

  • Programming interface from the maker of Freshdesk

    A programming interface for software developers.

    Published by Freshworks, as the maker's own page states.

    Found in the maker's own documentation on 12 November 2026. Last checked on 12 November 2026.

    ListedFound in a named public source on a stated date. We have not reviewed or used it.

What setup takes, and who approves it

Connecting a workflow to Freshdesk is agreed when the work is scoped: a person who looks after Freshdesk at your company approves how the workflow signs in and what it may see and change.

No time is promised here. Where no connector exists, the workflow works from an export.

What was checked, and when

  • The maker's own pages: read on 12 November 2026.
  • The workflow templates above: each link was read from the template's own text and reviewed, most recently on 12 November 2026.

How we list systems and connectors

Next step

Start your plan

Request this workflow

Want a workflow above built for your team? Open it and choose how to start, or book a fit call.

Technical details

  • Freshworks Model Context Protocol (MCP) server · MCP serverFound in the maker's own documentationhttps://<subdomain>.freshdesk.com/mcpFreshworks describes an MCP server that lets AI tools such as Cursor and Claude connect to and interact with Freshdesk, with the endpoint on each account's Freshdesk domain.The maker’s page
  • Freshdesk API · Public APIFound in the maker's own documentationhttps://<domain>.freshdesk.com/api/v2Freshdesk describes a REST API that reads, creates, updates and deletes helpdesk data, authenticated with a personal API key.The maker’s page