How to Integrate Freshdesk with Slack (2026)

One quick note before we start. There are a couple of official Freshworks Slack listings on the Marketplace — the Slack app (slack_v2) and Freshdesk for Slack — and they overlap heavily. We'll point both out and tell you which to reach for, rather than pretending there's exactly one app. And to be clear about scope: this is the internal collaboration integration (notifications, creating tickets from Slack, agent alerts), not a way to make Slack your customer-facing chat channel. That's almost certainly what you want.

What the Freshdesk Slack integration actually does

The integration is bidirectional, and it does more than ping a channel. Here's the full feature set so you know what you're turning on:

• Ticket notifications into channels. Ticket creation and update events (status, priority, assignee, notes) post into the public or private Slack channels you choose. Messages are color-coded by priority — Urgent, High, Medium, Low — so a glance tells you what's on fire.
• Direct-message alerts to agents. Instead of (or alongside) channel posts, agents can get a DM from the Freshdesk bot about changes to tickets assigned to them.
• Create tickets from Slack. The /create_fd_ticket slash command turns a Slack conversation or DM into a Freshdesk ticket — pulling in up to the previous 200 messages of context — so internal requests ("the VPN is down") become tracked tickets instead of vanishing in chat.
• Collaborate on tickets in Slack. View and work tickets from Slack and loop teammates in on the conversation, keeping the back-and-forth where your team already is.

The notification side is one-way (Freshdesk → Slack); the slash command is the two-way half (Slack → Freshdesk). Most teams use both, but you can run notification-only if all you want is awareness.

A note on the two official apps

When you search the Freshworks Marketplace, you'll see more than one Slack-related result, and it's worth a second of clarity:

• Slack (listing slack_v2) — the integration most teams install for notifications, agent DMs, and the /create_fd_ticket slash command. This is the one the steps below follow.
• Freshdesk for Slack — a Freshworks-published app (version 1.0, around six years old) for viewing, creating, and collaborating on tickets right from Slack. It supports both Freshdesk and Freshdesk Omni.

Both are official Freshworks apps, not third-party. The practical advice: start from the in-product Marketplace search (Step 1), enable the Slack app it surfaces, and you'll land on the right one. If you want the deeper "work tickets inside Slack" experience, check the Freshdesk for Slack listing too. For the wider catalogue, see our roundup of the best Freshdesk integrations.

Before you start: prerequisites

A few things will save you a mid-setup detour. Per Freshworks' docs, you need:

• A paid Freshdesk plan. The Slack integration is available on Growth, Pro, and Enterprise — not the Free plan. Slack works on all its plans.
• Freshdesk admin access. Installing Marketplace apps and configuring the integration is admin-only.
• A Slack account with admin rights that can access all the channels you want to connect. You authorize the connection with this account during install.

If you're brand new to the platform, our primer on what Freshdesk is covers the basics before you start wiring up integrations.

Step 1 — Install the Slack app from the Marketplace

1. Log in to Freshdesk as an administrator.
2. Click the Marketplace icon in the top-right corner, then open Marketplace Apps.
3. Search for Slack, open the app, and click Install (the app may show as enable).

The Freshworks Marketplace is where you discover and launch the app; the actual authorization and channel mapping happen in the next steps. (You can also install from the Slack side — the Freshdesk app is listed in the Slack Marketplace — but installing from inside Freshdesk is the cleaner path for most admins.)

Step 2 — Authorize your Slack workspace

This is the OAuth handshake that links the two products.

1. After enabling the app, you'll be prompted to sign in to Slack.
2. Use a Slack admin account with access to all the channels you intend to connect — this is the most common stumbling block. Authorizing with a limited account means channels you expect won't be selectable later.
3. Review the permissions and authorize Freshdesk.

Slack returns you to Freshdesk's app configuration screen, where you'll map channels and toggle features.

Step 3 — Map your channels and choose notification options

On the configuration screen, you decide where notifications go and what's switched on:

1. Select your channels. You can add up to 20 public and up to 20 private channels for the helpdesk to post into. Pick deliberately — a firehose channel for all new tickets and a low-noise channel for urgent ones is a common, sane pattern.
2. Allow DM to agent. Toggle this on if you want agents to get a direct message about changes to their tickets, sent by the Freshdesk bot rather than from an admin.
3. Allow slash command. Toggle this on to enable /create_fd_ticket so your team can raise tickets straight from Slack (more on this in Step 5).
4. Click Update to save.

