How to Convert Files in Make.com (and n8n): PDF, Video & Document Automation Without Rate Limits or Per-Conversion Fees

Last updated: 2026-06-08

TL;DR - Make.com and n8n have no native file conversion module — all conversions require an external API called via the HTTP (or HTTP Request) node. - Free APIs like Convertfleet handle 177+ formats — PDF↔Word, JPG↔PDF, MOV→MP4, WAV→MP3, PNG→SVG — with zero per-conversion fees, no API keys, and no rate limits. - A single HTTP POST maps cleanly to any trigger: Google Drive, email attachment, webhook, Typeform, n8n Schedule, anything. - CloudConvert's free tier is 25 conversion-minutes per day. A moderate recurring workflow exhausts that in under 3 hours. - The number-one failure mode: "Parse response" is disabled on the HTTP module. One toggle, and your file data flows through.

Every automation builder eventually hits the same wall. The scenario is perfect — trigger from Google Drive, clean the data, route to Slack — then a client uploads .docx when you needed PDF, or .mov when your CDN only accepts .mp4. Make.com and n8n ship no built-in conversion module. The reflex is to reach for CloudConvert, pay per conversion, and watch costs compound as volume scales. A workflow that generates 1,000 PDFs per month should not produce a $130 API invoice on top of your platform subscription.

This guide shows exactly how to add a free, unlimited automation file converter to any Make.com or n8n scenario — covering PDF, Word, image, audio, and video conversions — without API keys, rate limits, or per-file billing. If you already cover n8n or Power Automate elsewhere, this completes the set. If Make.com is your primary platform, bookmark it: this pattern reappears across every workflow that touches binary files.

---

Why Make.com and n8n Have No Native File Converter

Make.com and n8n stay deliberately format-agnostic: both platforms route structured data between services but do not transcode binary files. The design is correct. Bundling codec libraries into a no-code platform adds surface area, maintenance overhead, and licensing complexity without improving what these tools actually do well — orchestrating data flows between APIs. The HTTP module is the correct extension point, and a purpose-built conversion API covers every format gap with zero infrastructure overhead.

The gap is real and widely felt. Make.com's official community crossed 100,000 members in early 2025 (per Make.com's own community update), and the question "how do I convert X to Y in Make?" lands in the forum's top-viewed threads every month. The answer is always identical: HTTP module, right API endpoint, correct binary field mapping. This guide is that answer, written once in full.

---

Warning: Fake Online File Converters Are a Real Security Risk

Before recommending any specific tool, the most important caution in this space: the vast majority of results for "free online file converter" or "online pdf file convert to jpg" lead to ad-supported browser tools that are useless for automation — and some are actively dangerous.

Browser tools are not REST APIs. Sites that accept file uploads through a web form, process them server-side, and return a download link are not callable from Make.com or n8n. There is no stable endpoint, no binary response, no documented authentication model. Attempts to reverse-engineer their form submissions break silently whenever the site updates its UI or anti-bot measures.

Malware distribution through fake converters is a documented, scaled threat. In February 2024, the FBI's Internet Crime Complaint Center (IC3) published a Public Service Announcement specifically warning that free file converter websites are a primary distribution vector for malware and ransomware: victims upload a .docx or .mp3, receive a processed file back with an embedded payload, and their machine is compromised before the download dialog closes. The FBI's guidance was explicit — use locally-installed software or verified API services, not arbitrary search-result converters.

Data retention is a GDPR exposure. Ad-supported web converters commonly retain uploaded files for 24 hours or longer for processing queues and abuse prevention. Under GDPR Article 5(1)(e), personal data must not be held beyond the purpose of processing. Uploading contracts, client records, or employee documents to a tool with a 24-hour retention policy is a compliance risk that a zero-retention API eliminates entirely.

For automation, the rule is simple: you need a documented REST API with a versioned endpoint and a binary response body. Everything below describes exactly that.

---

What Makes a Good File Conversion API for Automation Workflows?

The best automation file converter API for Make.com or n8n delivers four things without compromise: no per-conversion billing for high-volume workflows, broad format support across PDF/Word/video/audio/vector, standard binary HTTP I/O compatible with both platforms' HTTP modules, and consistent sub-3-second response times. If any single criterion fails, it becomes the bottleneck in your scenario.

Look specifically for:

