Why File Storage Is a Common Make.com Pain Point
Most Make.com automations that handle files follow the same pattern: a file arrives from somewhere — a form submission, an email attachment, a CRM export — and you need to do something with it. The problem is that many intermediate file URLs in Make are temporary. They expire after a short window, which breaks any downstream step that tries to access them later.
What you actually need is a hosted, permanent URL you can pass to a CRM record, embed in an email, or log in a spreadsheet without worrying that it'll 404 in two days. That's exactly the gap that a dedicated make file storage integration fills.
Foldr.Space solves this cleanly. Every file you upload — whether through the web interface, the API, or an automation — gets a permanent download link that never expires. That link becomes a stable building block for the rest of your scenario.
How the Foldr and Make.com Integration Works
Foldr.Space has a native Make.com integration, which means you don't need to cobble together HTTP request modules or wrestle with authentication from scratch. You connect your Foldr account once, and then you can call Foldr actions directly from any scenario as a first-class module.
The core action you'll use most often is uploading a file and receiving a permanent link in return. That link is the output you pass into whatever comes next — a Slack message, a Google Sheet row, a Notion database entry, or an email send.
You can find the full details of the native connector on the Foldr integrations page at /integrations/make. It covers authentication, available triggers and actions, and the field mappings you'll need.
Setting Up the Integration: Step by Step
Start by logging into Make.com and creating a new scenario. Add the module that produces or receives the file you want to store — a Google Drive watch, a Typeform submission with attachments, an email parser, or whatever your source is. Run the scenario once to capture a sample bundle so Make knows the data structure.
Next, add a Foldr module to the canvas. Search for 'Foldr' in the module library. Click 'Create a connection' and enter your Foldr API credentials. If you're on the free tier you can test with a personal upload link, but for production automations a Pro account or a Foldr Space gives you the storage capacity and organization you'll want.
Map the file data from your previous module into the Foldr upload action. The key fields are the file content (usually a binary or a URL reference, depending on your source module) and the filename. Optionally, you can set a password on the link or configure link expiration if you don't want the file to be permanent — useful for sensitive documents that should self-destruct after a set time.
Run the scenario. Foldr returns a permanent URL in the output bundle. Map that URL into your next module — log it, send it, store it. That's the whole setup.
Using the Foldr API Directly for Advanced Scenarios
The native Make module covers the most common use case. But if you're building something more complex — bulk uploads, dynamic folder routing, or programmatic link management — you may want to hit the Foldr developer API directly using Make's HTTP module.
Foldr's REST API at /api/v1 supports programmatic uploads, bulk operations, and full control over link settings. You authenticate with an API key, POST your file as multipart form data, and get back a JSON response containing the permanent link and file metadata. This gives you more flexibility than the standard module when your scenario has conditional logic around how files should be stored.
One practical use case: a scenario that receives invoice PDFs from an accounting tool, uploads each one to Foldr, and writes the permanent Foldr URL alongside the invoice record in a database. Because the links never expire, your finance team can retrieve any invoice months later without chasing broken links. The API makes it straightforward to automate this at scale.
Choosing the Right Foldr Plan for Your Automation Volume
If you're just prototyping or running low-volume automations, the free tier is a reasonable starting point. You can upload files up to 2GB each with no account required and get a permanent link immediately — useful for testing your scenario end-to-end before committing to a paid plan.
For production workflows, the Pro plan is usually the right fit for individuals or small teams. It gives you 20GB of permanent storage, along with extras like swappable images, URL shortening, and a bio page. One-time pricing options ($99 for one year, $149 for two years) make it predictable cost-wise if you prefer not to think about recurring billing.
Teams handling higher volumes should look at Foldr Spaces. The Basic tier offers 5GB of dedicated team storage, Standard bumps to 20GB, and Premium reaches 100GB. Spaces keep team files organized and separate from personal uploads, which matters once more than one person is triggering automations that write to the same storage.
Practical Workflow Examples You Can Build Today
A few concrete scenarios that work well with this integration: First, a client delivery workflow where completed design files are automatically uploaded to Foldr when a project status changes in your project management tool. The client receives an email with a permanent download link — no shared drive permissions to manage, no expiring Dropbox links.
Second, a form-to-storage pipeline. If you use Foldr's built-in form builder with file upload support, submissions can feed directly into a Make scenario that processes the file, routes it based on metadata, and stores a reference URL in your CRM. The direct upload path at /upload also lets you accept files from external users without them needing a Foldr account.
Third, a media asset pipeline for content teams. Images, audio files, or video clips uploaded through Make get stored on Foldr and return direct embed URLs. Those URLs work immediately in web pages, emails, or CMS entries — no extra CDN configuration required.
These aren't hypotheticals — each relies only on documented Foldr features: permanent links, direct embed URLs, password protection, and the Make integration. Pick the pattern closest to your use case and adapt it.
Handling Edge Cases and Troubleshooting
The most common issue when building a make.com file upload scenario is the file arriving as a URL reference rather than binary data. Some source modules give you a temporary URL instead of the actual file bytes. In that case, add a Make HTTP 'Get a file' module between your source and the Foldr upload step to fetch the binary first.
If you're hitting file size limits during testing, check which tier your account is on. The free tier supports files up to 2GB per upload, which covers most common automation payloads. Unusually large files — video exports, large database dumps — may require chunking or a direct API upload rather than the standard module.
Authentication errors usually mean your API key has been regenerated since you created the Make connection. Go into your Make connections panel, find the Foldr connection, and re-enter your current API key. It's worth storing your API key somewhere secure (a password manager, not a Make data store) so you can retrieve it quickly when you need to reconnect.
Keeping Your Automations Maintainable Over Time
Automations that touch file storage have a habit of becoming invisible infrastructure — they run quietly in the background until something breaks, and then everyone is surprised. A few habits keep them healthy: label every Foldr module in your Make scenario with what it's uploading and why, and add an error handler that logs failures to a Slack channel or a spreadsheet.
Use Foldr's link expiration feature deliberately. If a file is only needed for a short window — say, a one-time client handoff — set it to self-destruct after the relevant period rather than accumulating permanent links you'll never audit. For everything that needs to persist, a permanent link is the default and requires no extra configuration.
Periodically review your Foldr storage usage, especially if you're on a fixed-tier plan. Automated workflows can fill storage faster than manual uploads, particularly if they're processing high-frequency triggers. Setting up a Make scenario that monitors storage and alerts you when you approach a threshold is a worthwhile five-minute build.
Frequently Asked Questions
Do I need a Foldr account to use it with Make.com?
You don't need an account to do a basic upload — Foldr's free tier lets you upload files up to 2GB and get a permanent link without signing up. However, for production Make.com automations you'll want an account so you can manage your API key, track uploads, and maintain predictable storage capacity.
What happens to the file links if I downgrade or cancel my Foldr plan?
Foldr's permanent links are designed to persist, but storage availability depends on your active plan. Check Foldr's terms for specifics on what happens to files after a plan change. For business-critical automations, keeping an active paid plan ensures continuity.
Can I upload multiple files in a single Make.com scenario run?
Yes. You can use Make's iterator or repeater modules to loop over an array of files and call the Foldr upload action for each one. Alternatively, Foldr's API at /api/v1 supports bulk upload operations if you'd rather batch them in a single HTTP request.
Is it possible to password-protect files uploaded via Make?
Yes — Foldr supports password-protected links as a built-in feature. When configuring the Foldr upload module in Make, you can set a password that recipients must enter before downloading the file. This works for sensitive documents you need to share via automation but want to restrict access to.
Can I use Foldr file links to embed images or videos in emails or web pages?
Foldr provides direct embed URLs for images, videos, and audio files, not just download links. These embed URLs can be dropped directly into HTML, CMS fields, or email templates without any additional hosting setup. This makes them useful for automations that generate content and need media hosted reliably.
What's the difference between using the native Foldr Make module versus the HTTP module with the API?
The native module is faster to set up and handles authentication cleanly — it's the right choice for most upload-and-get-a-link use cases. The HTTP module calling the API directly gives you more control: you can access advanced parameters, handle bulk uploads, or build conditional logic around the request that the standard module doesn't expose.
The fastest way to move forward is to build a minimal version of your scenario today: connect one file source, add the Foldr upload module, and verify that you get a working permanent link out the other end. Once that core loop works, layering in conditional logic, password protection, or Spaces organization is straightforward. Start simple, confirm the link behavior matches your expectations, and then scale the automation from there.