Channel notifications are color-coded by ticket priority, so once this is live a quick scan of the channel tells you severity without opening anything.

Step 4 — Wire notifications to the events you care about

Out of the box, the integration can post ticket creation and update events. To control which tickets post where, drive the notifications from Freshdesk's automation:

1. Go to Admin → Workflows → Automations (the "Ticket updates"/"Ticket creation" rule types).
2. Build or edit a rule with conditions that match the tickets you want surfaced — e.g. Priority is Urgent, or Status is changed to Resolved.
3. Add the Slack action to post to the channel (or DM the agent) you mapped in Step 3.
4. Save and order your rules so the noisy catch-alls don't drown the targeted ones.

Tightly scoped rules are the difference between a channel people watch and a channel people mute. Build one rule per channel-and-event combination rather than firing everything everywhere.

Plan around this when disabling: if you ever turn the Slack app off, remove the Slack actions from your automation rules first. Disabling the app while rules still reference it causes those rules to fail.

Step 5 — Create tickets from Slack with /create_fd_ticket

This is the inbound half, where Slack becomes a real intake source. Once Allow slash command is on (Step 3), each agent authorizes the command once:

1. The agent opens their Freshdesk agent profile/settings and uses the Authorize Slack widget.
2. They complete the OAuth authorization — no manual API token required.
3. From then on, typing /create_fd_ticket in Slack converts the conversation into a Freshdesk ticket, pulling in up to the previous 200 messages for context.

You can also cap how much context is captured by passing a number — /create_fd_ticket <n> (e.g. /create_fd_ticket 70) grabs the last n messages, up to a maximum of 200.

This is perfect for internal asks that would otherwise get lost in a thread. A couple of honest caveats covered fully in Limits below: the conversation body is captured as text; attached files and snippets are preserved as clickable Slack links rather than embedded inline. And slash commands are currently available in the North American region only — confirm availability for your account's region before you rely on it.

Limits to know

The integration is solid but not unlimited. Per Freshworks' docs (June 2026):

• 200-message ceiling. /create_fd_ticket captures only the previous 200 messages of a conversation — fine for most threads, but long-running channels get truncated.
• Body as text, files as links. The conversation body is captured as text; attached files and snippets are preserved as clickable Slack links rather than embedded inline.
• No SLA-violation notifications. The Slack app posts ticket create/update events, but it does not send SLA-breach alerts. If breach alerts matter, handle them separately inside Freshdesk.
• Region limit on slash commands. Slash-command ticket creation is documented as available in the North American region only — verify for your account.
• Channel caps. Up to 20 public + 20 private channels.
• Disable-order gotcha. Remove Slack actions from automation rules before disabling the app (see Step 4).

Troubleshooting

• A channel I want isn't selectable. You likely authorized with a Slack account that doesn't have access to that channel. Re-authorize (Step 2) with a Slack admin account that can see all the channels you need — and for private channels, make sure that account is a member.
• Notifications aren't posting. Check your automation rules (Step 4): over-tight conditions are the usual culprit. Confirm the rule actually has a Slack action pointing at a mapped channel.
• /create_fd_ticket does nothing. Confirm Allow slash command is enabled (Step 3), the agent completed the Authorize Slack OAuth step (Step 5), and you're in a supported region.
• Agents aren't getting DMs. Make sure Allow DM to agent is toggled on, and that the agent's Freshdesk identity is linked to their Slack account.
• A rule started failing after I touched the app. If you disabled or reinstalled the Slack app, automation rules that still reference Slack actions will error — remove or repoint those actions.

Alternatives: Zapier and Make

If you outgrow the native app — you need attachment handling, multi-step routing, conditional logic, or a region the slash command doesn't cover — a no-code automation platform fills the gap:

• Zapier and Make both connect Freshdesk and Slack via triggers and actions. A new Freshdesk ticket can post a richly formatted Slack message; a Slack message or reaction can create or update a Freshdesk ticket; and you can fan either out to hundreds of other apps in the same workflow.
• Make adds a visual, branching workflow builder if your logic is complex; Zapier is the faster path for simple one-step automations.
• The trade-off: these are third-party platforms billed per task/operation, and you maintain the connection yourself — but they're far more flexible than the native app's fixed options.

For the full landscape of what connects to Freshdesk, see the best Freshdesk integrations.

Where an AI layer fits in

Slack notifications are about surfacing tickets to humans faster — a genuine win, but notice the ceiling: the ticket still waits for a person to read the Slack ping, open it, and respond. The integration moves information between tools; it doesn't resolve anything on its own.