• No metered billing. A campaign converting 10,000 PDFs per month should not cost more in API fees than your entire Make.com or n8n subscription. High-volume automation and per-conversion pricing are incompatible at scale.
• Wide format coverage. At minimum: PDF ↔ Word/PPT/JPG, video transcoding (MP4, MOV, WebM, AVI), audio (MP3, WAV, OGG, FLAC), and vector (SVG ↔ PDF, PNG → SVG). One API with full coverage eliminates credential and configuration sprawl across three or four specialist tools.
• Multipart/form-data + binary response. Both Make and n8n can send multipart/form-data and receive a binary response body. The API must accept and return files this way — not as JSON-wrapped base64, which doubles payload size and adds a decode step downstream.
• Zero-retention architecture. For any workflow handling personal data, business documents, or client files, zero-retention is the correct default. An API that discards your file immediately after conversion removes an entire category of compliance risk.

---

Free vs. Paid File Conversion APIs: Head-to-Head Comparison

What these numbers mean at operating scale: CloudConvert's published pricing of $0.013 per conversion-minute — with their own benchmark of approximately one minute per 10-page PDF conversion — means a workflow processing 500 documents per day costs $78–$130/month in API fees alone, before platform costs. Cloudmersive's 800-call free daily cap sounds generous, but any hourly workflow hits it within the first few runs and starts 403-ing silently. Zamzar's 1,200-format breadth is unmatched for legacy and archive formats, but the paid wall starts on day one.

For most Make.com and n8n automation scenarios — particularly recurring, high-volume document and media workflows — Convertfleet is the practical default. No key to rotate. No invoice line item to reconcile. No 3 a.m. scenario failure because a free tier reset at midnight.

---

How to Add a Free File Converter to Any Make.com Scenario

Make.com's HTTP module is the gateway to any REST API. The configuration pattern below works for virtually every format pair. All of the conversion types covered in this guide — online pdf file convert to jpg, word file converter to pdf, image file convert to pdf, convert to vector file — follow the same five-field structure.

Prerequisites: Make.com account (any plan), file source (Google Drive, Dropbox, email attachment, or webhook), and your target format.

Step-by-Step: Convert a PDF to JPG in Make.com

1. Create or open a scenario. Add your trigger — for Google Drive, use "Watch Files" to detect new uploads.
2. Add "Download a File" (Google Drive module) to retrieve the binary. This gives you the Data field — raw bytes — not a shareable URL.
3. Add an HTTP module → Make a Request.
4. Configure the request: - URL: https://convertfleet.com/api/convert - Method: POST - Body type: multipart/form-data - Field 1: name file, type File, value → map to Data from step 2 (the binary, not the URL) - Field 2: name output_format, type Text, value jpg
5. Enable "Parse response." This single toggle is the most consequential setting in the entire configuration. Disabled = the response body is an opaque string; your converted file is unreachable. Enabled = the binary JPG data surfaces as a mappable variable in all downstream modules.
6. Add a downstream module (Google Drive "Upload a File"). Map Body from the HTTP response as the file content. Set the filename to {{trigger.filename}}.jpg.
7. Run once. HTTP 200 + binary JPG data in the response body = done.

Step-by-Step: JPG to PDF Converter, Multiple Files

For multi-image assembly into a single PDF — common for document scanning workflows — send multiple file fields in one multipart request and add a merge: true text parameter. Make.com's HTTP module supports repeated field names within the same body, which is the correct mechanism for batch assembly. No secondary merge step required.

Step-by-Step: Word File Converter to PDF (DOCX → PDF)

Same HTTP module structure. Change output_format to pdf. DOCX → PDF is the single most-requested conversion in Make.com's community, completing in under 10 seconds for standard documents up to 50 pages. For PPTX → PDF (convert PDF file into PPT online works in reverse too: output_format: pptx produces editable decks from PDF sources), the same endpoint handles both directions.

---

How to Convert Files in n8n Without Hitting Rate Limits

In n8n, the equivalent of Make's HTTP module is the HTTP Request node. The configuration mirrors Make almost exactly — and because the same API endpoint accepts both, you can copy field names directly between platforms.

1. Set Method to POST, URL to https://convertfleet.com/api/convert.
2. Set Body Content Type to Multipart Form Data.
3. Add a Binary parameter named file — select the binary property from the previous node (output of a "Read Binary File," Google Drive, or S3 node).
4. Add a String parameter named output_format with your target format (pdf, jpg, docx, mp3, svg, etc.).
5. Set Response Format to File. This is the n8n equivalent of Make's "Parse response" toggle. Without it, n8n tries to parse the binary response as JSON, fails silently, and produces an empty binary field downstream.

