Resources · Zapier integration

Freshdesk Zapier integrationAutomate Freshdesk with Zapier.

The Freshdesk Zapier integration gives you 5 triggers, 9 actions and 2 searches. Every trigger is instant: a new ticket, note or contact reaches Zapier as it happens, even on the free plan. Here is what each step does, what it costs and where it trips.

See the 16 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Freshdesk Zapier integration does for you

Freshdesk is a help desk: customer requests from several channels land in one place as tickets, and your agents answer them there. The Freshdesk Zapier integration lets those tickets, notes and contacts start automations on Zapier, and lets Zapier create or update them for you. You set each flow up once and stop copying details between screens.

Three results teams usually build first. Tickets that arrive already briefed: New Ticket starts the Zap and Add Notes to a Ticket drops a private note for the agent, so the context is there before the first reply. A contact base that stays tidy: Create Contact and Create Company turn people from other tools into Freshdesk records, and Find Contact checks first who already exists. A self-service forum fed by real questions: Create Forum Topic publishes a topic in the right category, built from what support learned.

What Zapier does not do here: it cannot delete a ticket or a contact, and there is no action to update a contact or a company once created. The two searches look up a contact by email and a ticket by its number, nothing broader. And no Zap reaches back to tickets opened before it was switched on.

If you are weighing tools, the same app has a Freshdesk n8n integration page and a Freshdesk Make integration page with their own operations.

Vocabulary

Zapier words, in plain English

Eight words come back on every Zapier page. Read them once here and the notes below read faster.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap, such as a new ticket. Once the Zap is on, Zapier waits for that event to happen.
Action
What the Zap does once it has started: the step that writes, sends or creates something for you, like a note on a ticket.
Task
The unit Zapier bills you for: one action your Zap completes successfully. The number on your plan counts those, nothing else.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment it happens.
Filter
A step that lets the Zap continue only when what arrived meets a condition you set, and stops it quietly the rest of the time.
Search step
A step that looks up something already in an app, such as a contact, so the steps after it can use what it found.
Connection
Your Freshdesk account linked to Zapier once, then reused by every step of every Zap that touches Freshdesk.
Cost

What it really costs you

Freshdesk is not a premium app, so it works from the free plan. The bill is counted in tasks, and triggers never count.

  • Tasks on the free plan100 per month
  • Steps on the free plan2: one trigger, one action
  • Premium appNo, works on the free plan
  • Instant triggers5 of 5

A trigger costs nothing, and neither does Zapier waiting for new tickets. Each action that succeeds counts as one task; one that fails is not counted. A Zap that adds a note to every new ticket costs one task per ticket. The free plan gives 100 tasks a month and two-step Zaps only: one trigger, one action. A filter or a search step makes the Zap multi-step, which needs a paid plan, so the ticket-lookup Zaps below are paid territory. All five Freshdesk triggers are instant, so the plan grid never slows them.

Connect

Connect your Freshdesk account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A dialog opens with a search box: type Freshdesk and pick it. You need an existing Freshdesk account before you start.

  2. 02

    Sign in to Freshdesk

    Click Add connection. A new tab opens on Freshdesk: sign in with an account that can see the tickets, contacts and forums you want to automate. If your access is limited, the Zap is limited the same way.

  3. 03

    Grant access and reuse it

    Allow Zapier to use the account. The connection is saved, and every Zap you build with Freshdesk reuses it, so the next one starts without signing in again.

First Zap

Your first Zap: a briefing note on key-account tickets

GoalWhen a key account opens a ticket, the agent finds a private note on it with the handling rules, before they read the request.

  1. 01

    Create the Zap

    Start building a new Zap. Pick Freshdesk as the app that starts the Zap, New Ticket as the event, and select your saved connection.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent tickets of your help desk, so you build the next steps on a real request rather than an empty sample.

  3. 03

    Add the filter

    Click the plus icon and choose Filter. Pick the field that tells key accounts apart, a text rule and the value. This step makes the Zap multi-step, so a paid plan is needed.

  4. 04

    Add the note

    Pick Freshdesk with Add Notes to a Ticket. Map the ticket number from the trigger into Ticket No, write the briefing in Notes, and set Private so customers never see it.

  5. 05

    Test, then publish

    Test the action once and open the ticket in Freshdesk to check the note. Then click Publish: every new key-account ticket gets its briefing from now on.

Triggers

Freshdesk triggers

5 events start a Zap when something happens in Freshdesk, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Ticket

Instant trigger

In Zapier“Triggers when there is a new ticket is created in Freshdesk.”

Each ticket created in your help desk starts the Zap, whatever channel it came through. It is where routing, alerts and first-touch notes begin.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a SaaS support team that wants every new request mirrored to the people who own the account, before an agent picks it up.
Watch out
a Zap on this trigger that also runs Create Ticket opens a ticket, which fires the Zap again, in a loop.
2

New Contact

Instant trigger

In Zapier“Triggers when a new customer is created.”

