Convert DOCX to PDF from URL using ConvertAPI - n8n Workflow

Users requiring high-volume automated document format conversions.
Technical staff needing to integrate third-party APIs into their n8n workflow.
Developers looking for robust n8n templates for file handling.
Anyone utilizing ConvertAPI and seeking an easy way to trigger conversions using an n8n node.

Handling various document formats in an automated environment can be challenging. This specific n8n workflow solves the problem of converting proprietary DOCX files into the more universally readable PDF format instantly using the ConvertAPI service.

This powerful n8n templates removes the need for manual browser-based conversions or complex custom scripts. By leveraging the n8n node dedicated to HTTP requests, the automation handles file fetching, conversion requests, authentication, and local file saving in one seamless flow. Setting up the initial n8n trigger allows for quick testing and later integration into larger systems, making this n8n automation highly valuable for document processing pipelines.

This automation is designed to run on demand, starting with a simple manual n8n trigger:

1. Initialization (n8n Trigger): The workflow begins when the 'When clicking ‘Test workflow’' n8n trigger is manually activated, allowing for immediate testing and configuration adjustment.


2. Configuration: The 'Config' n8n node uses a Set operation to define the input file. Here, the urltofile parameter is set to the public URL of the DOCX document slated for conversion.


3. Conversion Request: The 'HTTP Request' n8n node acts as the conversion engine. It sends a POST request to the ConvertAPI endpoint (/convert/docx/to/pdf). It dynamically attaches the file from the configured URL as a body parameter (file). Crucially, this n8n node is configured to use Query Authentication, which expects the ConvertAPI secret key.


4. Binary Output: The n8n node is configured to expect a file response (application/octet-stream). The resulting binary PDF data is captured.


5. File Saving: Finally, the 'Read/Write Files from Disk' n8n node takes the binary data received from the HTTP request and writes it to the local execution disk, naming the output file document.pdf. This completes the core n8n workflow.

To deploy and utilize this n8n workflow, follow these steps:

1. Import the Workflow: Copy the provided JSON data and import it into your n8n instance via the 'New' menu > 'Import from JSON'.


2. ConvertAPI Credentials Setup: You must have a ConvertAPI account.

1. Link Credentials: Verify that the 'HTTP Request' n8n node is linked to the ConvertAPI credential you just created.


2. Configure Input: Edit the 'Config' n8n node and update the urltofile value to point to the DOCX file you wish to convert.


3. Execution: Click the 'Test workflow' n8n trigger to run the automation.

When clicking ‘Test workflow’ (Manual Trigger): The starting n8n trigger point for on-demand execution and rapid development testing.
Config (Set Node): Essential for defining the variable input. It stores the urltofile string, which is later passed to the HTTP Request n8n node. This allows for easy modification of the source document.
HTTP Request (n8n Node): The core of the conversion process. It utilizes the ConvertAPI endpoint, authenticates using the Query Auth credential, and sends the DOCX URL for remote processing. Key configuration includes using multipart-form-data and expecting a binary file response.
Read/Write Files from Disk (n8n Node): Responsible for the final output. It captures the binary data (the PDF) from the previous n8n node's output and saves it as document.pdf to the local environment where n8n is running.