The Freshdesk Marketplace
Most Freshdesk gaps are already filled by somebody in the Freshdesk marketplace. The rest are a weekend of custom app work, and knowing which is which saves months.
What the Freshdesk marketplace actually is
The Freshworks Marketplace is a catalogue of apps that extend Freshdesk without you writing anything. Some are built by Freshworks, most are built by partners or by the vendor of the other product, and a handful are open contributions.
Two things are worth understanding before you browse. First, apps are scoped: a marketplace app usually renders inside a specific place in the product, most commonly the ticket sidebar, sometimes the contact page, sometimes a full page or a background service with no interface at all. Second, an app is not a magic bridge. It uses the same Freshdesk API your own code would use, so it can only do what the API allows.
That second point matters when someone tells you an app will solve a problem the platform genuinely cannot solve. It will not. It can present the problem more conveniently.
Installing an app without regretting it
Installation itself is quick. Find the app in the marketplace from your admin area, install, and work through whatever configuration screen it presents. Usually that's an API key or an OAuth handshake with the other system, plus a couple of choices about what to show.
The part people skip is the permission review. Ask these before you click install.
Install into a test environment first if you have one. If you don't, install on a quiet afternoon and open five real tickets afterwards to check nothing slowed down or moved.
The categories worth your time
There are hundreds of listings and honestly most teams need four or five apps, total. These are the clusters that earn their place.
The broader landscape is covered in the Freshdesk integrations guide. What follows is the part that guide does not cover: what to do when nothing in the catalogue fits.
Custom apps and the FDK
Freshworks publishes a developer kit, commonly called the FDK, for building your own apps. It is a command line tool. You scaffold a project, develop against a local server, then package and submit it, either privately to your own account or publicly to the marketplace.
A custom app is the right answer in three situations.
You have an internal system nobody else has. Your warehouse database, your bespoke billing platform, your in-house licensing server. Nobody is going to build that connector for you.
You need a specific workflow, not a specific integration. A button that creates a replacement order with three fields prefilled. A sidebar that shows the customer contract terms and highlights the ones about to expire. Small, opinionated, exactly shaped to your process.
You want automation the rules engine cannot express. Though before you build, check whether a webhook plus a small service somewhere else does the job. Often it does, with less to maintain.
Two honest warnings. App SDK versions move, and an app written against an older version will eventually need attention, so treat it as software you own rather than a one-off. And custom apps typically sit behind a plan requirement, so check what your current subscription allows in the Freshworks developer documentation before anyone starts building.
Reviewing what is installed
Once a year, list every installed app and answer one question for each: who would notice if this stopped working tomorrow? If the answer is nobody, uninstall it.
Dead apps are not harmless. They hold credentials, they may still be pulling data, and every one of them is a panel taking space in a sidebar agents are trying to read quickly. I have seen ticket views with six apps loaded where agents used one.
Check the API keys too. An app installed by someone who left, authenticated with their personal token, is a support outage waiting for the day IT deactivates that account.
Frequently asked questions
What is the Freshdesk FDK?
The Freshworks developer kit. The Freshdesk FDK is the command line tool you use to scaffold, run and package a custom app before installing it privately.
Can you build custom apps for Freshdesk?
Yes. Custom apps Freshdesk teams build use the FDK, the Freshworks developer kit, and install privately rather than through the Freshdesk app store.
Are Freshdesk marketplace apps free?
Many are, particularly the ones built by the other vendor to connect their own product. Others are paid, either through the marketplace or by requiring a paid plan on the other side. The listing states which.
Can I build a private app just for my account?
Yes. The FDK supports custom apps installed only into your own Freshdesk account without publishing them to the public marketplace. Plan requirements apply, so check the current developer docs.
Do apps slow down the agent view?
They can. Each sidebar app makes its own calls when a ticket loads. Two or three is fine. Six will be noticeable, especially if one of them is talking to a slow external system.
What happens to an app when I downgrade my plan?
Apps that depend on features above your new tier stop working, and custom apps may become unavailable entirely. Check plan requirements before downgrading rather than afterwards.
Is the marketplace the same for Freshdesk and Freshservice?
It's one Freshworks marketplace, filtered by product. An app listed for Freshservice will not necessarily install into Freshdesk, so check the product tag on the listing.
One app you won't find there
Duplicate detection that actually merges tickets rather than flagging them. Ticket Merger connects to Freshdesk and does it automatically, from $29/month.
Start free trial14-day free trial. No credit card required.