Freshworks · Freshservice
Saved Bulk Actions
Update any number of Freshservice tickets after a preview, and roll back if needed.
- Works with Freshservice
- Marketplace Freshworks Marketplace
Coming soon
Under review by Freshworks Marketplace
Saved Bulk Actions for Freshservice is under review by Freshworks Marketplace. It has not been approved or listed, so it cannot be installed by the public today.
Coming soon toFreshworks Marketplace
What it does
Saved Bulk Actions for Freshservice is an application for Freshservice administrators who need to change a field across hundreds of tickets at once. It finds every matching ticket, shows the before and after value for a sample, applies the update one ticket at a time under the platform rate limit, records every original value before it is changed, and can roll a job back from inside the application.
Capabilities
Up to 2,000 tickets per job
Saved Bulk Actions finds every ticket that matches your filter and date range, in any status, and works through up to 2,000 of them in one resumable job, so a large change does not turn into page-by-page clicking or a one-off API script.
Filters you already know
Status, priority, urgency, impact and type as chips; agent and group from your account's own lists; tags; created, updated or due date range; workspace. An advanced box accepts Freshservice filter syntax for anything else.
Preview and dry run
Before anything is written you see how many tickets match and, for a sample, the current value and the proposed value of every field you are changing. Tickets that already hold the target value are skipped and counted separately.
Names, not IDs
Groups, agents, departments and workspaces are shown by name. Field values are checked against your own account's ticket form fields, so a value that is not valid for a field is rejected before any write.
Original values recorded first
The previous value of every field is stored before the ticket is updated. A run can be paused, and if the tab closes the app offers to continue the unfinished job from its exact position. No ticket is written twice.
Roll back from inside the app
A finished job can be undone. Each ticket is read first; if someone changed it after the job, it is reported as a conflict and left untouched instead of being overwritten.
Saved presets
Recurring clean-ups — reassigning a leaver's tickets, closing stale requests — can be saved with their filter and change and run again in a few clicks.
Access control
Only the agents listed at installation get bulk updates, undo, preset changes and job deletion in the application; everyone else can preview. The list is a workflow safeguard, not a security boundary: a Freshworks server function cannot verify which agent sends a request, so every change runs with the permissions of the agent whose API key is installed.
Audit CSV
Every job produces a CSV with the ticket, workspace, field, old value, new value, outcome, the Freshservice error message for any failure, and a timestamp.
Questions
Where does Saved Bulk Actions run?
The application runs on the Freshworks Developer Platform. Its interface and its server-side functions run on infrastructure operated by Freshworks. Atesen Software does not operate a server or a database for it.
What does Saved Bulk Actions connect to?
Every outbound request is addressed to your own Freshservice account at your-subdomain.freshservice.com. The application sends no data to Atesen Software, to an analytics provider or to any other third party.
How do I get help with Saved Bulk Actions?
Support for Saved Bulk Actions for Freshservice is provided by email in English and Turkish.
Email support@atesensoftware.com. We aim to acknowledge every support email within two business days (Europe/Istanbul).
What we do not claim
- It is under review by Freshworks Marketplace, not approved, listed or publicly installable. Public installation, customer and review counts are not verified. Our implementation checks used a simulated Freshservice account only; real customer operation is not verified.
- No completion time is promised. Updates are sent one ticket at a time and paced under the Freshworks app limit of 50 requests per minute.
- It holds no security certification and has not undergone a third-party audit.
- Notes, time entries, scheduled runs and a job history screen are not part of the current feature set.
- No comparison with Freshservice's own bulk edit is claimed; its limits were not measured for this page.
- The allowed-agents list is not a security boundary: the application cannot verify which agent sends a request. Every change runs with the permissions of the agent whose API key is installed, whoever opens the application; Freshservice enforces those permissions on every request.
Marketplace
Freshworks Marketplace: Under review — not approved, not listed, and not installable by the public.
Coming soon toFreshworks Marketplace