That's the layer an AI agent adds. To be clear about what Macha is: it's not a help desk and not a Freshdesk replacement — it runs on top of your existing Freshdesk. Instead of only posting a ticket into Slack for a human to grab, an AI agent can read the incoming request, pull from your connected knowledge and past tickets, and draft or fully resolve the routine ones before anyone gets pinged — escalating to your Slack channel only the cases that genuinely need a person, with context attached.

There's a neat second connection, too: Slack itself can be a knowledge source. The years of answers your team has typed into support and engineering channels are real institutional knowledge — an AI agent can learn from that corpus the same way it learns from your help center, so the resolutions it drafts sound like your team, not a generic bot.

The honest framing: it's another system to configure and supervise, and it's only as good as the knowledge you connect to it. On cost, Macha bills per AI action — any automated step it takes, whether drafting a reply, tagging, routing, or resolving — not per resolution, because most of the work is the steps along the way, not a tidy closed ticket. If a big slice of what hits your Slack channels is repetitive and answerable from existing knowledge, that's the line where notifications alone stop scaling. You can try it free — 7-day free trial, no credit card required.

Frequently asked questions

How do I connect Freshdesk to Slack? Install the official Freshworks Slack app from inside Freshdesk: as an admin, click the Marketplace icon → Marketplace Apps, search Slack, enable it, and authorize with a Slack admin account that can access your channels. Then map up to 20 public and 20 private channels, toggle Allow DM to agent and Allow slash command, and click Update. You need a paid Freshdesk plan (Growth, Pro, or Enterprise) — the Free plan isn't supported.

How do I get Freshdesk ticket notifications in a Slack channel? After installing the app and mapping the channel, use Freshdesk automation rules (Admin → Workflows → Automations) to post ticket creation/update events to that channel. Scope each rule's conditions (e.g. Priority is Urgent) so the channel stays useful. Channel messages are color-coded by priority.

Can I create a Freshdesk ticket from a Slack message? Yes. Enable Allow slash command in the app settings, have each agent authorize the command via the Authorize Slack widget in their Freshdesk profile, then type /create_fd_ticket in Slack. It converts the conversation into a ticket and pulls in up to the previous 200 messages of text. Note: slash commands are documented as available in the North American region only.

Is the Freshdesk Slack integration free? The app itself is provided by Freshworks at no extra charge from the Marketplace, but it requires a paid Freshdesk plan (Growth, Pro, or Enterprise) — it's not available on the Free plan. Slack works on any plan. Always confirm current availability in your own account.

What are the limits of the Freshdesk Slack app? The main ones: ticket creation from Slack captures only the previous 200 messages, where the conversation body is captured as text and attached files and snippets are preserved as clickable Slack links rather than embedded inline; there are no SLA-violation notifications, slash commands are North-America-only, and you can connect up to 20 public + 20 private channels. Also remove Slack actions from automation rules before disabling the app, or those rules will fail.

What's the difference between the two official Slack apps? Both are published by Freshworks. The Slack app (slack_v2) covers notifications, agent DMs, and the /create_fd_ticket slash command — it's what most teams install. Freshdesk for Slack is a separate Freshworks app for viewing, creating, and collaborating on tickets inside Slack, and it supports Freshdesk Omni as well. Start from the in-product Marketplace search; check both listings if you want the deeper in-Slack workflow.

The bottom line

Integrating Freshdesk with Slack is a clear sequence: install the official Freshworks Slack app from the Marketplace, authorize with a Slack admin account, map up to 20 public and 20 private channels, toggle agent DMs and the slash command, then drive notifications through Freshdesk automation rules and let agents raise tickets with /create_fd_ticket. Keep the limits in mind — the 200-message/text-only ceiling on ticket creation, no SLA-breach alerts, and the North-America-only slash command — and reach for Zapier or Make when you need logic the native app can't do. Done right, it turns Slack from a place where requests get lost into a real, two-way extension of your help desk. And when a growing share of what lands in those channels is repetitive and answerable from existing knowledge, that's the point where an AI agent layer like Macha — resolving the routine tickets before anyone gets pinged — starts to earn its place alongside the notifications.

Setup steps and limits verified against Freshworks' official documentation, June 2026. Freshworks revises its apps, plan availability, and regional limits periodically — confirm labels and availability in your own account and on the Freshworks Marketplace before relying on them.