Greenhouse Bulk Candidate Status Updater

WHAT IT DOES

Greenhouse Bulk Candidate Status Updater solves a common recruiting workflow challenge: moving multiple Greenhouse candidates through the hiring pipeline is tedious when done one at a time. While Greenhouse allows individual candidate editing, there is no native way to update the status of many candidates simultaneously. This tool reads your current Greenhouse candidate list or pipeline page, detects all visible candidates, and displays them in a scrollable checklist with candidate names, current stages, jobs, and application dates. You select the candidates you want to move, choose a target stage from a dropdown that detects all available pipeline stages, and optionally add a note that will be added to each candidate. The tool then processes each selected candidate sequentially through Greenhouse's Harvest API, updating the application stage while preserving all other candidate data. A preview shows your selection before updating, and progress tracking shows each candidate as it's processed.

WHERE IT RUNS

This extension panel runs directly inside your browser as an overlay on any Greenhouse candidate list or pipeline page. It works on candidate views, pipeline stages, and search results. The tool detects candidates from the page's DOM and uses Greenhouse's Harvest API (via GM_xmlhttpRequest) for status updates. It requires no additional API keys beyond your existing authenticated session — the tool extracts your API key from the page.

HOW TO USE

After installing the BotGentz extension and activating Greenhouse Bulk Candidate Status Updater, navigate to any Greenhouse candidate list or pipeline page. Click the extension icon in your browser toolbar to open the panel. The tool automatically detects all candidates displayed on the current page. Each candidate appears with their name, current stage, job, and application date alongside a checkbox. Use the "Select All" toggle or individually check candidates. Next, choose a target stage from the dropdown — the tool detects all available stages in the current pipeline. Optionally, enable the "Add note to candidates" toggle and enter a note to be added to each candidate during the status change. The preview section shows how many candidates are selected, the target stage, and the note if provided. Finally, click "Update Statuses." The tool processes each candidate with a 500ms delay, showing progress as each candidate is updated. A notification appears when all candidates are processed.

TECHNICAL OPERATION — Greenhouse Harvest API Status Updates with Optional Notes

This tool uses Greenhouse's Harvest API to perform status updates reliably. It first extracts the user's API key from the page (using regex to find `api_key` in scripts or meta tags), then constructs a PATCH request to `/v1/applications/{applicationId}` with a payload containing the `stage_id` of the target stage. When the note toggle is enabled, the tool includes a `notes` field with the user's message. The API approach is more reliable than DOM-based simulation because it works independently of Greenhouse's UI structure, supports proper error handling with HTTP status codes, and can handle large numbers of candidates efficiently without triggering UI event delays. A 500ms delay between updates prevents rate limiting and API congestion. The tool includes candidate job and application date information in the display for better context.

THE PANEL

The extension panel is fully draggable and remembers its position per site session. It snaps to the nearest edge of the browser viewport when dragged within 50 pixels of any side. You can collapse the panel to a compact title bar using the minimize button, preserving your selection state. The panel resizes vertically by dragging the bottom edge. Press the Escape key to close the panel instantly without losing your candidate selection. The preview updates in real-time as you select candidates, choose stages, or add notes.

PLEASE NOTE

This tool requires the free BotGentz extension to function. The script uses Greenhouse's Harvest API and requires your session to be authenticated. It does not store, transmit, or log any candidate data, stage information, or user activity. All API requests are made locally from your browser session. The tool relies on extracting your API key from the page, which may expire if your session times out. Greenhouse may update its DOM structure over time, which could affect candidate detection; we monitor and release compatibility updates as needed. Status changes are permanent — review the preview carefully before confirming. Adding notes to candidates will create internal notes visible to recruiting team members. Export formats include CSV and JSON for maximum compatibility with analysis tools.