Conversion job creation

CloudConvert processes files by running them through a conversion job that turns one format into another, such as a document into PDF or an image into a different file type. A Beam agent creates a job when a new file arrives from a connected source, sets the target format the workflow requires, and submits it for processing. It then reads the job status until the file is ready. If a file fails to convert, uses an unsupported format, or the job returns an error, the agent routes the case to a person instead of guessing at a fix.

Job status polling

Each CloudConvert job moves through stages from queued to processing to finished or failed, and a Beam agent reads that status rather than assuming a file is ready. It checks the job at intervals or on a status update, and once the job reports success, it retrieves the converted file for the next step in the workflow. When a job stays queued past the expected time, returns an error, or produces a file that doesn't match the expected type, the agent flags it for a person to check rather than passing along a broken file.

Output delivery to storage

Once a CloudConvert job finishes, the converted file needs to land somewhere useful, whether that's a shared drive, a storage bucket, or back into the system the original file came from. A Beam agent reads the completed job, retrieves the output file, and writes it to the destination the workflow specifies, keeping the file name and format consistent with what downstream steps expect. If the destination is unreachable, already holds a conflicting file, or the delivery step fails, the agent routes the file and the error to a person rather than leaving it stranded.