Resources · Make integration

Freshdesk Make integrationAutomate Freshdesk with Make.

Can your helpdesk update itself while your agents stay on the conversations that matter? The Freshdesk Make integration gives you 31 modules: 3 triggers, 20 actions and 8 searches. This guide shows a support lead how to link the account, build a first scenario and pick the right module.

Try the Freshdesk integration on MakeSee the 31 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Freshdesk Make integration do for your support team?

The Freshdesk Make integration links your helpdesk account to Make, a visual tool where you build a scenario: an automation made of modules, each one a single brick that watches, searches or acts. Tickets, contacts, companies and forum posts can then move between Freshdesk and your other apps without anyone copying them by hand.

A CRM that knows about every new customer. Watch Contacts picks up people added or edited in Freshdesk, and the next module sends them to the tool your sales team lives in. The reverse also works: Create a Contact and Create a Company fill Freshdesk from a signup form.

Tickets opened from anywhere. A bug report in a form, a message in a chat tool, a failed payment alert: Create a Ticket turns each one into a proper ticket, so agents keep a single queue.

Context written straight into the ticket. When Watch Events fires on a ticket, Get a Contact and Search Companies can gather the account details, and Create a Note leaves them for the agent before the first reply.

The listed modules do not cover every corner of Freshdesk, and the doc gives no limits to plan around. For anything missing, Make an API Call reuses the same connection. Freshdesk also has a node in n8n, described on the Freshdesk n8n integration page, and the n8n vs Make comparison helps you place the two tools. New to the editor? The Make training starts from the basics.

Connect

How do you connect your Freshdesk account to Make?

  1. 01

    Copy your Freshdesk API key

    In Freshdesk, click your profile picture in the upper-right corner, open Profile Settings, then press View API key in the right sidebar. Copy the value and keep it somewhere safe: it acts as a password for Make.

  2. 02

    Open the connection window in Make

    Add any Freshdesk module to your scenario and click Create a connection. A connection is your Freshdesk account linked to Make once, then reused by every Freshdesk module. The Connection name field is optional.

  3. 03

    Enter the key and your domain

    Paste the key in API key. In Company name, type only the first part of your helpdesk address: for https://abc.freshdesk.com, that is abc. Click Save, and confirm access if Freshdesk asks you to.

First scenario

Your first scenario: a note on every changed ticket

GoalWhen a ticket is created or updated in Freshdesk, Make writes an internal note on it for the agent.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario. The editor opens on an empty canvas with a big +: click it to place your first module.

  2. 02

    Add Watch Tickets

    Type Freshdesk in the search, choose Watch Tickets and click Create a connection with your API key and domain. This trigger is scheduled: Make checks Freshdesk on the scenario's schedule.

  3. 03

    Add Create a Note

    Click the + to the right of the trigger and pick Create a Note. Map the ticket from the first module so the note lands on the right ticket, then write the text your agents should read.

  4. 04

    Test with Run once

    Update a test ticket in Freshdesk, then click Run once. Each module shows the bundles it received (a bundle is one item passing along, here one ticket). Check that the note appeared in Freshdesk.

  5. 05

    Schedule it and switch it on

    On the first module, the clock sets the schedule: every 15 minutes by default, and never below 15 minutes on the Free plan. Turn the scenario on, and each module run now counts as one operation on your plan.

Triggers

Which Freshdesk triggers can start a scenario?

3 modules start a scenario when something happens in Freshdesk. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Freshdesk as soon as it happens.

Freshdesk1Watch Events

Watch Events

Instant trigger

In Make“Triggers when an event occurs to a ticket.”

Watch Events starts your scenario the moment something happens to a ticket, so a routing rule or a warning to another tool can react while the customer is still waiting. It is the only instant module in the Freshdesk app, which makes it the pick when timing matters.

How it fires
instant, Freshdesk calls Make through a webhook as soon as the event happens.
When to use it
escalating a ticket to an on-call channel the moment its status turns urgent in your helpdesk.
Watch out
nothing arrives until you paste the webhook address from Make into a Freshdesk automation rule.
Freshdesk2Watch Tickets

Watch Tickets

Scheduled trigger

In Make“Triggers when a ticket is created or updated.”

Watch Tickets collects the tickets that were created or updated since the last check and passes each one down the scenario as its own bundle. It needs no setup inside Freshdesk beyond the connection, which makes it the easiest trigger to start with.

How it fires
scheduled, Make checks Freshdesk on the scenario's schedule, every 15 minutes by default.
When to use it
copying ticket details into a reporting sheet where a short wait does no harm.
Watch out
an edit also counts, so one ticket can come back several times; filter on what changed if you only want new ones.
Freshdesk3Watch Contacts

