Resources · Zapier integration

Freshservice Zapier integrationAutomate Freshservice with Zapier.

The Freshservice Zapier integration gives you 4 triggers and 5 actions. All four triggers are instant, so tickets and users reach your Zap as soon as they change, even on the free plan. Here is what each step does, what it costs and where it breaks.

See the 9 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Freshservice Zapier integration actually does

Freshservice is a cloud helpdesk for IT teams, built around the ITIL way of running a service desk: tickets, requesters, approvals. Zapier links it to the rest of your tools, so a ticket or a new user in Freshservice can set something off elsewhere, and the other way round, without anyone retyping.

Three outcomes cover most needs. Tickets that open themselves: a form, an alert or a message in another app becomes a Freshservice ticket through Create Ticket, with the requester's email attached. Approvals that do not wait in an inbox: New Ticket starts the Zap and Request Ticket Approval sends the request to the right approver. A user directory that stays in step: New User and Update User tell your HR or onboarding tool when someone joins or changes, and Create Requester adds people coming from elsewhere.

What it does not do matters too. Zapier offers no search step for Freshservice, so a Zap cannot look up an existing ticket or user on its own: it only works with what the trigger brings. It cannot close, assign or delete a ticket through a ready-made action either. For anything beyond the five actions, the API Request step is the only door.

Comparing platforms? The same app is covered on our Freshservice n8n integration and Freshservice Make integration pages, built the same way.

Vocabulary

Zapier words you will meet on this page

Six terms, in plain words. After this, the page uses them as is.

Zap
The automation you build: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in Freshservice that starts the Zap, such as a new ticket. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once started: the step that creates a ticket, adds a note or sends something to another app.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan's quota counts these and nothing else.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant one is reported by the app itself the moment it happens.
Filter
A step that only lets the Zap go on when what arrived meets the condition you set, and stops it quietly otherwise.
Cost

What a Freshservice Zap really costs you

The trigger never costs a task, and with Freshservice there is no checking to pay for either: the app calls Zapier itself. Only an action that goes through is counted.

  • TriggerNo task
  • Each successful actionOne task
  • Free plan100 tasks a month, two-step Zaps
  • Reserved to paid plansNo, works on Free

In a Zap with several actions, each successful one counts on its own, so a three-action Zap uses three tasks per run. A failed action is not counted. The free plan gives you 100 tasks a month and two-step Zaps only: one trigger, one action. A filter makes the Zap multi-step, which needs a paid plan. Freshservice is not on Zapier's list of apps reserved to paid plans, so it works from the free one. For a wider look at the tool itself, see our Zapier review.

Connect

Connect your Freshservice account to Zapier

  1. 01

    Open your connections

    In Zapier, go to the Apps page and click + Add connection. Type Freshservice in the dialog and pick it. You need a Freshservice account, plus access to any tickets or users you do not own and want the Zap to touch.

  2. 02

    Sign in to Freshservice

    Click Add connection. A tab opens on the Freshservice side. Sign in with the account the Zap should act as: every ticket, note or requester it creates will come from that account.

  3. 03

    Grant access

    Freshservice asks you to let Zapier into the account. Accept and the tab closes. The connection now sits on your Apps page, and every Freshservice step in every Zap reuses it.

First Zap

Build your first Freshservice Zap

GoalWhen a new ticket asks for access to something, the Zap sends it straight for approval.

  1. 01

    Create the Zap

    Start a new Zap and pick Freshservice with New Ticket as the trigger. Choose your Freshservice connection. The lightning bolt in the editor shows this trigger is instant.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent tickets of the account. Pick one with a real subject, so you can map its fields in the next steps.

  3. 03

    Add the filter

    From the plus icon, add a Filter. Pick the subject field, a text rule that checks it contains a word, and type access. This step makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the approval

    Add the action Request Ticket Approval. Map the ticket from the trigger, choose the approval type and the approver, both required.

  5. 05

    Test and publish

    Test the action once and check the request shows up in Freshservice. Then click Publish: from now on, each new access request goes for approval on its own.

Triggers

Freshservice triggers: what can start your Zap

4 events start a Zap when something happens in Freshservice, and 4 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 Freshservice.”

Starts the Zap each time a ticket is opened in your helpdesk. The ticket's details travel with it to the next steps.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
the on-call engineer wants a ping in the team chat for every new incident, without keeping the helpdesk open all day.
Watch out
tickets raised before the Zap was published are never picked up.
2

New User

Instant trigger

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

Fires when someone new is added to Freshservice, so whatever comes next (an account in another tool, a welcome message) can follow without a manual handover.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
HR wants each new person in the helpdesk mirrored into the onboarding checklist they already track elsewhere.
Watch out
a bulk import of users can arrive as one big batch, which Zapier's flood protection may hold back.
3

Updated Ticket

Instant trigger

In Zapier“Triggers when a Ticket is updated.”

Reacts whenever an existing ticket changes. It is the trigger to watch when what happens to a ticket after it is opened matters more than its creation.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
account managers want to know when a ticket from one of their clients moves, so they can follow up before the client calls.
Watch out
a Zap that writes back into the same ticket, for example with Add Notes to a Ticket, risks setting this trigger off again and looping; test it before you publish.
4

Update User

Instant trigger

In Zapier“Triggers when a user is updated.”

Catches every change made to a user's record in Freshservice, which keeps other tools aligned when someone moves team or changes details.

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 directory or payroll tool should pick up updated details as soon as IT edits them in the helpdesk.
Watch out
each edit starts a run, so a filter on a paid plan keeps your task count under control.
Actions