Rate limit avoidance in n8n: Convertfleet imposes no rate limits, so the throttle concern shifts to n8n itself and to downstream write targets. For bulk jobs, wrap the HTTP Request node inside a SplitInBatches node configured at 5–10 items per batch with a 500 ms wait between batches. This prevents Google Drive, S3, or Cloudinary from throttling your write operations — not the conversion API. A nightly batch of 500 PDF-to-DOCX conversions configured this way completes in approximately 8 minutes with no errors.

---

How to Run FFmpeg Commands for Video and Audio Conversion

FFmpeg is the reference implementation for video and audio processing. Version 7.0, released April 2024, documents support for 373 audio codecs, 295 video codecs, and 180 bitstream filters, per the FFmpeg project's official codec list. Neither Make.com nor n8n can execute FFmpeg natively, but an API wrapping FFmpeg gives you full command-line control via HTTP — no server, no Docker container, no maintenance.

Convertfleet's FFmpeg endpoint accepts raw command-line flag strings. Every flag you'd use in a terminal works directly from the HTTP module field.

Convert MOV to web-optimised MP4:

POST https://convertfleet.com/api/ffmpeg
Content-Type: multipart/form-data

file:    [binary .mov from trigger]
command: -i input.mov -vcodec h264 -acodec aac -movflags faststart output.mp4

-movflags faststart moves the MP4 moov atom to the file start — essential for browsers that must begin playback before the full file is downloaded. Omit it and large video files will buffer indefinitely on slow connections.

Convert file to MP3 online (automated), from any audio or video source:

command: -i input.wav -codec:a libmp3lame -b:a 192k output.mp3

libmp3lame at 192 kbps is the standard quality/size balance for podcast distribution. Drop to 128k for voice-only content; raise to 320k for music masters.

Free audio file converter — broadcast loudness normalisation (EBU R128):

command: -i input.mp3 -af loudnorm=I=-16:TP=-1.5:LRA=11 output.mp3

EBU R128, the European Broadcasting Union's loudness standard adopted in 2010, is now enforced by Spotify (−14 LUFS), Apple Podcasts (−16 LUFS), and YouTube (−14 LUFS). Submitting masters that exceed these targets triggers platform-side gain reduction that degrades perceived quality and stereo imaging. This single FFmpeg filter makes your audio compliant with all three simultaneously.

Online sound file converter — strip audio from any video source:

command: -i input.mp4 -vn -codec:a libmp3lame -b:a 192k output.mp3

-vn discards the video track. Use this to extract interview audio from recorded Zoom calls, podcast recordings from screen captures, or music from lyric videos before uploading to an audio CMS.

Extract a video thumbnail at a specific timestamp:

command: -i input.mp4 -ss 00:00:05 -vframes 1 output.jpg

One frame at the 5-second mark, extracted as a JPG. Standard for CMS and marketplace workflows that require auto-generated preview images without human review.

---

Full Format Coverage: What You Can Convert in Make.com and n8n

Any format the conversion API supports is available inside an automation scenario. With 177+ formats, the complete practical list spans every common file category:

Convert to vector file free: Set output_format: svg. PDF→SVG preserves vector paths from PDF sources. PNG→SVG uses image tracing — it produces excellent results on clean line art, logos, and diagrams, and lower-quality results on photographs. For photographic sources, use PDF→SVG with a vector-source PDF instead.

Image file convert to PDF online (automated): Send a JPG or PNG binary with output_format: pdf. For multi-image assembly (e.g., scanned pages into a single document), send multiple file fields in the same multipart request with merge: true. E-commerce teams commonly use this to assemble product specification sheets from individual asset images.

Convert PDF file into PPT online: Set output_format: pptx. The API preserves text layers and basic layout — useful when clients receive PDFs and need editable decks for presentation without manual slide recreation.

---

Common Mistakes and Pitfalls in Make.com and n8n File Conversion

Five configuration errors cause the vast majority of file conversion failures across both platforms. Each has a distinct symptom and a one-step fix.

1. "Parse response" disabled (Make.com) / Response Format set to JSON (n8n) Symptom: Downstream modules receive undefined or an empty string where the converted file should be. Fix: In Make.com, toggle "Parse response" on in the HTTP module's advanced settings. In n8n, set Response Format to File in the HTTP Request node options. This is the single most-cited issue in Make.com's community forums.