Watch Contacts

Scheduled trigger

In Make“Triggers when a contact is created or updated.”

Watch Contacts looks for customers added or edited in Freshdesk and hands them to the rest of the scenario, one bundle per person. It keeps a CRM, a mailing list or a billing tool aligned with the people your agents talk to.

How it fires
scheduled, Make checks Freshdesk on the scenario's schedule rather than being called by it.
When to use it
an agent fixes a customer's email address and your newsletter tool should get the corrected one.
Watch out
since updates trigger it too, add a search in the destination app before creating anything, or you will pile up duplicates.
Modules

What can each Freshdesk module do?

Freshdesk gives you 28 modules in 6 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Ticket

10 modules
Freshdesk1

Search Tickets by Query

Search

In Make“Searches for tickets by using filter or query.”

Search Tickets by Query finds tickets that match a filter or a query you write, and returns each match as a separate bundle for the following modules to handle.

When to use it
you need a precise slice of the queue, such as open tickets tied to one customer, before acting on them.
Watch out
a search can return zero, one or many tickets, so plan what the next module does when nothing comes back.
Freshdesk2

Search/List Tickets

Search

In Make“Searches for tickets.”

Search/List Tickets pulls a list of tickets from your helpdesk without asking you to write a query. It suits simple pulls where the default listing is enough to feed a report or a cleanup.

When to use it
a board in a spreadsheet should show your tickets and a written query would be overkill.
Watch out
every returned ticket travels as its own bundle, and each later module runs once per bundle, which adds operations.
Freshdesk3

List Ticket Conversations

Search

In Make“Retrieve a list of all conversation in a specified ticket.”

List Ticket Conversations brings back every message exchanged on one ticket, replies and notes, so the whole thread can be read by another tool or archived elsewhere.

When to use it
a closed ticket should be summarized by an AI tool or pasted into the customer file in your CRM.
Watch out
it works on a single ticket, so a previous module has to supply which ticket you mean.
Freshdesk4

List Time Entries

Search

In Make“Retrieves a list of all time entries of a ticket.”

List Time Entries returns the time your agents logged against a given ticket. That turns tracked effort into data you can total, bill or chart outside Freshdesk.

When to use it
a client on a support contract gets billed for hours, and finance wants each entry in its invoicing tool.
Watch out
one bundle comes out per entry, so place an aggregator after it if you need a single total.
Freshdesk5

List Satisfaction Ratings

Search

In Make“Retrieves a list of all satisfaction ratings of a ticket.”

List Satisfaction Ratings fetches the scores customers gave on one ticket. With it, feedback stops living only in Freshdesk and reaches the people who can act on it.

When to use it
a poor rating should reach the team lead in a chat channel along with the ticket link.
Watch out
a ticket with no rating returns nothing, which is normal; add a filter so the rest of the scenario does not fail on empty data.
Freshdesk6

Get a Ticket

Action

In Make“Gets a specified ticket.”

Get a Ticket reads one specific ticket and exposes all its details to the modules that follow. You already know which ticket you want; this module just loads it.

When to use it
another app stored a ticket ID, for example a project card, and you want the current state of that ticket.
Watch out
it needs the exact ticket, so check the ID mapped from the previous module during your Run once test.
Freshdesk7

Create a Ticket

Action

In Make“Creates a new ticket. Note that ticket creation is done only from the perspective of the agent (custom fields that are required for agents should be filled in, etc.).”

Create a Ticket opens a new ticket in Freshdesk from data coming out of another app, so requests that start outside the helpdesk still end up in the same queue.

When to use it
a web form, a chat message or a monitoring alert should become work for your agents.
Watch out
Freshdesk creates it as if an agent did, so custom fields that agents must fill are required here too.
Freshdesk8

Create an Outbound Email

Action

In Make“Creates a new outbound email.”

Create an Outbound Email creates a new outbound email in Freshdesk, straight from your scenario. The Make doc says nothing more about it, so its fields are something you discover in the module itself.

When to use it
another app holds the information and you want Freshdesk, not your own inbox, to be where the email starts.
Watch out
open the module once the connection exists and read its fields before mapping anything; test with Run once on your own address.
Freshdesk9

Update a Ticket

Action

In Make“Updates an existing ticket.”

Update a Ticket changes an existing ticket based on what happened in another tool. Agents stop editing tickets by hand after each outside event.

