A Freshdesk MCP where exactly one node can email your customer
Connect your account domain and one agent API key, and Freshdesk tickets, conversations, contacts, companies, knowledge base articles, and time entries become workflow steps for visual automations and AI agents. Notes are private by default, both deletes are soft deletes with a restore node behind them, and the single node that emails the ticket requester says so in its own name.
What the Freshdesk MCP connector does
The Freshdesk connector for Mattering Automations is 38 nodes across the v2 API: the ticket lifecycle (list, search with the filter query language, read, create, update, soft delete, and restore), full conversation threads with public replies and private notes, contacts with soft delete, restore, and name autocomplete, companies, agents, groups, and products, ticket and contact field schema discovery including custom fields, satisfaction ratings, time entries, the solutions knowledge base, and canned response reads.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can answer how many urgent tickets are open in a region, summarize a thread that already runs to forty replies, or find the contact behind an email address, without anyone opening the Freshdesk dashboard.
Because Mattering is a work platform rather than middleware, support work lands somewhere useful by default: a scheduled sweep of aging tickets can open tasks in Mattering Productivity, a satisfaction rating below a threshold can start a follow up, and a summarized thread can post into a channel, all on one canvas next to the rest of the work.
The email boundary is explicit rather than advisory. Freshdesk: Reply to Ticket (Emails Requester) sends a real email to the ticket requester the moment it succeeds, and a sent reply cannot be unsent, which is why the node is named for the side effect. Freshdesk: Add Note to Ticket is the safe path for everything an automation wants to say: notes default to private, are visible to agents only, and send the requester nothing. Set private to false and the note becomes visible on the customer portal, which is a decision you make rather than one you stumble into.
One connection, three surfaces
- Visual automations. Drag Freshdesk nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Freshdesk node, ready to drop on the canvas
38 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 24
Freshdesk: Filter Tickets (Query Language)
Search tickets with Freshdesk's filter query language, for example priority:4 OR priority:3, agent_id:3001 AND status:2, or cf_region:'emea'. Returns 30 results per page and the page number is capped at 10, so at most 300 results are reachable per query (the total count is still exact). New updates take a few minutes to index. Archived tickets are excluded.
Freshdesk: Get Company
Fetch one company by id, including domains, custom fields, health score, and account tier.
Freshdesk: Get Contact
Fetch one contact by id, including custom fields, tags, other_emails, and company links.
Freshdesk: Get Current Agent
Return the agent the API key belongs to. Needs no configuration, which makes it the connector's credential health check, and it is the one Agent API that does not require admin privileges, so it works for any agent's key. A wrong key returns 401 with Freshdesk's invalid_credentials error code; the response never echoes the API key.
Freshdesk: Get Group
Fetch one agent group by id, including its member agent ids and escalation settings.
Freshdesk: Get Solution Article
Fetch one knowledge base article by id, with its full HTML description, status, tags, SEO metadata, and feedback counts.
Freshdesk: Get Ticket
Fetch one ticket by id, with optional embeds for conversations (first ten), requester, company, and stats. Each include costs one extra API credit (conversations costs two); the full thread comes from List Ticket Conversations.
Freshdesk: List Agents
List the helpdesk's agents with their contact profiles, group and role ids, and availability. Filter by exact email, mobile, phone, or state (fulltime/occasional). Requires admin privileges on the API key's agent (only Get Current Agent is exempt from that requirement).
Freshdesk: List Canned Response Folders
List canned response folders with their response counts. The canned response APIs are documented as admin-only, so the API key's agent needs admin privileges.
Freshdesk: List Canned Responses in Folder
List the canned responses in a folder WITH their full content (title, plain-text content, and content_html, which may carry Freshdesk placeholders like {{ticket.url}}). Documented admin-only. Useful as reply templates feeding the Reply to Ticket node.
Freshdesk: List Companies
List companies with their domains, health score, account tier, renewal date, and custom fields, up to 100 per page.
Freshdesk: List Contact Fields
List the account's contact field definitions: default and custom fields with their names (the keys used in a contact's custom_fields), labels, types, and edit permissions. The schema-discovery step before creating or updating contacts.
Freshdesk: List Contacts
List contacts, alphabetical, up to 100 per page. Filter by exact email, phone, mobile, company, state, or updated_since. Unblocked, undeleted contacts are returned by default; state=deleted lists soft-deleted contacts for the Restore Contact node.
Freshdesk: List Groups
List agent groups with their member agent ids and escalation settings. Group ids feed ticket assignment (group_id on create/update ticket).
Freshdesk: List Products
List the account's products (multi-product helpdesks). Product ids feed ticket routing (product_id on create/update ticket).
Freshdesk: List Satisfaction Ratings
List customer satisfaction survey ratings across the helpdesk, with the ticket, agent, and group each rating belongs to. New-survey rating values run from 103 (extremely happy) to -103 (extremely unhappy) on the default_question key; classic surveys use 1 happy, 2 neutral, 3 unhappy.
Freshdesk: List Solution Articles
List the articles inside a solution folder, including each article's status (1 draft, 2 published), hit count, and thumbs up/down feedback.
Freshdesk: List Solution Categories
List the knowledge base's top-level solution categories. The KB hierarchy is category, then folder, then article; walk down with List Solution Folders.
Freshdesk: List Solution Folders
List the folders inside a solution category, with each folder's visibility setting and article count.
Freshdesk: List Ticket Conversations
List a ticket's full conversation thread: replies (source 0) and public or private notes (source 2), oldest first, up to 100 per page. The ticket's original description is not a conversation; it lives on the ticket itself.
Freshdesk: List Ticket Fields
List the account's ticket field definitions: default and custom fields, their names (the keys used in custom_fields and the Filter Tickets query language), labels, types, required flags, and dropdown choices. The schema-discovery step before creating or filtering tickets.
Freshdesk: List Tickets
List tickets, newest first by default (up to 100 per page, 300 pages max). By default only tickets created in the last 30 days that are not deleted or spam are returned; set updated_since for older tickets, or the deleted filter to list soft-deleted tickets for the Restore Ticket node. Each include embed costs two extra API credits.
Freshdesk: List Time Entries
List time entries logged on tickets across the helpdesk, filterable by company, agent, execution window, and billable flag. time_spent is in hh:mm format.
Freshdesk: Search Contacts by Name
Autocomplete-style contact search by name, case insensitive, matching from the start of each word (john and jonz both find John Jonz; hn does not). Returns id and name pairs; follow with Get Contact for the full record.
Action nodes 14
Freshdesk: Add Note to Ticket
Add a note to a ticket. Notes are PRIVATE by default (visible to agents only), which makes this the safe path for automation commentary; it sends nothing to the requester unless you explicitly set private to false (a public note is visible on the customer portal). notify_emails pings specific agents about the note.
Freshdesk: Create Company
Create a company. Name is required and must be unique (a duplicate returns a duplicate_value error). Contacts whose email matches one of the company's domains are associated with it automatically. Returns 201 with the new company.
Freshdesk: Create Contact
Create a contact. Name is required plus at least one identifier: email, phone, mobile, twitter_id, or unique_external_id (email must be unique; a duplicate returns a duplicate_value error). Returns 201 with the new contact. Reversible: contacts can be soft-deleted and restored.
Freshdesk: Create Solution Article
Create a knowledge base article in a folder. Status 1 saves it as a draft (this node's default, the safe path); status 2 publishes it to the portal immediately, subject to the folder's visibility. Returns 201 with the new article.
Freshdesk: Create Ticket
Create a ticket. Identify the requester by email, requester_id, phone, or unique_external_id (one is required); an unknown email or phone creates a new contact automatically. Returns 201 with the new ticket. Helpdesk notification rules may email the requester about the new ticket. Reversible: a created ticket can be soft-deleted and restored.
Freshdesk: Create Time Entry
Log time on a ticket. ALWAYS set time_spent (hh:mm) for a plain log entry: if time_spent and timer_running are both omitted, Freshdesk starts a RUNNING TIMER instead, and starting a timer stops any other timer that agent has running. Returns 201 with the new entry.
Freshdesk: Delete Contact
DESTRUCTIVE: soft-delete a contact (the docs title this endpoint Soft Delete a Contact). The contact is recoverable with Restore Contact and shows up under List Contacts with state=deleted. The separate hard-delete endpoint, which also destroys the contact's tickets permanently, is deliberately not offered by this connector.
Freshdesk: Delete Ticket
DESTRUCTIVE: soft-delete a ticket. Per the docs the ticket is recoverable: list it with the deleted filter on List Tickets and bring it back with Restore Ticket (no scrub timer is documented). Permanent deletion (emptying trash) only exists in the UI and the bulk endpoints, which this connector deliberately does not offer.
Freshdesk: Reply to Ticket (Emails Requester)
SENDS A REAL EMAIL: post a public reply on a ticket, which Freshdesk immediately emails to the ticket requester (plus any cc/bcc). A sent reply cannot be unsent, so point automations at tickets you intend to answer; for internal collaboration use Add Note to Ticket (private by default) instead. When testing, use a scratch ticket whose requester is your own address.
Freshdesk: Restore Contact
Restore a soft-deleted contact. Find deleted contacts with List Contacts using state=deleted. Returns 204 on success.
Freshdesk: Restore Ticket
Restore a soft-deleted ticket back to the account. Find deleted tickets with List Tickets using the deleted filter. Returns 204 on success.
Freshdesk: Update Company
Update a company. Only the fields you fill are sent, so partial updates are safe. The domains array replaces the existing domain list when provided.
Freshdesk: Update Contact
Update a contact. Only the fields you fill are sent, so partial updates are safe. Note that a contact who has been converted to an agent can no longer have name, phone, mobile, or job title changed through this API.
Freshdesk: Update Ticket
Update a ticket: change status (2 Open, 3 Pending, 4 Resolved, 5 Closed), reassign (responder_id / group_id), set priority, replace tags, or edit subject and description. Only the fields you fill are sent. Updating description rewrites the ticket's original description, not the conversation; replies and notes are separate nodes. Subject and description cannot be updated on outbound-email tickets.
Connecting Freshdesk takes one credential
Every Freshdesk agent has a personal API key on their own Profile Settings page, just below the change password section. API access is a paid plan feature: Freshdesk's support documentation states that on its free tier the API key and the API functionality are not available, and the published API rate limit table covers only the paid plans. The 14 day trial does include the API, rate limited to 50 calls per minute. The key acts as that agent and carries exactly that agent's permissions, so create a dedicated integration agent rather than borrowing a human admin's key. The connector also needs the account domain, which is the examplecorp in examplecorp.freshdesk.com, because v2 has no shared API host: every call goes to your own account host.
In Freshdesk, sign in as the agent the automations should act as, open Profile Settings, and copy the API key shown below the change password section.
In Mattering Automations, open Connectors, click Add Connector, choose Freshdesk, and create a credential. The form shows generic Username and Password labels: the username is your account domain and the password is the API key.
Click Test Connection. Mattering builds your account host from the domain, authenticates with the key, and reports which agent the credential belongs to.
All 38 Freshdesk nodes appear in the canvas palette. Run Freshdesk: List Ticket Fields early, because it returns the field names, types, and dropdown choices (including any custom statuses) that the ticket nodes and the filter query language expect.
Common uses for the Freshdesk MCP
Search that speaks the helpdesk's own query language
Freshdesk: Filter Tickets (Query Language) takes expressions like priority:4 AND status:2, or cf_region:'emea', so an agent can ask a real question instead of paging through everything. Enter the bare expression and the connector adds the quoting the API requires. Custom fields query by name with the cf_ prefix, and Freshdesk: List Ticket Fields tells you what those names are.
Triage and routing without opening the dashboard
Freshdesk: List Tickets and Freshdesk: Get Ticket read the queue, Freshdesk: List Ticket Conversations pulls the full thread, and Freshdesk: Update Ticket sets status, priority, tags, or a new owner. Freshdesk: List Groups and Freshdesk: List Agents supply the ids that assignment needs, and Freshdesk: List Products covers multi product helpdesks.
Notes a robot can write, replies a person approves
Freshdesk: Add Note to Ticket posts agent only commentary and can ping specific agents with notify_emails, which makes it the right home for AI summaries, sentiment flags, and internal context. Freshdesk: Reply to Ticket (Emails Requester) is the deliberate second step that actually answers the customer, and Freshdesk: List Canned Responses in Folder can feed it approved wording.
Contacts and companies kept in step
Freshdesk: Search Contacts by Name does autocomplete style lookup from the start of each word, Freshdesk: Get Contact and Freshdesk: List Contacts return the full records, and Freshdesk: Create Contact and Freshdesk: Update Contact keep them current. Freshdesk: List Companies, Freshdesk: Create Company, and Freshdesk: Update Company do the same for accounts, with Freshdesk: List Contact Fields naming the custom field keys first.
Knowledge base articles that start as drafts
Walk the hierarchy with Freshdesk: List Solution Categories, Freshdesk: List Solution Folders, and Freshdesk: List Solution Articles, then read one with Freshdesk: Get Solution Article. Freshdesk: Create Solution Article writes a new article as a draft by default, so an automation can propose documentation without publishing it to the customer portal.
Deletes you can walk back
Both deletes in this connector are soft deletes with a shipped recovery loop. Freshdesk: Delete Ticket removes a ticket from the queue, the deleted filter on Freshdesk: List Tickets finds it again, and Freshdesk: Restore Ticket brings it back. Freshdesk: Delete Contact behaves the same way, listable with state set to deleted and reversed by Freshdesk: Restore Contact.
Example: Urgent tickets get summarized, noted, and routed, and only a person emails the customer
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a schedule runs every ten minutes.
Freshdesk: Filter Tickets (Query Language) searches for what needs attention, for example status:2 AND priority:4, and returns the matching ticket ids.
Freshdesk: List Ticket Conversations pulls each ticket's full thread, replies and notes together, oldest first.
Matter reads the thread and produces a short summary plus a suggested answer.
Freshdesk: Add Note to Ticket posts the summary as a private note. Nothing reaches the customer, because notes are agent only unless you say otherwise.
Freshdesk: Update Ticket reassigns the ticket to the right group, and a task in Mattering Productivity carries the suggested answer to a person, who is the one who runs Freshdesk: Reply to Ticket (Emails Requester).
Freshdesk MCP questions, answered
What Freshdesk operations are supported?
38 nodes on the v2 API: tickets (list, filter with the query language, get, create, update, soft delete, restore), conversations (read the thread, public reply, private note), contacts (list, get, create, update, soft delete, restore, name autocomplete), companies (list, get, create, update), agents, groups, and products as reads, ticket and contact field schema discovery, satisfaction rating reads, time entry logging and listing, the solutions knowledge base (categories, folders, articles, and draft first article creation), and canned response reads. Deliberately not shipped: the bulk endpoints and the Jobs API, ticket merge and the archive family, attachment upload and deletion, contact hard delete (which also destroys the contact's tickets and cannot be undone), outbound email ticket creation and ticket forwarding, agent and field write APIs, satisfaction rating creation, and conversation update or delete.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively. The 24 read nodes are the safest surface to hand an agent, because none of them change a ticket or send anything.
Can this connector email a customer by accident?
One node can email a customer, and it is named for it. Freshdesk: Reply to Ticket (Emails Requester) posts a public reply that Freshdesk immediately emails to the ticket requester plus any cc or bcc, and a sent reply cannot be unsent. Everything else an automation typically wants to write belongs on Freshdesk: Add Note to Ticket, which defaults to private, is visible to agents only, and sends the requester nothing (notify_emails pings agents, not customers). When testing the reply node, point it at a scratch ticket whose requester is your own address. Note that creating a ticket can also generate customer email if your helpdesk's own notification rules are configured to send one, which is a Freshdesk setting rather than a connector behavior.
What goes in the Username and Password fields?
The username is your Freshdesk account domain, the examplecorp in examplecorp.freshdesk.com, and the password is the agent API key. The stored username is not what is sent as the Basic username: the connector uses the domain only to build your account host, and builds the authorization header itself as base64 of the API key followed by a dummy password, which is the convention Freshdesk's own docs specify with curl -u yourapikey:X. Pasting a full helpdesk URL into the username is fine too, because the connector normalizes it down to the domain.
Why do my searches only return recent tickets?
Freshdesk: List Tickets returns only tickets created in the last 30 days unless you set updated_since, and it caps out at 300 pages of 100, which is 30,000 tickets. Set updated_since to reach older tickets. Freshdesk: Filter Tickets (Query Language) is the other route, and it has different limits: 30 results per page with the page number capped at 10, so at most 300 results are reachable per query, although the total count it reports stays exact. Recent updates take a few minutes to be indexed for that search, and archived tickets are excluded from it.
If a workflow deletes the wrong ticket, is it gone?
No, both deletes here are soft deletes and the full recovery loop ships. A deleted ticket is listed by the deleted filter on Freshdesk: List Tickets and brought back by Freshdesk: Restore Ticket; there is no separate deleted tickets endpoint, the filter is the list. A deleted contact is listed with state set to deleted and brought back by Freshdesk: Restore Contact. Both delete nodes are still flagged destructive, because emptying the trash in the Freshdesk interface can make a deletion permanent outside the API. The hard delete endpoint, which also destroys all of the contact's tickets and cannot be undone, is deliberately not built.
Why are status, priority, and source numbers?
That is how the API models them, and it is the single most common source of confusion. Status is 2 Open, 3 Pending, 4 Resolved, 5 Closed. Priority is 1 Low, 2 Medium, 3 High, 4 Urgent. Source is 1 Email, 2 Portal, 3 Phone, 7 Chat, 9 Feedback Widget, 10 Outbound Email. Accounts can also define custom statuses with their own numbers, which is exactly why the schema discovery nodes matter: run Freshdesk: List Ticket Fields to see the real choices for your account, and Freshdesk: List Contact Fields before writing contact custom fields.
What are the rate limits, and do I need admin privileges?
Rate limits are per minute and account wide, and even invalid requests count against them. Freshdesk documents 50 calls per minute for trial accounts, and for current plans Growth 100, Pro 400, and Enterprise 700 (older plans are Blossom 100, Garden 200, Estate 400, Forest 700), with per endpoint sub caps on top and extra credits charged for include embeds. Every response carries X-RateLimit-Total, X-RateLimit-Remaining, and X-RateLimit-Used-CurrentRequest, and a 429 comes with a Retry-After in seconds; there is no automatic retry, so build backoff into the automation. On privileges: every Agent API except the currently authenticated agent read requires an admin key, and the canned response APIs are admin only, so Freshdesk: List Agents, Freshdesk: List Canned Response Folders, and Freshdesk: List Canned Responses in Folder need an admin agent's key. Everything else works with a plain agent key. On plans: API access is a paid plan feature. Freshdesk documents the API key and the API functionality as unavailable on its free tier, and the rate limit table above covers only the paid plans. To test without paying, use the 14 day trial, which needs no credit card and runs at 50 calls per minute.
Put Freshdesk to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Freshdesk is a product of its respective owner; Mattering is an independent platform.