Founding offer: 40% off the first payment on selected apps with code FOUNDING40, until 30 November 2026.40% off selected apps’ first payment: FOUNDING40 until 30 Nov. See founding prices

Atesen Software Find your appAll apps
Menu

Can you bulk update more than 30 tickets at once in Freshdesk?

You select tickets in the list, click Bulk Update, and the number thirty keeps coming up. This guide sets out what Freshworks documents, which of its articles disagree, how to find out what your own account allows, and what to do when the job is hundreds or thousands of tickets.

The short answer

Freshworks documents it in two ways. Its older article How to respond to multiple tickets with a common reply, modified 2 June 2023, says Bulk Update on the ticket list view works on a selected set of tickets, with a maximum of 30 tickets per page. The newer article Understand the ticket list view, modified 5 December 2025, describes the same Bulk Update steps without naming a cap, and says the list can show 30, 50 or 100 tickets per page, a setting that is local to the agent and resets each session. Neither article describes selecting tickets across pages.

So the safe reading is to treat the number of tickets you can select on one page as your batch, and to test on a harmless field before you rely on it.

How a bulk update works in the list

  1. Apply filters or use the search bar to find the tickets, and select the tickets you want. The newer article says to click the checkmark next to each ticket, then Bulk Update.
  2. In the Bulk update panel, check the ticket fields to update, provide the details, and click Update.
  3. If you set the Status to closed and mandatory fields are empty, you may get an error. Fill them in and confirm again.

To find your own limit, set the page size to 100 for the session, select the page, open Bulk Update and change a field you do not mind changing, then count how many tickets changed. The articles do not tell you what that count will be, so this test is the only way to know.

When it is thousands: the API

Freshdesk's API reference documents POST /api/v2/tickets/bulk_update, with a mandatory ids array of ticket IDs and no maximum named for it. The properties it lists include group_id, priority, status, type, responder_id, product_id, due_by, fr_due_by, tags and custom_fields.

  • It is a background job. The response gives a job_id and an href to the job. The reference says the update happens in the background and its progress can be checked with the job_id. Its example job response shows only an id and a status, so reading the tickets back afterwards is the safe way to see what changed.
  • You need the IDs first. The search route stops at 300 tickets, so a large set has to be gathered in slices. See Freshdesk API only returns 300 tickets.
  • The rate limit is shared. It is applied per account, and every response reports the calls remaining.

Where these stop

The list route is quick for one page and tedious for ten. The API route is a small project: collecting IDs, batching, pacing, waiting for jobs, reading tickets back and keeping a record of old and new values for the day someone asks what changed.

Option: Saved Bulk Actions (free)

Saved Bulk Actions is a Freshdesk app for agents and administrators who need to change a field across more tickets than a list page or the search screen can hold. You choose a filter and a date range, and the app takes it from there:

  • The whole match set. It enumerates every matching ticket by splitting the range as needed, and previews the count before anything is written.
  • Dry run, then confirmation. The dry run resolves the change against real ticket data and shows the current and proposed value per sampled ticket. Values that are not valid for a field, and fields that are not writable, are rejected before a write is submitted, and the app writes only the fields you selected after an explicit confirmation.
  • Batches, verification and a record. Updates go through the Freshdesk bulk-update endpoint in bounded batches, paced by your account's rate-limit headers. Each ticket's result is read back, and an audit CSV holds the previous value, the new value, the outcome and the time. A long run can be resumed from its position.

Good to know. Throughput depends on your account's rate limits and on Freshdesk, and the app promises no duration for a given volume. Scheduled and recurring runs are not part of it. It is newly listed and has no public installation count or review history yet. It sends no data to Atesen Software; its requests go to your own Freshdesk account.

Disclosure. Atesen Software, which publishes this guide, makes Saved Bulk Actions. The list and API routes above work without it.

Price. Saved Bulk Actions is free, and any Freshdesk account can install it from its Freshworks Marketplace listing.

Install free from the Freshworks Marketplace About Saved Bulk Actions

Which route fits

  • One page of tickets: the list view and Bulk Update.
  • A repeatable job for a developer: the bulk update API.
  • Hundreds or thousands, with a preview and a record of old values: the app above.

Atesen Software is independent. Freshdesk is a trademark of Freshworks Inc., and this page is not affiliated with, sponsored or endorsed by Freshworks. Saved Bulk Actions is an independent app that Freshworks listed on its Marketplace after review. Freshworks articles and the API reference were checked on 22 October 2026; limits can change.

Questions about this guide: support@atesensoftware.com.