When to use it
the linked bug is marked fixed in your dev tracker and the ticket should move forward on its own.
Watch out
updating a ticket can also wake up Watch Tickets in another scenario, so avoid loops between the two.
Freshdesk10

Delete a Ticket

Action

In Make“Deletes a ticket.”

Delete a Ticket removes a ticket from your helpdesk. It is useful for clearing out spam or test tickets that another module has already identified.

When to use it
a search has found tickets created by a test form and you want them gone.
Watch out
treat it as final and put a filter just before it, because a wrong mapping could remove real customer tickets.

Conversation

2 modules
Freshdesk11

Create a Reply

Action

In Make“Creates a new reply to a specified ticket.”

Create a Reply posts an answer on a ticket that the customer will see. It suits standard responses you can build safely from data, such as a confirmation or a tracking link.

When to use it
an order lookup in your shop returns a shipping status and the customer should get it without an agent typing it.
Watch out
the customer reads exactly what you mapped, so check an empty field cannot produce a broken sentence.
Freshdesk12

Create a Note

Action

In Make“Create a new note to a specified ticket.”

Create a Note adds a message to a ticket for your team rather than for the customer. It is the safest way to push context from other apps into Freshdesk.

When to use it
the customer's plan or unpaid invoices from your billing tool should sit on the ticket before an agent answers.
Watch out
it targets one ticket, so map the ticket from the trigger or a search, never type a fixed number.

Contact

6 modules
Freshdesk13

Search Contacts

Search

In Make“Searches for contacts by their name or filter parameter.”

Search Contacts looks up people in Freshdesk by name or by a filter. It answers the question every sync starts with: does this person already exist?

When to use it
a new lead arrives from a form and you must decide between Update a Contact and Create a Contact.
Watch out
two customers can share a name, so prefer a filter on a unique value when your data has one.
Freshdesk14

Search/List Contacts

Search

In Make“Searches for contacts.”

Search/List Contacts returns contacts from your helpdesk as a list, without a name or filter to build first. It is the broad pull, where Search Contacts is the targeted one.

When to use it
you are exporting your Freshdesk customers to a spreadsheet or a mailing tool for a one-off cleanup.
Watch out
each contact becomes a bundle and every later module runs once per contact, which adds up in operations.
Freshdesk15

Get a Contact

Action

In Make“Gets a specified contact.”

Get a Contact loads the full record of one person you already have the ID for. The following modules can then reuse everything stored on that record.

When to use it
Watch Events told you a ticket changed and you want details on the requester before notifying sales.
Watch out
if the ID comes from another app, confirm during Run once that it is really a Freshdesk contact ID.
Freshdesk16

Create a Contact

Action

In Make“Creates a new contact.”

Create a Contact adds a new customer to Freshdesk from any other source, so agents recognize the person the first time they write in.

When to use it
someone signs up for your SaaS and should already exist in the helpdesk when they open their first ticket.
Watch out
run Search Contacts before it, or a customer who signs up twice will appear twice in Freshdesk.
Freshdesk17

Update a Contact

Action

In Make“Updates an existing contact.”

Update a Contact edits a person who already exists in Freshdesk, keeping their details in line with the tool that holds the truth, often your CRM.

When to use it
a customer changes phone number in your CRM and agents should see the new one.
Watch out
if Watch Contacts runs in another scenario, this update will fire it too; guard against the two feeding each other.
Freshdesk18

Delete a Contact

Action

In Make“Deletes a contact.”

Delete a Contact removes a person from your helpdesk. It fits cleanup work and data removal requests handled from one central tool.

When to use it
a customer asks to be erased and the request is tracked in a form that should clean Freshdesk as well.
Watch out
consider it irreversible, and add a filter so only the intended contact ID reaches this module.

Company

5 modules
Freshdesk19

Search Companies

Search

In Make“Searches for companies by their name or filter parameter.”

Search Companies finds company records by name or by a filter. It links tickets and contacts to the account they belong to before anything is created.

When to use it
a new deal is won in your CRM and you need to know if the company already has a Freshdesk record.
Watch out
names are written differently across tools, so an empty result does not always mean the company is missing.
Freshdesk20

Get a Company

Action

In Make“Gets a specified company.”

Get a Company reads one company record in full, giving the next modules its details without a search.

When to use it
a contact is linked to a company and your alert should mention the account, not just the person, when an important ticket arrives.
Watch out
it needs the company ID; if you only have a name, use Search Companies instead.
Freshdesk21

Create a Company

Action

In Make“Creates a new company.”

Create a Company adds an organization to Freshdesk, so contacts and tickets from that business can be grouped under one account.

