Pinch Voice Translation Status

What it's for

This is the small sibling in the Pinch Voice Translation pack, and it exists for one honest reason: the main node blocks for up to thirty minutes polling a cloud dubbing job, and when things go sideways you want a way to check in without re-running the whole job. PinchVoiceTranslationStatus is that way. Feed it a job_id and it tells you where the job stands - and if it finished, hands you the download links.

It's also the natural partner for a workflow that already ran once. If you ever lose the output file or close the console, the job_id is your receipt, and this node is how you cash it in.

What it does

One call to GET /api/dubbing/jobs/{job_id} with your API key. It returns the job status, and when the status is completed it makes a second call to the result endpoint to pull the actual download URL and subtitle URLs. No uploads, no polling loop, no waiting - it's a single status check you can fire any time, for a job that might have been created hours ago.

Inputs and outputs

Two required inputs, both plain strings: api_key (same key you use on the main node) and job_id.

Four outputs:

• status - queued, processing, completed, failed, and the rest of whatever the API reports
• output_url - direct download link once the job is done
• subtitles_original_url and subtitles_translated_url - SRT download links

The gotcha: links, not files

Here's the asymmetry worth knowing. The main dubbing node downloads the finished file to ComfyUI/output/ for you. This node does not - it returns URLs, and you have to fetch them yourself (browser, curl, or a download node). Pinch says output URLs are valid for 48 hours, so don't sit on them. If the job just completed, grab the file while the link is warm.

Install

Same pack, same one-time install:

cd ComfyUI/custom_nodes/
git clone https://github.com/pinch-eng/comfyui-pinch-voice-translation
pip install -r comfyui-pinch-voice-translation/requirements.txt

Or search "Pinch Voice Translation" in ComfyUI Manager. The only dependency is requests; there are no models to download.

When you'd actually use it

• The main node hit its 30-minute timeout - it returns the job_id precisely so you can hand it to this node.
• A workflow crashed mid-poll and you restarted; the job is still running server-side, and you want to know if it survived.
• You want a cheap "did it finish yet?" check wired into a larger workflow.

Honest take: if your jobs complete in the usual few minutes, you'll rarely touch this node. It's a recovery tool, not a daily driver - keep it on the canvas for the day a long dub makes you glad it exists.