The Freshdesk Marketplace Explained (How Apps & Custom Apps Work)

What the Freshdesk Marketplace actually is

The Marketplace is a catalogue of apps that extend Freshdesk without you writing (much) code. Some are built by Freshworks, most are built by third-party developers, and a handful you build yourself. Per Freshworks' Installing Apps from Freshworks Marketplace documentation, you reach it from Admin → Support Operations → Apps → Get More Apps, where you can filter by category or search for a specific integration, read the full listing, and install with a single click.

Under the hood, Freshworks recognises three distinct app types, and the distinction matters for how an app is distributed:

• Freshworks (Marketplace) apps — publicly displayed in the Marketplace and installable by any Freshworks customer.
• Custom apps — private only to the customer that built them; they never appear in the public gallery.
• External apps — not installed inside Freshdesk at all, just listed with a link to an external website.

That taxonomy comes straight from the app submission process docs, and it's the mental model to carry through the rest of this piece: public apps are shared with the world, custom apps stay inside your four walls.

Installing a public app from the Marketplace

The happy path is genuinely fast. For most integrations — a CRM connector, a translation tool, a survey app — installing is a matter of finding the tile and authenticating.

1. Go to Admin → Support Operations → Apps → Get More Apps.
2. Browse by category (CRM & Sales, Productivity, Agent Productivity, and so on) or search for the app by name.
3. Open the listing to read what it does, check the rating and install count, and confirm pricing — some apps are free, others carry their own subscription.
4. Click Install, enter the necessary credentials (usually an API key or an OAuth handshake), and the app is live.

If you want a shortlist of what's actually worth installing rather than a raw catalogue, we've rounded up the best Freshdesk marketplace apps by job-to-be-done. Once an app is installed, it moves out of the browse gallery and into your own Apps list — the section your help desk uses to show only the extensions you've actually enabled, so configuring or uninstalling any of them is a one-click affair.

Notice the App Type filter in that Manage Apps view: Public, Custom, and In Development. That filter is the clearest window into the three-way split — public apps you installed from the Marketplace, custom apps built for your account, and apps still being built and tested. On a fresh trial the list reads 0 Public App with a "get started by installing Recommended Apps" prompt, which is exactly what you'd expect before anyone has installed anything.

Custom apps: private, account-scoped, and not reviewed

A custom app is one you build for your account and nobody else's. Formerly called Freshplugs, custom apps — per Freshworks' What is a Custom App? guide — are "installed only to your account" and exist to integrate with internal tools or implement workflows specific to your business. They don't get listed publicly, and they can't be shared across other Freshdesk instances.

The lifecycle differs from a public app in two important ways. First, install scope is the whole point: a custom app is published and installed only in the same account it was created in. Second, the review model is different — custom apps are not subject to the Freshworks review process and are available for installation within roughly 30 minutes of submission. A public Marketplace listing has to pass review; a private custom app can go live almost immediately because only you will ever see it.

You build one on the Freshworks developer platform, pack the app, fill in the App Information and installation details, then Save and Publish. It then appears under Manage Apps → Custom Apps in your account, ready to install. Custom apps can be placed in specific spots in the agent workspace — the Ticket Details page, the Contact Details page, the New Ticket screen, and the New Email composer — so the integration shows up exactly where an agent needs it. Freshworks keeps up to three published versions live at once, so you can promote a new build while agents on an older version keep working uninterrupted.

Public app vs. custom app: which path to take

The choice usually comes down to whether the thing you need already exists and whether anyone else should be able to use it.

If an off-the-shelf tile does the job, install it and move on. If your workflow is genuinely specific — an internal inventory system, a bespoke approval flow — a custom app is the sanctioned way to wire it in without exposing it to anyone else.

The honest limits — and where an AI layer picks up

The Marketplace model is solid at what it does: it distributes integrations cleanly, keeps public apps behind a review gate, and lets you build private apps without polluting the public catalogue. But it's worth being clear-eyed about the ceiling.

First, plan gating. Apps aren't available on the entry-level Free/Sprout tier — you need Growth, Pro, or Enterprise (or the legacy Blossom/Garden/Estate/Forest plans) to install and manage them. Confirm your own plan before you architect a workflow around an app.

Second, and more fundamental: most marketplace apps surface data, they don't reason over it. A CRM app can show an agent the customer's account panel next to the ticket; it can't read the ticket, understand what the customer is actually asking, decide which account field matters, and write the reply. A custom app can pull a record from your internal system into the ticket sidebar — but a human still has to interpret it and type the response. The app model moves information; it doesn't do the thinking.

That's the seam an AI agent layer fits into, and it's worth weighing the build-versus-buy tradeoff before you commit engineering time to a custom app that ultimately just displays a value. The broader category of AI agents for customer service exists to do the reasoning-heavy work a marketplace tile can't. Macha is one such layer: it runs on top of the Freshdesk you already use as a native connector — it does not replace Freshdesk, and it isn't a rival marketplace. You connect Macha to Freshdesk with your subdomain and API key, and it works the same tickets your apps already touch: reading the incoming message, deciding what to do, calling out to your own systems through a custom tool that turns a REST API into something an agent can invoke, and drafting or posting a grounded reply. Where a custom app would show an agent an order status, Macha can fetch it and write the answer around it — the automation step covered in more depth in how to automate Freshdesk with AI. (Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. And credits are consumed per AI action, not per resolution — see the pricing breakdown.)

The clean division of labour: use the Marketplace and custom apps for what they're built for — distributing integrations and surfacing data inside the agent workspace — and layer an AI agent on top for the part the app model can't do, which is turning that data into a real, sent answer.

FAQ

Where do I install apps in Freshdesk? Go to Admin → Support Operations → Apps → Get More Apps. Browse or search the Marketplace, open a listing, click Install, and enter the required credentials. Installed apps then show up in your own Apps (Manage Apps) list.

What's the difference between a Marketplace app and a custom app? A Marketplace (Freshworks) app is publicly listed and installable by any Freshworks customer after passing review. A custom app is private to your account only — it never appears in the public gallery, isn't reviewed, and is available to install within about 30 minutes of being submitted.

Are Freshdesk apps available on every plan? No. Apps aren't supported on the entry-level Free/Sprout tier. You'll need Growth, Pro, or Enterprise (or the legacy Blossom/Garden/Estate/Forest plans) to install and manage them. Check your own plan before designing a workflow around an app.

Where do custom apps appear once I build them? Under Manage Apps → Custom Apps in your account. You can place them on the Ticket Details page, Contact Details page, the New Ticket screen, or the New Email composer, and Freshworks keeps up to three published versions live at once.

Can I add AI to Freshdesk without building a custom app or replacing Freshdesk? Yes. An AI agent layer like Macha connects to Freshdesk as a native connector and runs on top of your existing help desk — it's not a marketplace competitor or a helpdesk replacement. It reads tickets, calls your own tools, and drafts grounded replies, doing the reasoning a marketplace tile or custom app doesn't.

Ready to add the reasoning layer your marketplace apps can't? Start a free trial of Macha and connect it to your Freshdesk in minutes.