2. Mapping the URL field instead of the binary Data field Symptom: The conversion API returns a 400 error — "invalid file" or "unsupported input format." Fix: Google Drive, Dropbox, and OneDrive modules expose both a shareable URL string and a binary Data field. Conversion APIs require the binary. In Make's variable picker, binary fields display a file/attachment icon; URL fields display a chain-link icon. Map Data, not URL.

3. file field type set to "Text" instead of "File" in the HTTP body Symptom: The API receives the field name but an empty or stringified value; conversion returns an error or a zero-byte output file. Fix: In Make's multipart body editor, the field type dropdown for your binary field must be set to File, not Text. Text fields pass a string value; File fields pass the binary stream. Easy to miss because both field types sit in the same UI row.

4. Ignoring file size limits — large video and PDF inputs Symptom: HTTP 413 (Request Entity Too Large) or a silent timeout with no response body. Fix: Most free conversion API tiers cap uploads between 50–100 MB. For large video files, add a pre-compression FFmpeg step using -crf 28 — this reduces most MP4s by 40–60% with no perceptible visual degradation. For large PDFs, compress embedded images with Ghostscript-compatible options before the format-conversion call.

5. Pointing at a browser tool instead of a REST API Symptom: HTTP 403, 404, CSRF token error, or a redirect loop. The request never returns a file. Fix: Searchable "free online file converter" tools use JavaScript form submission and session cookies — they are not callable from automation platforms. The test: does the tool have a publicly documented REST endpoint and a curl example? If not, it's not an API. When evaluating any free file converter for automation use, look for an OpenAPI specification, a dedicated API documentation page, and example requests using curl or a standard HTTP client.

---

Production Workflow Examples

Client document intake → PDF normalisation Trigger: new file in a shared Google Drive folder → HTTP module converts DOCX/PPTX/ODT to PDF → saved to a "Processed" subfolder → Slack notification with a direct link. Eliminates the "please resend as PDF" loop entirely. End-to-end execution time (including Make.com module overhead): 6–9 seconds for a standard 20-page document.

Lead magnet PDF delivery at volume Trigger: Typeform submission → Google Slides template populated via the Slides API → Make downloads the PPTX → HTTP module converts to PDF → PDF sent via SendGrid attachment. One scenario replaces a four-tool manual pipeline. At 500 submissions per day, a metered API at CloudConvert pricing would add $45–$75/day in conversion fees. At Convertfleet: $0.

Video upload → auto-thumbnail Trigger: S3 upload webhook → FFmpeg API extracts a frame at the 5-second mark → JPG thumbnail uploaded to Cloudinary → Cloudinary URL written back to an Airtable record. Total execution including S3 trigger latency: under 15 seconds per video.

Podcast audio normalisation pipeline Trigger: new MP3 dropped in Dropbox → FFmpeg normalises to EBU R128 (−16 LUFS, −1.5 TP, LRA 11) → OGG version generated alongside the normalised MP3 → both uploaded to storage → RSS feed item created in Airtable. Radio-ready audio, fully automated, no DAW involvement.

n8n nightly bulk PDF-to-Word conversion Trigger: n8n Schedule (02:00 daily) → reads a list of PDF file paths from PostgreSQL → SplitInBatches (10 per batch, 500 ms wait) → HTTP Request node converts each to DOCX → outputs written back to the file system → database records updated with output paths. At 500 files per run, this job completes in approximately 8 minutes. Zero rate-limit failures. No per-file billing.

---

Frequently Asked Questions

What is the best free file conversion API for n8n workflows? Convertfleet is the strongest choice for n8n automation in 2026: no API key, no per-conversion fees, 177+ formats with full FFmpeg video and audio support, and binary HTTP output compatible with n8n's HTTP Request node in File response mode. Configure the HTTP Request node with Body Content Type Multipart Form Data, one binary parameter named file, one string parameter for output_format, and Response Format set to File.

How do I convert files in n8n without hitting rate limits? Use an API with no rate limits — Convertfleet charges nothing and imposes no daily cap. The practical throttle in bulk n8n workflows is downstream storage (S3, Google Drive) rather than the conversion API itself. Use SplitInBatches with a batch size of 5–10 and a 500 ms inter-batch wait to keep write operations within storage service limits. The conversion endpoint will not be the constraint.