Fires when a new customer record is created in Freshdesk. It lets your other tools know about a person the moment support meets them.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an online shop whose marketing team wants to hear about every customer who contacted support for the first time.
Watch out
people already in Freshdesk before you publish the Zap are never sent through it.
3

New Ticket Note

Instant trigger

In Zapier“Triggers when a Note is added to a Ticket.”

Reacts each time a note is added to a ticket, by an agent or by another Zap. Notes are where the real story of a ticket gets written, so this trigger follows the work rather than the request.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an agent flags a bug in a note and the product team should hear about it without reading the help desk.
Watch out
a Zap that answers a note with Add Notes to a Ticket writes a note, which sets itself off again.
4

Update Ticket

Instant trigger

In Zapier“Triggers when a Ticket is updated.”

Starts the Zap whenever an existing ticket changes. That covers a lot of ground, so it is usually paired with a filter to keep only the change you care about.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your account managers want to know when a ticket from one of their clients moves, without watching the queue all day.
Watch out
busy tickets change often, and each change that gets through to an action costs a task.
5

Update Contact

Instant trigger

In Zapier“Triggers when a user is updated.”

An edit to a customer record already in Freshdesk starts this one. It is the trigger for keeping other tools in step when support corrects a detail about someone.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
agents often fix email addresses or names while helping a customer, and the billing team needs the corrected version too.
Watch out
run a test first and read what comes back, so your filter targets the change you actually care about.
Actions

Freshdesk actions

Freshdesk gives you 9 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Notes to a Ticket

Action

In Zapier“Add Private or Public notes to a Freshdesk Support Ticket.”

Writes a note on a ticket, either private for the team or public for everyone on the portal. A private note keeps the context inside the team.

When to use it
order details or account history should sit on the ticket before an agent opens it.
Watch out
Ticket No wants the display number, and Private is required, so decide on purpose who sees the note.
2

Create Company

Action

In Zapier“Allows you to create a Company entry in Freshdesk.”

Creates a company entry in Freshdesk from just its name, which gives contacts and tickets an organisation to belong to.

When to use it
a deal is signed in your sales tool and the client's company should exist in the help desk before its people write in.
Watch out
the action creates, it never updates, so a company created twice stays twice.
3

Create Forum

Action

In Zapier“Creates a Forum under a Category.”

Opens a forum inside an existing category, with its type and visibility chosen in the step. It is the middle layer between category and topics.

When to use it
every new customer cohort or region needs its own discussion space under an existing category.
Watch out
the category, name, type and visibility are all required before the step will run.
4

Create Forum Category

Action

In Zapier“Creates a Forum Category.”

Creates a top-level category in your Freshdesk forums from a single name. Categories are the shelves that forums and topics then sit on.

When to use it
each new product line launched in your catalogue gets its own space in the community.
Watch out
a category alone is empty; plan the forums that go under it.
5

Create Forum Topic

Action

In Zapier“Create a new Forum Topic on Freshdesk Forums.”

Publishes a topic inside a forum, with a title and a description. This is where answers from support can become something customers find on their own.

When to use it
a recurring question solved by support should become a public topic others can read.
Watch out
you pick the category first, then the forum, then write the title and description, all four required.
6

Create Ticket

Action

In Zapier“Create a ticket in Freshdesk for your domain.”

Opens a ticket in your help desk from anywhere a Zap can listen, so requests that arrive outside Freshdesk still join the queue.

When to use it
a form on your site or a partner tool collects support requests that agents should handle in Freshdesk.
Watch out
Subject, Email and Description are all required; a run missing one of them stops there.
7

Create Contact

Action

In Zapier“Allows you to create a User/Customer in Freshdesk for your support domain.”

Adds a person to Freshdesk with a name and an email, so agents see who they are dealing with before the first ticket.

When to use it
new customers sign up elsewhere and you want them known to support from day one.
Watch out
run Find Contact first if the person may already exist, so you do not end up with doubles.
8

Update Ticket

Action

In Zapier“Updates a ticket in FreshDesk.”

Changes an existing ticket for you, so a status or detail decided in another tool shows up in Freshdesk without an agent touching it.

When to use it
a fix ships in your issue tracker and the related customer ticket should reflect it straight away.
Watch out
the Zap needs the right ticket to change; Find Ticket by Id is the step that hands it over.
9

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced step that sends a raw request to Freshdesk with the connection you already have, for jobs no ready-made action covers.

When to use it
someone on the team knows the Freshdesk API and needs one call the list above does not offer.
Watch out
requests only reach Freshdesk's own domains, and the required Stop on error choice decides whether a failure halts the Zap.
Searches

Freshdesk searches

2 search steps look for data that already exists in Freshdesk, so a later step can use it.

A search step finds a record that already exists in Freshdesk and hands it to the steps after it. In the editor, searches sit at the bottom of the action list under their own heading. Three settings decide what happens when the lookup does not go to plan.

1

Find Contact

Search

In Zapier“Finds an existing customer or a potential customer that has raised a ticket.”

Looks up a person in Freshdesk from an email address, whether a customer or someone who has only raised a ticket so far. The next steps then work on that exact record.

