CloudConvert n8n integrationAutomate CloudConvert with n8n.

Runs a custom ffmpeg, ImageMagick or GraphicsMagick command on the input file, which covers anything the ready made operations do not.

• Command: the base command to execute, for example ffmpeg or convert; the supported commands are listed in the CloudConvert docs.
• Engine: FFmpeg, ImageMagick or GraphicsMagick.
• Arguments: input files are read from /input/{taskName}/ and output must be written to /output/.
• Capture Console Output: returns the console output in the result, which is how you debug a failing command.

Stamps a watermark onto a PDF, an image or a video, and returns the marked copy while the original stays untouched.

• Text: the text used as watermark, often an expression such as {{ $json.state }}.
• Font Size: required, and worth testing on the largest page format you handle.
• Image URL: a PNG, JPG or SVG to use instead of text, paired with Watermark Image.
• Opacity: a percentage, where 100 means fully visible.
• Vertical Position and Horizontal Position: top, center or bottom, and left, center or right.

The core operation: one file in, the same content in another format out.

• Output Format: the format to convert to, picked from the dropdown.
• Input File Name: the filename with its extension, which is how CloudConvert knows what it received.
• Binary Property: the binary field carrying the file to convert.
• Additional Options: a JSON dictionary of extra options added to the converting task; the CloudConvert job builder generates them for you.

Bundles several files into a single archive, so the workflow carries one item instead of eight.

• Output Format: the archive format, ZIP, RAR or another supported one.
• Input File Contents: the text content uploaded when the file is not binary.
• Binary Input Data: switch it on to take the files from a binary field instead.
• Input File Name: the name with extension, which becomes the entry inside the archive.

Produces a small preview image of a file, useful when a list needs to show something before the file is opened.

• Width and Height: the thumbnail size in pixels.
• Fit: Max keeps the image inside the box without enlarging a smaller one, Crop fills the box and cuts the excess, Scale forces both dimensions.
• Output Format: the image format returned.
• Binary Property: the field holding the source file.

Compresses a file to reduce its size without changing its format, which matters when the next step has an attachment ceiling.

• Binary Property: the binary field holding the file to compress.
• Binary Input Data: on means the file comes from that binary field, off means CloudConvert uses Input File Contents.
• Additional Options: a JSON dictionary of options added to the converting task, generated with the CloudConvert job builder.

Reads the metadata CloudConvert can extract from a file and returns it as JSON, so the next node can branch on it.

• Input File Name: the filename including extension.
• Binary Property: the binary field containing the file to inspect.
• Binary Input Data: leave it on when the file arrives from a previous node rather than as text.

Writes metadata into the file and returns the updated copy, the mirror image of reading it.

• Metadata: a JSON dictionary of keys and values to write, for example Title, Author, Creator or Producer.
• Input File Contents: the text content when the file is uploaded directly.
• Binary Property: the field holding the file to rewrite.

Adds a text layer over a scanned PDF, which turns a picture of a page into something you can search and copy from.

• Languages: a comma separated list of language codes, for example eng,deu.
• Auto Orient: detects and corrects page orientation before the OCR pass.
• Binary Property: the binary field holding the scanned PDF.

Rewrites a PDF into the archival PDF/A family, the format record keeping rules usually ask for.

• Conformance Level: PDF/A-1B, PDF/A-2B or PDF/A-3B.
• Binary Property: the field carrying the PDF to convert.
• Binary Input Data: on when the PDF comes from the previous node as binary data.

Removes the protection from a password protected PDF and returns a readable copy for the rest of the workflow.

• Password: the password of the encrypted file, usually pulled from a credential store rather than typed in the node.
• Input File Contents: the text content when the file is uploaded as text.
• Binary Property: the binary field holding the locked PDF.

Locks a PDF and, on top of the password, decides what a reader is allowed to do with it.

• Set Password: the password required to open the file.
• Set Owner Password: the owner password for permissions; with it, every protection can be removed again.
• Allow Print and Allow Modify: the permitted levels, for example full and form.
• Allow Extract and Allow Accessibility: copying content, and screen reader support.

Pulls selected pages out of a PDF and returns them as a new file, leaving the source document alone.

• Pages: single pages or ranges, for example 1,2,5-7; numbering starts at 1.
• Binary Property: the field holding the PDF to cut.
• Binary Input Data: on when the PDF is the binary output of an earlier node.

Combines several files into a single PDF, in the order the items reach the node. No parameter is required on this one, which makes it the simplest operation of the node and the easiest to slot at the end of a branch that has collected files from different places.

Turns single pages or every page of a PDF, which fixes documents that were fed into the scanner the wrong way round.

• Rotation: the angle to apply, for example +90, -90 or 180.
• Pages: the pages or ranges to rotate, such as 1,2,5-7, with numbering starting at 1.
• Binary Property: the binary field holding the file.

Breaks a PDF into one file per page, so a batch document becomes a list of items the workflow can loop over.

• Binary Property: the field holding the PDF to split.
• Binary Input Data: on to take the document from that binary field.
• Input File Contents: the text content, for the upload path instead.

Renders a live web page and returns it as a PDF, a JPG or a PNG screenshot. This is the only operation that starts from a URL rather than a file.

• URL: the address of the page to capture.
• Output Format: PDF for a document, JPG or PNG for a screenshot.
• Additional Options: a JSON dictionary of extra options for the task, built with the CloudConvert job builder.