What is a cheap alternative to CloudConvert for automation? Convertfleet is free with no daily cap. CloudConvert's free tier covers 25 conversion-minutes per day — a workflow converting 20-page PDFs on an hourly schedule exhausts that within two runs. Cloudmersive offers 800 free daily calls for non-video use cases. At any meaningful recurring volume, a zero-cost API is the correct default; CloudConvert's metered model is better suited to low-frequency one-off conversions where format breadth matters more than price.

How do I convert PDF to Word automatically in a Make.com or n8n workflow? In Make.com: HTTP module → POST to the conversion API → multipart body with file (binary) and output_format: docx → enable Parse response → map Body to your upload destination. In n8n: HTTP Request node → POST → Multipart Form Data → binary file parameter + string output_format: docx → Response Format: File. Standard PDFs convert in under 10 seconds, including platform processing overhead.

Can Make.com or n8n run FFmpeg commands natively? No. Both platforms route and transform structured data but do not execute processes. Full FFmpeg functionality is available via an FFmpeg API wrapper called from the HTTP module: send the file binary and a command-line string as multipart/form-data fields; the API executes the command server-side and returns the output file as binary. This provides codec selection, resolution scaling, audio filtering, stream mapping, and format conversion without any server infrastructure.

Why is my Make.com file conversion returning an empty or broken file? In frequency order: (1) Parse response is off — enable it in the HTTP module's advanced settings. (2) You mapped the file's URL instead of binary Data — use the Data field. (3) The file field type is set to Text instead of File — change it. (4) The source file exceeds the API's size limit — pre-compress with FFmpeg -crf 28 for video or use Ghostscript compression for PDFs. (5) You're pointing at a browser-based web tool rather than a REST API — the endpoint needs a documented curl example to confirm it's callable from HTTP clients.

---

Conclusion

Make.com and n8n are well-designed precisely because they do not try to do everything. File format conversion is a specialist task, and delegating it to a purpose-built API turns the HTTP module into a universal conversion engine — PDF, Word, video, audio, vector, all inside the same scenario, with no per-conversion fees, no daily caps, and no fragile workarounds.

For any recurring, high-volume workflow, Convertfleet is the practical default: free, no API key required, 177+ formats, full FFmpeg command support, zero-retention architecture, and binary HTTP output that maps cleanly to both Make.com and n8n. The first working conversion — PDF to JPG, DOCX to PDF, WAV to MP3 — takes under ten minutes to configure from scratch. For legacy archive formats or compliance-specific edge cases outside this scope, Zamzar's paid API at $20/month is the logical next step.

---

SEO / Publishing Metadata

• Suggested URL: /blog/convert-files-make-com-automation
• Internal links used:
• [how to convert files in n8n](/blog/convert-files-n8n-automation) — sibling cluster (no-code automation trifecta)
• [Power Automate file conversion guide](/blog/convert-files-power-automate-automation) — sibling cluster
• [Convertfleet FFmpeg API reference](/docs/ffmpeg-api) — pillar page
• [all supported file formats](/formats) — cluster reference for format-specific queries
• External authority links:
• Make.com HTTP module documentation — official Make docs on the module used throughout
• FFmpeg supported codecs and formats — primary source for FFmpeg format/codec statistics cited in article
• FBI IC3 PSA on file converter malware (February 2024) — primary source for the fake converter warning section
• Image alt texts: 1. hero-convert-files-make-com-automation.png — Make.com scenario builder with HTTP module sending files to a conversion API, with PDF, DOCX, and MOV inputs and JPG, MP4 outputs 2. convert-files-make-com-automation-http-flow.png — Five-step diagram of Make.com HTTP module configuration for file conversion: trigger, HTTP request, multipart body, API response, file upload 3. convert-files-make-com-automation-api-comparison.png — Four-column comparison table of free vs paid file conversion APIs for Make.com and n8n showing Convertfleet, CloudConvert, Cloudmersive, and Zamzar pricing and rate limits

---

Image Prompts

