Freshdesk
Customer support.
Verdict
Common use cases
- Triage support tickets during morning standup
- Create tickets from customer Slack messages
- Reply to urgent tickets without switching tabs
- Pull ticket status before shipping a fix
- Summarize open issues for weekly review
Integration
- Vendor
- Freshdesk
- Category
- crm
- Auth
- API_KEY
- Tools
- 7
- Composio slug
freshdesk
Tools
- Create Ticket
Creates a new ticket in freshdesk.
- Delete Ticketdestructive
Deletes an existing ticket in freshdesk.
- Get Tickets
Retrieves a list of tickets from freshdesk.
- List All Tickets
Lists all tickets in freshdesk.
- Reply to Ticket
Replies to an existing ticket in freshdesk.
- Update Ticket
Updates an existing ticket in freshdesk.
- View Ticket
Views an existing ticket in freshdesk.
Setup
Setup guide
- 11. In Switchy, open the Space where you want to use Freshdesk and click 'Add Integration' from the sidebar. 2. Select 'Freshdesk' from the MCP catalog and choose 'Connect with API Key'. 3. Log into your Freshdesk account, navigate to Profile Settings, and copy your API key from the API section (you'll need admin or agent permissions). 4. Paste the key into Switchy's connection dialog and confirm. 5. Test the connection by typing '@Freshdesk list all tickets' in your Space — you should see a response with recent tickets. 6. To invoke any tool, @mention Freshdesk followed by your request, like '@Freshdesk create a ticket for login issue reported by user@example.com'. The MCP will confirm actions and return ticket IDs or details inline.
What teammates see: by default, memories from Freshdesk are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Triage High-Priority Tickets
@Freshdesk get all tickets with priority 'high' and status 'open'. Group them by category and show me the requester email and subject line for each.Open in a Space →
Create Ticket from Chat
@Freshdesk create a ticket with subject 'Payment processing timeout' for requester support@example.com, priority 'urgent', and description 'Customer reports checkout fails after entering card details'.Open in a Space →
Reply to Waiting Customer
@Freshdesk reply to ticket #4521 with this message: 'We've identified the issue and deployed a fix. Please try again and let us know if you still see problems.'Open in a Space →
Check Ticket Before Deploy
@Freshdesk view ticket #4389 and tell me the current status, last update time, and whether the customer has replied since our last message.Open in a Space →
Weekly Open Ticket Summary
@Freshdesk list all tickets with status 'open' or 'pending'. Show me how many we have in each category and highlight any that are older than 7 days.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@freshdesk show me all open tickets tagged 'billing' that haven't been updated in the last 3 days
Found 12 open tickets matching your criteria. Here's a summary: 8 tickets are marked Priority 2 (High), 4 are Priority 3 (Medium). The oldest unattended ticket is #4521 from user sarah.chen@example.com, opened 6 days ago regarding invoice discrepancy. Tickets #4498 and #4502 both mention payment gateway timeouts. The remaining 9 tickets span refund requests, subscription changes, and billing address updates. Most recent is #4589 from 4 days ago.
This example shows Freshdesk's filtering and list capabilities. The MCP requires API key auth with read permissions on tickets. Response shape depends on your Freshdesk plan's custom fields and tag structure. If your account has thousands of tickets, consider narrowing the date range to avoid rate limits on initial queries.
@freshdesk create a ticket for demo@company.com: 'Dashboard widget not loading on mobile Safari, returns 403 error' — set priority to high and tag it 'mobile-bug'
Ticket #4612 created successfully. Assigned to: Support Team (default group). Status: Open. Priority: High. Tags: mobile-bug. Subject: 'Dashboard widget not loading on mobile Safari, returns 403 error'. Requester: demo@company.com. The ticket is now visible in your Freshdesk queue and the requester will receive an automated confirmation email per your account's notification settings.
This demonstrates ticket creation with custom priority and tagging. The MCP needs write permissions on tickets. Side-effect: the requester receives an email immediately unless you've disabled auto-notifications in Freshdesk settings. If demo@company.com doesn't exist as a contact, Freshdesk will create a new contact record automatically.
@freshdesk pull the last 5 resolved tickets about 'API integration' and draft a summary of common issues for our engineering team
Retrieved 5 resolved tickets (IDs: #4587, #4521, #4489, #4401, #4378). Common patterns: 3 tickets involved OAuth token expiration after 24 hours, suggesting clients aren't implementing refresh flows. 2 tickets reported 429 rate-limit errors during bulk operations—users were unaware of the 100 requests/minute cap. One ticket (#4489) highlighted unclear error messages when webhook signatures fail validation. Recommendation: update API docs to emphasize token refresh and rate-limit handling; consider adding code samples for webhook signature verification.
This example pairs Freshdesk data retrieval with AI synthesis. The MCP fetches ticket content, then the AI identifies recurring themes across multiple support interactions. Useful for spotting documentation gaps or product friction points. Accuracy depends on how consistently your team tags and categorizes tickets—inconsistent tagging yields weaker pattern recognition.
Use-case deep-dives
When Freshdesk MCP beats manual ticket assignment for small teams
A 5-person SaaS startup handling 40-60 support tickets daily uses this MCP during morning standup to batch-assign tickets by urgency and product area. The team shares one Switchy workspace where the AI pulls unassigned tickets, reads the last three customer replies, and drafts assignment recommendations based on each engineer's recent commit history. The MCP's reply and update tools let the AI close simple how-to questions without human review, cutting first-response time from 4 hours to 20 minutes. This works until ticket volume crosses 150 daily—at that scale, you need Freshdesk's native automation rules instead of AI-driven triage. If your team is under 10 people and tickets cluster around product questions rather than billing disputes, this MCP turns Switchy into your ticket command center.
Using Freshdesk MCP to extract feature requests from support threads
A 12-person B2B product team runs a Friday ritual where the product manager asks Switchy to scan the week's closed tickets for recurring feature requests and pain points. The MCP's list and view tools let the AI read ticket bodies and internal notes across 80-120 tickets in under a minute, then group requests by theme and count mentions. The output becomes the input for next week's roadmap discussion—no manual tagging required. This scenario depends on your support team writing decent internal notes; if tickets are just one-line closures, the AI has nothing to synthesize. The MCP also can't access Freshdesk's canned responses or macros, so you're limited to ticket content itself. If your support team already uses Freshdesk tags religiously, native reporting beats this approach—but most small teams don't tag consistently, making the MCP the faster path to insight.
When Freshdesk MCP accelerates support rep ramp-up time
A 7-person support team onboards a new hire by giving them Switchy access to a workspace where the AI uses the Freshdesk MCP to pull historical tickets from the last 90 days. The new rep asks questions like 'show me all tickets about SSO setup failures' or 'what's our standard response for billing cycle questions,' and the AI retrieves relevant ticket threads with replies intact. The MCP's view and list tools make this a 10-minute exercise instead of a 2-hour Freshdesk UI deep-dive. The limitation: the MCP can't access Freshdesk's solution articles or knowledge base, so you're only searching ticket history, not your help center. This works best for teams under 15 people where institutional knowledge lives in ticket replies rather than formal documentation. If your new hire needs to learn 50+ help articles, point them at Freshdesk's native search—but for learning how your team actually talks to customers, this MCP shortens ramp-up from 3 weeks to 10 days.
Frequently asked
What does the Freshdesk MCP do in Switchy?
It lets your AI agents create, read, update, and reply to Freshdesk support tickets without leaving the workspace. Agents can pull ticket lists, view individual conversations, post replies, and even delete tickets when needed. This means you can triage support queues, draft responses, or summarize customer issues directly in Switchy instead of switching tabs to Freshdesk.
Do I need admin access to connect Freshdesk?
You need an API key from Freshdesk, which any agent or admin can generate from their profile settings. You don't need full account admin rights, but the key inherits your Freshdesk permissions—so if you can't delete tickets in Freshdesk, the MCP won't be able to either. Use an account with the access level your team actually needs.
Can the Freshdesk MCP handle ticket attachments or custom fields?
No. The seven tools focus on core ticket operations—creating, reading, updating, replying, and deleting. Attachments, custom fields, time tracking, and SLA rules aren't exposed. If your workflow depends on those, you'll still need to open Freshdesk directly or build a custom integration against their full REST API.
Why use this instead of just opening Freshdesk in a browser?
You use it when you want an AI agent to act on tickets as part of a larger workflow—like summarizing overnight support volume, drafting replies based on your knowledge base, or escalating high-priority issues to Slack. The MCP turns Freshdesk into a programmable tool your agents can call, not a separate app you context-switch into.
Who on the team should connect the Freshdesk MCP?
Whoever owns your support triage process and has a Freshdesk account with the right permissions. Typically a support lead or operations manager. The connection lives in your Switchy workspace, so once it's set up, any team member with workspace access can use it in their agent prompts—they don't each need their own Freshdesk API key.