What we do
Tools
Industries
Department
How we workLet's talk →
Home/Freshdesk/Freshdesk Integrations That Act on Tickets
Freshdesk

Freshdesk Integrations for When the Sidebar Shows the Record and Nothing Else Moves

An agent resolves a billing complaint, and the account manager hears about it from the customer a week later. The two systems are connected: the Marketplace app puts the CRM record right beside the ticket. Showing it is all that app was made for. Freshdesk gives you three ways to go further: an app from the Freshdesk Marketplace, a custom app your developers build and install in your own account, and the Freshdesk API, with webhooks fired by automation rules.

Pick the Freshdesk route by what should happen

What you want to happen Route that usually fits Check first
New and updated tickets post to a Slack channel, and agents reply from Slack The Slack app from the Freshdesk Marketplace. Which ticket events post, and to which channel, so every group's tickets don't pour into one place.
A bug report on a ticket becomes a linked Jira issue The Jira app from the Marketplace. Whether seeing the issue from the ticket is enough, or the customer should hear back when the fix ships.
Agents see the Salesforce or HubSpot record beside the ticket The listed Salesforce or HubSpot app. Whether seeing is all you need. A resolved ticket updating a deal or account is outside what these apps do.
Alerts in Microsoft Teams, or a support widget on a WordPress site The listed Teams or WordPress app. Whether people need to act from Teams, or only need to be told.
A niche order system or an in-house tool with no listing A custom app built with the Freshworks developer kit, plus API calls to the other system. That the other system has an API, or at least an export you can rely on.
Something in another system should change when a ticket does An automation rule with a webhook action, calling a small service that makes the change. Where a failed call gets logged, so a missed update gets noticed.

A custom app inside Freshdesk, or a sync running between the two systems

In the agent's screen

Custom Freshdesk app

  • Built with the Freshworks developer kit (FDK) and uploaded to your own account instead of being listed on the Marketplace.
  • Shows another system's data in the ticket sidebar and can give agents buttons to act on it.
  • Right when an agent has to look something up or take an action partway through a ticket.
Runs with nobody clicking

API sync

  • Calls the Freshdesk REST API and the other system's API on a schedule, or when a webhook arrives.
  • Creates tickets, updates fields and writes outcomes elsewhere without an agent doing anything.
  • Right when records in both systems have to agree.

Plenty of builds use both: the app for what agents see, the sync for what has to happen whether anyone's looking or not.

Signs the installed Freshdesk app has hit its ceiling

The CRM record is visible, and the CRM never changes

How you'll know: Resolved tickets, escalations and refunds don't show up on the account or the deal.

Fix: Add an automation rule that fires a webhook on the status change, and a service that writes the outcome to the right CRM field.

A custom field doesn't map

How you'll know: The app syncs name, email and company, and leaves your plan tier or contract number behind.

Fix: Map that field through the API. Freshdesk addresses custom fields by their internal name, which isn't always the label agents see.

The tool you need isn't listed

How you'll know: A Marketplace search for your order or booking system turns up nothing, or an app that hasn't changed in years.

Fix: A custom app for the sidebar and API calls for the data, built against both systems.

Two apps fight over one field

How you'll know: A contact's phone number or company flips back after someone corrects it.

Fix: Decide which system owns each field, and switch off syncing it from everywhere else.

The build behind a Freshdesk integration that acts

The work leans on two parts of Freshdesk the Marketplace apps don't set up for you. The v2 REST API lets outside code create and update tickets, contacts and companies. Automation rules can call a webhook when a ticket is created or updated, which is how Freshdesk tells another system that something happened.

n-frames builds on both: the resolution of a ticket written onto the CRM account, an onboarding ticket opened with the plan details attached when a deal closes, a private sidebar app for the order system agents keep opening in another tab, and two-way status between Freshdesk and a tool that has no listing at all.

Questions people ask

Does Freshdesk integrate with Salesforce?

Yes, through a Marketplace app that syncs contacts and shows the related Salesforce record beside the ticket. It's built for visibility. Having a ticket's outcome change something in Salesforce, or a closed deal create a ticket, is custom work added on top.

Does Freshdesk integrate with HubSpot?

Yes. HubSpot has a Marketplace app that works much like the Salesforce one, syncing contacts and showing HubSpot data inside Freshdesk. It shows the record, but it won't start actions across the two systems by itself.

Does Freshdesk integrate with Slack?

Yes. The Slack app on the Marketplace posts tickets and updates into a channel and lets agents reply from Slack, which is all many teams need from it.

Can Freshdesk integrate with a tool that has no Marketplace app?

Yes. The Freshdesk REST API handles one side and the other tool's API handles the other, with a custom app if agents need to see its data in the ticket. That's the pairing work n-frames builds when a tool isn't on the Marketplace list.

Can we build our own private Freshdesk app?

Yes. Freshworks' developer kit builds an app that you pack and upload to your own Freshdesk account, rather than submitting it for a Marketplace listing. It can sit in the ticket sidebar and call your other systems.

Is Freshdesk the same as Freshsales for CRM integration purposes?

No. Freshsales is a separate Freshworks product, a sales CRM, while Freshdesk is the help desk. How the two pair up, and how Freshdesk connects to other CRMs, is on our Freshdesk CRM page.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.