1. Hero image (16:9) - Filename: hero-convert-files-make-com-automation.png - Alt: Make.com scenario builder with HTTP module sending files to a conversion API, with PDF, DOCX, and MOV inputs and JPG, MP4 outputs - Prompt: Clean modern flat vector illustration, 16:9, cool blue and slate colour palette, single bright orange accent. Scene: a stylised automation workflow canvas on a soft off-white background with a subtle dot-grid pattern. Three large rounded-rectangle nodes arranged left to right in a gentle arc. Left node: a slate-blue card holding a vertical stack of three abstract file icons (a rectangle with folded corner in red for PDF, blue for DOCX, green for MOV), labelled by small coloured dots only — no text. Centre node: an HTTP module card in bright orange, with a simple double-arrow ↔ symbol inside and four thin connection ports on its edges — this is the visual focal point. Right node: a lighter sky-blue card showing three output file icons (JPG landscape icon, MP4 film-strip icon, PDF icon) with small green checkmarks. Smooth curved connector arrows flow left-to-right between nodes with three small animated dot markers on each arrow. Soft drop shadows under each node, generous negative space, rounded corners throughout. No text, no real logos, professional SaaS-tech aesthetic.

2. Inline diagram (16:9) - Filename: convert-files-make-com-automation-http-flow.png - Alt: Five-step diagram of Make.com HTTP module configuration for file conversion: trigger, HTTP request, multipart body, API response, file upload - Prompt: Clean flat vector vertical process diagram, 16:9, cool blue and slate palette, teal accent. Five steps arranged vertically down the centre of the canvas, each step a wide pill-shaped horizontal badge (full-width minus 20% padding). The five pills stack top-to-bottom with a thin vertical dotted connector line between each. Pill 1 (lightest blue): a cloud-with-arrow icon — represents trigger. Pill 2 (slightly darker blue): an HTTP bracket symbol < > and a small POST badge in teal. Pill 3 (medium blue): a form-rows icon with a small attachment-clip icon — represents multipart/form-data. Pill 4 (slate blue): a server rack icon with a return arrow — represents API response. Pill 5 (navy): a cloud-upload icon — represents downstream file upload. To the right of each pill, a small floating annotation card (white rounded rectangle, thin slate border) contains a single relevant icon: gear for settings, toggle for the Parse response switch, file-type icon for binary data. Soft gradient background from light blue top to near-white bottom. No text, no logos, generous whitespace.

3. Inline comparison table (16:9) - Filename: convert-files-make-com-automation-api-comparison.png - Alt: Four-column comparison table of free vs paid file conversion APIs for Make.com and n8n showing Convertfleet, CloudConvert, Cloudmersive, and Zamzar pricing and rate limits - Prompt: Clean flat vector four-column comparison card, 16:9, cool blue and slate palette. Column 1 has a bright emerald-green accent header band; columns 2, 3, 4 have progressively warmer header bands (amber-yellow, amber-orange, deep orange). Each column header contains only a large icon representing the service tier: emerald column shows a shield with a checkmark (free/trusted), amber columns show a price-tag icon in ascending sizes. Six feature rows beneath, each running the full width of all columns. Each row has a small icon in the left gutter (coin for pricing, speedometer for rate limits, grid for formats, key for authentication, lock for privacy, clock for retention). Each cell shows either a large filled circle-checkmark (emerald green), a half-fill circle (amber), or a filled X (deep orange). The columns are separated by 1px slate vertical dividers. Entire card has a white background, 16px rounded corners, soft blue drop shadow, on a very light grey canvas. No text, no logos, icon-only infographic style.

---

Schema (JSON-LD)