When to use it
before Create Contact, to check the person is not already in the help desk.
Watch out
Email is the only way in; a name alone will not find anyone.
2

Find Ticket by Id

Search

In Zapier“Find a ticket by ID.”

Fetches one ticket from its number, so a Zap that started elsewhere can work on the right ticket in Freshdesk.

When to use it
an issue in another tool carries the ticket number, and Update Ticket needs the ticket itself.
Watch out
the Ticket Id is required, so the number has to reach the Zap from an earlier step.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create. Freshdesk offers no such variant on Zapier, so you will not see this box on these two searches.
  3. If multiple search results are found?
    Three ways out when several records match: keep the first, which is the default, stop the Zap, or pass them all on.
When it breaks

When it breaks

Zapier attaches one getting-started article to Freshdesk and no list of known issues. The cases below come from how Zaps behave around a help desk.

A help desk is a busy place, and that is exactly what makes a Zap misbehave: tickets change all day, notes pile up, and imports arrive in bulk. Most failures come from that rhythm rather than from Freshdesk. When a run fails, our Zapier troubleshooting page is the place to start.

  • Old tickets are never picked up

    A Zap only reacts to what happens after you publish it. Tickets and contacts already in Freshdesk stay out, and moving that backlog is a separate job.

  • The note that writes itself forever

    A Zap on New Ticket Note that adds a note to the same ticket sets itself off again and again, and the monthly task count drains fast.

  • A bulk import held back

    Importing a large batch of contacts or tickets fires the triggers all at once, and Zapier's flood protection can hold those runs back.

  • A search that stops the Zap

    If Find Contact or Find Ticket by Id comes back empty and the default setting is kept, the Zap stops there and the steps after it never run.

  • Required fields left blank

    Many actions require several fields, from Ticket No to Topic Description. A run where the mapped value is empty fails on that step, and it is not billed.

  • A filter that never lets anything through

    Filter rules are typed: a text rule only works on text, a number rule only on numbers. Pick the wrong type and every ticket stops at the filter.
Need help

Need help automating Freshdesk with Zapier?

A person reads every message.

FAQ

Freshdesk and Zapier: your questions

01Is the Freshdesk Zapier integration free?
Yes, for two-step Zaps. Freshdesk is not a premium app, so the free Zapier plan accepts it, with 100 tasks a month and Zaps of one trigger and one action. A Zap that adds a note to each new ticket fits. The moment you add a filter, a second action or a search step such as Find Contact, the Zap becomes multi-step and needs a paid plan. All five triggers stay instant on the free plan, so nothing waits for a check.
02How many tasks does a Freshdesk Zap use?
One task per successful action, nothing for the trigger. A Zap that writes one note per new ticket costs one task per ticket. A Zap with a search and two actions can cost more per run, because every action that succeeds counts on its own. Failed actions are not counted. The real risk in a help desk is volume: Update Ticket fires on every change, so filter hard before any action that costs a task.
03Is Freshdesk on Zapier real-time?
Yes, for all five triggers. New Ticket, New Contact, New Ticket Note, Update Ticket and Update Contact are instant: Freshdesk tells Zapier the moment something happens, and the Zap starts right away on every plan, the free one included. The grid of 15, 2 and 1 minute checks only applies to polling triggers, and Freshdesk has none. A Zap built on an instant trigger shows a lightning bolt in the editor, so you can confirm it before you publish.
04What does it take to connect Freshdesk to Zapier?
A Freshdesk account that can see what the Zap will touch. In Zapier you open Apps, click + Add connection, pick Freshdesk, sign in in the tab that opens and grant access. The connection is saved and every later Zap reuses it. The Zap inherits that account's reach: tickets, contacts or forums it cannot see stay invisible to the triggers, and actions on them fail. For forum actions, the categories and forums must exist already.
05Why does a Freshdesk forum action stay empty?
Because the dropdowns list what your help desk already holds. Create Forum needs a Forum Category, and Create Forum Topic needs a category and then a forum inside it. If none exist yet, there is nothing to pick and the step cannot be set. Create the structure once, by hand or with Create Forum Category and Create Forum, then build the topic Zap. Name, type, visibility, title and description are required on top.
06What if the Freshdesk operation you need is not on Zapier?
Then API Request (Beta) is the way in. It sends a raw request to Freshdesk with the connection you already have, which reaches parts of the API the ready-made steps skip. It is an advanced step: you set the method and the address, requests only go to Freshdesk's own domains, and the required Stop on error choice decides whether a failure halts the Zap. Without API skills on the team, stay with the listed steps.
07Zapier, Make or n8n for Freshdesk?
Compare on criteria, not on a ranking. On Zapier, all five Freshdesk triggers are instant, two searches cover contacts by email and tickets by number, you pay per successful action, and searches or filters require a paid plan. This site has a Freshdesk page for Make and one for n8n, to set against your own needs. Weigh monthly ticket volume, the number of steps per flow and who will maintain them.
Same platform

Other docs you might need on this stack.

Browse all integrations