When to use it
a B2B customer signs its contract and the helpdesk should be ready before its users write in.
Watch out
pair it with Search Companies first, because two records for the same client split its ticket history.
Freshdesk22

Update a Company

Action

In Make“Updates an existing company.”

Update a Company edits an existing company in Freshdesk when its details change in the tool your account managers use.

When to use it
a client upgrades its contract in your CRM and agents should see the new tier on its record.
Watch out
map only the fields you mean to change, since a blank value sent by mistake can erase what agents had typed.
Freshdesk23

Delete a Company

Action

In Make“Deletes a company.”

Delete a Company removes an organization record from your helpdesk. It closes the loop when an account ends and your data should follow.

When to use it
a duplicate company was spotted by a search and only one record should stay.
Watch out
there is no undo in the scenario, so test with a dummy company before pointing it at real records.

Forum

3 modules
Freshdesk24

Create a Forum

Action

In Make“Creates a new forum.”

Create a Forum adds a new forum to your Freshdesk community space, giving customers a place to discuss one topic area together.

When to use it
a product line launches in your catalog and its users should get a dedicated space for questions.
Watch out
a public space appears for customers, so review its name and settings in a test run before going live.
Freshdesk25

Create a Forum Category

Action

In Make“Creates a new forum category.”

Create a Forum Category sets up a new category in your community area, the top level you use to sort forums by theme.

When to use it
you open a new region or a new product family and want its forums grouped from day one.
Watch out
categories rarely change, so this module fits a scenario started by a clear event, not one that runs over and over.
Freshdesk26

Create a Forum Topic

Action

In Make“Creates a new forum topic.”

Create a Forum Topic starts a new discussion thread inside a forum, turning an announcement or a common question into a public post.

When to use it
release notes published in your product tool should open a topic where customers can react.
Watch out
the topic is visible to your community, so check the mapped title and text with Run once before switching on.

Other

2 modules
Freshdesk27

Get an Agent

Action

In Make“Gets a specified agent.”

Get an Agent reads the profile of one of your support agents, so a message sent to another tool can name the right person.

When to use it
a ticket is assigned and your chat alert should say who owns it, not just show an ID.
Watch out
it expects the agent ID, usually mapped from a ticket loaded by an earlier module.
Freshdesk28

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any part of the Freshdesk API that the listed modules do not cover, with the connection you already set up.

When to use it
you need a Freshdesk feature that has no ready-made module in Make.
Watch out
you describe the request yourself, so keep the Freshdesk API documentation open and test the call with Run once.
Need help

Need help automating Freshdesk with Make?

A person reads every message.

FAQ

Freshdesk and Make: common questions

01Is the Freshdesk Make integration free?
Yes, Freshdesk is a standard app in Make, so you can use it on the Free plan. That plan has real limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run on one bundle. Your Freshdesk subscription is a separate matter.
02What does it take to connect Freshdesk to Make?
You need a Freshdesk account, its API key and your helpdesk domain. The key sits in Freshdesk under your profile picture, Profile Settings, then View API key. In Make, click Create a connection on any Freshdesk module, paste the key, and type only the subdomain in Company name: abc for abc.freshdesk.com. Save, then confirm access if asked. For the instant Watch Events trigger, you also create a webhook and paste its address into a Freshdesk automation rule.
03Do Freshdesk triggers in Make work in real time?
Only one does. Watch Events is instant: Freshdesk calls Make through a webhook as soon as something happens to a ticket, once you add the webhook address to an automation rule. Watch Tickets and Watch Contacts are scheduled: Make checks Freshdesk on the scenario's schedule, every 15 minutes by default. On the Free plan the gap cannot go below 15 minutes, on paid plans it can drop to 1 minute. Pick Watch Events when a delay would hurt the customer.
04What if the Freshdesk module you need is missing?
Use Make an API Call. It sends any request to the Freshdesk API with the connection you already have, so you are not stuck with the 31 listed modules. You write the request yourself, which means reading the Freshdesk API docs and testing with Run once. The Make doc for Freshdesk gives no numeric limits, so there is no documented ceiling to plan around. If a request still fails, check the API key and the domain entered in Company name first.
05Make or n8n: which one fits Freshdesk?
It depends on where your other automations already run, since both tools connect to Freshdesk. In Make, you get 31 ready modules covering tickets, conversations, contacts, companies and forums, plus Make an API Call for the rest, all behind a single API key connection. n8n offers its own Freshdesk node, described on a separate page of this site. Nothing here ranks one above the other: compare the modules you need on each side and keep your support flows in one tool.
Same platform

Other docs you might need on this stack.

Browse all integrations