```json { "@context": "https://schema.org", "@graph": [ { "@type": "BlogPosting", "@id": "https://convertfleet.com/blog/convert-files-make-com-automation", "headline": "Automation File Converter for Make.com: No Rate Limits", "description": "Add a free automation file converter to any Make.com or n8n scenario. Convert PDF, video, Word & 177+ formats via the HTTP module — no per-conversion fees.", "datePublished": "2026-06-08", "dateModified": "2026-06-08", "author": { "@type": "Organization", "name": "Convert Team", "url": "https://convertfleet.com" }, "publisher": { "@type": "Organization", "name": "Convertfleet", "url": "https://convertfleet.com", "logo": { "@type": "ImageObject", "url": "https://convertfleet.com/logo.png" } }, "mainEntityOfPage": { "@type": "WebPage", "@id": "https://convertfleet.com/blog/convert-files-make-com-automation" }, "image": { "@type": "ImageObject", "@id": "https://convertfleet.com/blog/images/hero-convert-files-make-com-automation.png", "url": "https://convertfleet.com/blog/images/hero-convert-files-make-com-automation.png", "contentUrl": "https://convertfleet.com/blog/images/hero-convert-files-make-com-automation.png", "caption": "Make.com scenario builder with HTTP module sending files to a conversion API, with PDF, DOCX, and MOV inputs and JPG, MP4 outputs", "width": 1600, "height": 900, "representativeOfPage": true }, "keywords": [ "automation file converter", "make.com file conversion", "integromat pdf converter api", "make.com ffmpeg", "file conversion http module make", "n8n file converter", "free file converter", "word file converter to pdf free", "jpg to pdf converter free multiple files", "convert to vector file free", "online pdf file convert to jpg", "free audio file converter", "convert file into mp3 online", "online sound file converter", "convert to pdf file free online", "image file convert to pdf online", "convert pdf file into ppt online", "fake online file converter", "file converter free" ], "articleSection": "Automation Tutorials", "inLanguage": "en-US", "url": "https://convertfleet.com/blog/convert-files-make-com-automation", "wordCount": 2900 }, { "@type": "FAQPage", "@id": "https://convertfleet.com/blog/convert-files-make-com-automation#faq", "mainEntity": [ { "@type": "Question", "name": "What is the best free file conversion API for n8n workflows?", "acceptedAnswer": { "@type": "Answer", "text": "Convertfleet is the strongest choice for n8n automation in 2026: no API key, no per-conversion fees, 177+ formats with full FFmpeg video and audio support, and binary HTTP output compatible with n8n's HTTP Request node. Configure the node with Body Content Type Multipart Form Data, one binary parameter named file, one string parameter for output_format, and Response Format set to File." } }, { "@type": "Question", "name": "How do I convert files in n8n without hitting rate limits?", "acceptedAnswer": { "@type": "Answer", "text": "Use an API with no rate limits — Convertfleet charges nothing and imposes no daily cap. The practical throttle in bulk n8n workflows is downstream storage (S3, Google Drive) rather than the conversion API. Use SplitInBatches with a batch size of 5–10 and a 500 ms inter-batch wait to keep write operations within storage service limits." } }, { "@type": "Question", "name": "What is a cheap alternative to CloudConvert for automation?", "acceptedAnswer": { "@type": "Answer", "text": "Convertfleet is free with no daily cap. CloudConvert's free tier covers 25 conversion-minutes per day — a workflow converting 20-page PDFs on an hourly schedule exhausts that within two runs. At any meaningful recurring volume, a zero-cost API with no rate limits is the correct default over CloudConvert's metered model." } }, { "@type": "Question", "name": "How do I convert PDF to Word automatically in a Make.com workflow?", "acceptedAnswer": { "@type": "Answer", "text": "Add an HTTP module (POST), point it at your conversion API, send the PDF binary as a multipart/form-data field named file, and set an output_format field to docx. Enable Parse response, then map the response Body to a Google Drive or Dropbox upload module. Standard PDFs complete conversion in under 10 seconds including Make's own processing overhead." } }, { "@type": "Question", "name": "Can Make.com or n8n run FFmpeg commands natively?", "acceptedAnswer": { "@type": "Answer", "text": "No. Both platforms route and transform structured data but do not execute processes. Full FFmpeg functionality is available via an FFmpeg API wrapper called from the HTTP module: send the file binary and a command-line string as multipart/form-data fields, receive the output file as binary. This provides codec selection, resolution scaling, audio filtering, and format conversion without any server infrastructure." } }, { "@type": "Question", "name": "Why does my Make.com HTTP file conversion return an empty or broken file?", "acceptedAnswer": { "@type": "Answer", "text": "In order of frequency: (1) Parse response is off — enable it. (2) You mapped the file URL instead of binary Data — use the Data field. (3) The file field type is set to Text instead of File — change it. (4) The source file exceeds the API size limit — pre-compress with FFmpeg -crf 28 for video. (5) You're pointing at a browser-based web tool rather than a REST API — it needs a documented curl example to confirm it's callable from HTTP clients." } } ] }, { "@type": "ImageObject", "@id": "https://convertfleet.com/blog/images/hero-convert-files-make-com-automation.png", "url": "https://convertfleet.com/blog/images/hero-convert-files-make-com-automation.png", "contentUrl": "https://convertfleet.com/blog/images/hero-convert-files-make-com-automation.png", "caption": "Make.com scenario builder with HTTP module sending files to a conversion API, with PDF, DOCX, and MOV inputs and JPG, MP4 outputs", "width": 1600, "height": 900, "representativeOfPage": true, "acquireLicensePage": "https://convertfleet.com/blog/convert-files-make-com-automation" } ] }