Freshworks · Freshdesk
Saved Bulk Actions
Find every matching ticket, preview the change, then update in verified batches with an audit trail.
Not publicly listed yet
Saved Bulk Actions is in development. It has not been submitted to, approved by, or published on the Freshworks Marketplace, and it cannot be installed by the public today. This page will be updated when that changes.
What it does
Saved Bulk Actions is a Freshdesk application for agents and administrators who need to change a field across more tickets than the Freshdesk search screen can return. It enumerates the full match set, previews the result, applies the update in bounded batches, verifies every ticket individually, and produces an audit CSV of old and new values.
Capabilities
Enumeration beyond the 300-result search cap
The Freshdesk ticket search endpoint stops returning results after a fixed page limit. Saved Bulk Actions splits the requested date range into smaller ranges until each one fits under that cap, deduplicates tickets that appear at a range boundary, and reports any range it cannot split further instead of silently returning a short list.
Preview before you commit
A read-only preview returns how many tickets match the current filter. The preview is a strict projection: when a run is only partially enumerated it reports a partial count and its resume points rather than presenting an incomplete number as a total.
Dry run
The dry run resolves the requested change against real ticket data and shows the current value and the proposed value per sampled ticket. It performs no write.
Freshdesk custom-field resolution
Field labels are resolved against the ticket-field definitions of your own Freshdesk account, including custom fields and their choice lists. Values that are not valid for a field, and fields that are not writable, are rejected before any write is submitted.
Bounded bulk updates
Updates are submitted in batches through the Freshdesk bulk-update endpoint, with pacing driven by the rate-limit headers your account returns and explicit handling of Retry-After responses.
Per-ticket result verification
A bulk submission returns a job, not a per-ticket answer. Saved Bulk Actions reads the job record and records the outcome of each individual ticket, so a partially failed batch is reported as such instead of being assumed successful.
Resumable sharded job storage
Run state is written to the Freshworks application data store in shards, so a long run that exceeds a platform response window can be resumed from its exact position rather than restarted.
Audit CSV
Every run can produce a CSV containing the ticket identifier, the previous value, the new value, the per-ticket outcome and its timestamp — the record an administrator needs after a mass change.
What we do not claim
- It is not listed on the Freshworks Marketplace and has no public installation count, customer list or review history.
- No end-to-end duration is promised for a given ticket volume. Throughput depends on your account's rate limits and on Freshdesk itself.
- It holds no security certification and has not undergone a third-party audit.
- Scheduled and recurring runs are not part of the current feature set.
Marketplace
Freshworks Marketplace: Submission pending — no public listing exists yet.