Package Exports
- n8n-nodes-cloudconvert
- n8n-nodes-cloudconvert/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (n8n-nodes-cloudconvert) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
n8n-nodes-cloudconvert
This is an n8n community node. It lets you use CloudConvert in your n8n workflows.
CloudConvert is an online service providing all sorts of file processing / transformation features, that can be used to convert or tweak PDFs, images, ebooks, audio, documents, etc...
n8n is a fair-code licensed workflow automation platform.
Installation
Operations
Credentials
Compatibility
Usage
Resources
Installation
Follow the installation guide in the n8n community nodes documentation.
Operations
- Jobs:
- Create (sync or async)
- List
- Get One
- Delete
Credentials
Authentication relies on an API key that you can generate from your CloudConvert dashboard. Both live and sandbox environments are supported. You will likely need the task.read
and task.write
scopes.
Compatibility
Tested on n8n 0.206.1
Usage
Sandbox Usage
Note that it's strongly recommended to perform your tests against the sandbox environment, which needs to be enabled first and which uses a separate API key. Note that:
- Separate credentials should be created for the live and sandbox environments.
- The main limitation of the sandbox environment is that all imported files need to be whitelisted first before processing (based on the file's
md5
hash).
Job Definitions
The most useful operation is to send new conversion jobs to CloudConvert. The definition of each job is done in JSON format, and the CloudConvert Job Builder UI can be used to build the job definition visually and interactively, and copy-paste the resulting JSON.
This node provides convenience methods to manipulate files, notably:
- There's an option to automatically upload binary attachments to the job (using an
import/base64
task - this task will be automatically added to the job definition, you won't need to specify it). - There's an option to automatically download any resulting exported file (only the
export/url
tasks are supported).
Here's a sample workflow / node definition:
Resources
- n8n community nodes documentation
- CloudConvert API Docs
- The CloudConvert Visual Job Builder which can be used to build the job definition JSON
TODO
- Trigger node, handling webhooks