Job finished
Receive the signed CloudConvert job.finished event when a job finishes. This workflow does not create or start the conversion.
Workflow template
Log completed CloudConvert jobs in Google Sheets. Each signed Job finished event adds the job ID, tag, status and completion time to your selected worksheet.
How it works
Receive the signed CloudConvert job.finished event when a job finishes. This workflow does not create or start the conversion.
Append the job ID, tag, status and ended_at timestamp to columns A:D of an existing worksheet. RAW input keeps formula-looking values as text.
The result
The row records job-level completion metadata. It does not save converted files, download URLs or a separate row for every task in the job.
| Job ID | Tag | Status | Completion time |
|---|---|---|---|
| 00000000-0000-4000-8000-000000000001 | Example conversion | finished | 2026-01-01T00:00:00Z |
Completion time comes from job.ended_at. Conversion outputs remain in CloudConvert or their configured export destination.
Before activation
Connect CloudConvert and authorize access to the account’s jobs and webhook settings. Select that connected account for Job finished and wait for its signed event subscription to connect.
Connect Google Sheets and use Browse to choose a spreadsheet and worksheet. Reserve columns A:D for job ID, tag, status and completion time; add optional headers in that order.
Activate before completing a small test conversion in CloudConvert. Check the resulting job.finished event and compare its four mapped values with the new row. CloudConvert conversion credits and account limits apply.
Completion logging only. Creating a CloudConvert job is asynchronous and is not the same as finishing it. This template listens for job.finished; job creation and job.failed events are not logged by this trigger.
No file transfer or worksheet creation. The prepared action appends four values to an existing worksheet. It does not create the spreadsheet, download converted files or copy expiring output URLs into the row.
Append-only records. RAW input prevents incoming tags from becoming spreadsheet formulas. The workflow has no job-ID lookup to update an existing row, so manual reruns can append the same job again.
No. It listens for the signed job.finished event from a job you create elsewhere. There is no Create job or conversion action in this template.
The selected trigger is job.finished. A separate job.failed event is outside this recipe and needs a workflow for that event.
No. The prepared row contains job ID, tag, status and ended_at. Files and output download URLs are not copied to Google Sheets.
No. Choose an existing worksheet and optionally add four headers in the example order. Each run appends A:D without finding or replacing an earlier row for that job.