Freshservice actions: what your Zap can do

Freshservice gives you 5 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 Freshservice Support Ticket.”

Writes a note on an existing ticket, found by its number. You choose whether it stays private to agents or shows to everyone on the portal.

When to use it
the outcome of a step in another tool should be logged on the ticket where agents look first.
Watch out
Private is a required choice, so pick it on purpose.
2

Create Ticket

Action

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

Opens a ticket in your Freshservice helpdesk with a subject, a description, a status and the requester's email, all required.

When to use it
a monitoring alert or a web form should land in the service desk queue instead of someone's inbox.
Watch out
without a requester email the step fails, so map one from the trigger.
3

Create Requester

Action

In Zapier“Allows you to create a Requester in Freshservice for your support domain.”

Adds a requester, someone who can raise tickets, to your support domain from just a first name and a primary email.

When to use it
new hires entered in your HR tool should be able to log tickets from their first morning.
Watch out
First Name and Primary Email are both required, so map them from fields that are always filled.
4

Request Ticket Approval

Action

In Zapier“Creates a ticket approval request”

Sends an approval request on a ticket to the approver you name, with the approval type you choose.

When to use it
software or access requests must be signed off by a manager before IT does anything.
Watch out
both the approval type and the approver are required, so the step fails on a run where either one is missing.
5

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 your own request to Freshservice through the connection you already set up, for the jobs no ready-made action covers.

When to use it
you need a Freshservice call that none of the four other actions makes, and someone on the team is comfortable reading the Freshservice documentation.
Watch out
it only reaches Freshservice addresses, and Stop on error decides whether a failure halts the Zap.
When it breaks

When a Freshservice Zap breaks

Four situations to know before you rely on a Freshservice Zap.

Zapier attaches no help article to Freshservice, so what follows comes from how triggers and plans work on Zapier in general. Read it before you publish, and keep our Zapier troubleshooting page for the day a run fails.

  • Old tickets never show up

    A Zap reacts only to what happens after you publish it. Tickets and users that already existed are not picked up; moving that backlog is a separate job.

  • A ticket Zap that triggers itself

    Updated Ticket watches ticket changes. If the same Zap then writes into that ticket, with Add Notes to a Ticket for instance, the write may count as an update and set the Zap off again, burning tasks fast. Treat it as a risk and test.

  • A bulk import gets held back

    When a large batch of users or tickets arrives at once after an import or a migration, Zapier's flood protection can hold the trigger back instead of running every item.

  • The filter step is locked

    On the free plan a Zap stops at one trigger and one action. A filter, or a second action, makes it multi-step and asks for a paid plan.
Need help

Need help automating Freshservice with Zapier?

A person reads every message.

FAQ

Freshservice Zapier integration: your questions

01Is the Freshservice Zapier integration free?
Yes, Freshservice is not one of the apps Zapier reserves to paid plans, so you can connect it on the free plan. That plan gives you 100 tasks a month and two-step Zaps: one trigger, one action. Adding a filter or a second action turns the Zap into a multi-step one, which needs a paid plan. The good news is that all four Freshservice triggers are instant, so the free plan does not slow them down the way it slows polling triggers on other apps.
02How many tasks does a Freshservice Zap use?
One task for each action that succeeds, on each run. The trigger costs nothing. So a Zap that adds a note to every new ticket costs one task per ticket, and a Zap that also posts in a chat tool costs two. An action that fails is not counted. Keep an eye on Update User and Updated Ticket: they start a run on every edit, so they can use up 100 tasks a month faster than you expect if the helpdesk is busy.
03Does Freshservice trigger Zaps in real time?
Yes. All four triggers, New Ticket, New User, Updated Ticket and Update User, are instant: Freshservice tells Zapier the moment the event happens, and the Zap starts at once on any plan, the free one included. The polling interval grid of Zapier plans (15 minutes on Free, 2 on Professional, 1 on Team and Enterprise) does not apply to them. In the editor, a Zap built on one of these triggers shows a lightning bolt.
04What does it take to connect Freshservice to Zapier?
A Freshservice account, plus access to any tickets or users you do not own and want the Zap to read or change. You connect it from the Apps page in Zapier: add a connection, pick Freshservice, sign in in the tab that opens and grant access. Choose the account carefully, since every ticket, note and requester the Zap creates will come from it. It also needs to see the approvers and requesters your actions will name.
05Why does Create Ticket fail in a Freshservice Zap?
One cause to check first is an empty required field. Create Ticket needs four things on every run: a subject, a description, a ticket status and the requester's email. If the trigger app sometimes sends a record without an email, that run fails. The fix is to map the email from a field that is always filled, or to put a filter in front, on a paid plan, so only complete records reach the action.
06What if the Freshservice action you need is not in the list?
Then the API Request (Beta) action is the way. It sends a request of your choice to Freshservice while reusing your existing connection, so there is no extra login to manage. That is the route for any call the five ready-made actions do not make. It only reaches Freshservice addresses, and its Stop on error setting decides whether a failed call stops the Zap. You will need the Freshservice documentation to write the request.
07Zapier, Make or n8n for Freshservice?
There is no single winner, only criteria. On Zapier, Freshservice exposes 9 operations: 4 triggers, all of them instant, 5 actions and no search step, and it is not reserved to paid plans, so a two-step Zap runs on the free plan at full trigger speed. Set that list against the Freshservice operations each of the other two tools offers, check which ones your use case needs, and weigh the tool your IT team already knows. The one that covers your exact event and action is the right pick.
Same platform

Other docs you might need on this stack.

Browse all integrations