How can I configure a CloudConvert node in my n8n workflow?

Below is some guidance for configuring a CloudConvert node in your n8n workflow based on the example provided. Note that CloudConvert isn’t one of the core n8n nodes (like the Convert to File node), so you’ll need to set it up as a custom node (or install it via npm if it isn’t already available).

Steps to Set Up the CloudConvert Node in n8n

1. Install and Enable the Node

   If you haven’t already, install the CloudConvert node package for n8n. This is usually done via npm in your n8n installation. Check the CloudConvert GitHub repository for the installation instructions.

2. Provide Your API Key

   When you add the CloudConvert node to your workflow, there should be a place to enter your CloudConvert API key. This key is used for authentication when calling the CloudConvert API.

3. Configure the Tasks

   The provided workflow snippet shows how you might create a job with three tasks – one to import, one to convert, and one to export. In the node’s configuration panel in n8n, you’ll enter values corresponding to these tasks. For example:

   • Task 1 (Import):
     Set the operation to import a file from a URL. You’ll need the input URL to the file (e.g., your example file PDF).

   • Task 2 (Convert):
     Configure this task to take the output of the import task as input. Choose the conversion settings (for instance, setting the output format to JPG).

   • Task 3 (Export):
     Set this task to export the results from the conversion task so that you obtain the file in its new format.

4. Mapping Fields in n8n

   Instead of writing code directly as in your example, in n8n you typically use the node’s UI to map these values. For example, you might have fields labeled “Operation,” “Input,” “Output Format” and so on. Consult the node’s documentation or the GitHub readme for details on each parameter.

5. Testing the Workflow

   After you’ve configured all the tasks, test the workflow. Confirm the import downloads the file from the URL, the conversion is done as expected, and the export provides you with a link or binary file that you can use downstream in your workflow.

Example Outline in n8n Context

Although you’ll configure tasks via the UI, here’s an outline reflecting the job structure from your code sample:

JSCopied
// This pseudocode represents the job structure.
// In n8n, you configure these steps via the node’s fields.
{
  tasks: {
    import: {
      operation: 'url',
      url: 'https://example.com/file.pdf'
    },
    convert: {
      operation: 'convert',
      input: 'import',       // Use output from the import task.
      output_format: 'jpg'
    },
    export: {
      operation: 'export',
      input: 'convert'       // Use output from the convert task.
    }
  }
}

In the CloudConvert node’s UI, you should see corresponding fields for these operations. Make sure you map the outputs properly so that the export task knows where to pull the file from.

Final Note

If you run into issues with a particular parameter or the node’s setup, double-check the CloudConvert node docs on GitHub and any issues posted by others in the community forum. This node’s functionality isn’t documented as part of the core nodes, so the community and the CloudConvert GitHub repository are good resources for additional guidance.

Feel free to ask if you have more questions about configuring nodes in n8n!