Resources · Make integration

Filestack Make integrationAutomate Filestack with Make.

Files arriving from other tools can land in Filestack and move on by themselves. The Filestack Make integration gives you 6 action modules for uploads, downloads, ZIP files, collages and Workflows. This guide connects your account and walks you through a first scenario.

Try the Filestack integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Filestack Make integration do for you?

The Filestack Make integration links your Filestack account to Make so that files are uploaded, bundled or processed inside a scenario, the automation you build in Make as a chain of modules. Each module is one brick of that chain. Filestack brings six of them, all actions: nothing in Filestack starts a scenario on its own.

Files collected elsewhere, stored in Filestack. When another app hands Make a file or a link, Upload a File pushes it into your Filestack storage and returns a handle, the reference Filestack uses for that file. Every later module works from that handle.

A processing chain started for you. Run a Workflow launches a Workflow you already designed in Filestack, right after the upload. A marketing team gets every new product photo through the same processing without anyone opening the dashboard.

Deliverables packed in one go. Create a ZIP bundles several handles or external URLs into one archive, and Create a Collage assembles images into a single visual. Download a File brings a stored file back into Make so another app can receive it.

What Make cannot do here: watch Filestack for new uploads, since the app has no trigger. The scenario has to start from a schedule or from another app. If a Filestack feature has no module, Make an API call reaches the rest of the API with the same connection. The same app often exists as an n8n node too; the n8n vs Make comparison sets the two tools side by side. To go further, the Make training covers scenario design, and the Make troubleshooting guide helps when a run fails.

Connect

How do you connect Filestack to Make?

  1. 01

    Copy your Filestack keys

    In Filestack, open the Security section of the left menu, then Policy & Signature. Click Copy API key at the top right, then Show next to App Secret and copy the secret shown on screen.

  2. 02

    Add a Filestack module

    In your Make scenario, add any Filestack module and click Create a connection. A connection is your Filestack account linked to Make once, then reused by every Filestack module you add later.

  3. 03

    Paste the credentials

    Give the connection a name in Connection name if you like, it is optional. Paste the API key and the secret you copied, or follow the instructions Make shows on screen, then save the connection.

First scenario

Your first scenario with Filestack

GoalWhen another app sends Make a file, Make stores it in Filestack and starts your Filestack Workflow on it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app that receives your files first, for example a form tool, since Filestack cannot start the flow.

  2. 02

    Add Upload a File

    Click the + on the right of the first module, search Filestack and choose Upload a File. Create the connection, then map the file URL or file data coming from the previous module.

  3. 03

    Chain Run a Workflow

    Add Run a Workflow after the upload and fill its fields. The handle returned by Upload a File is there to map if the module asks which file to process.

  4. 04

    Test with Run once

    Click Run once, then send a test file from the first app. Open each module to read the bundle it received, the single item passed from one module to the next.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, which is every 15 minutes by default on a new scenario, then switch the scenario on. Each module run counts as one operation on your plan.

Modules

What each Filestack module does

Filestack gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Filestack1

Create a Collage

Action

In Make“Creates a collage from the passed file handles.❗️Turn off your Filestack Security before usage.”

Turns several stored images into one composed picture, built from the file handles you pass in. The result is a single visual you can publish or send on without leaving the scenario.

When to use it
a product team wants one preview image that groups every photo uploaded for the same item.
Watch out
Filestack Security must be turned off before this module works, so check that setting first.
Filestack2

Create a ZIP

Action

In Make“Creates a ZIP file from passed file handles or external URLs.❗️Turn off your Filestack Security before usage.”

Packs files into one archive, whether they already sit in Filestack as handles or live elsewhere behind an external URL. The reader of your email gets one download instead of a scattered list of links.

When to use it
a project closes and the client should receive every deliverable in a single file.
Watch out
like the collage module, it requires Filestack Security to be off.
Filestack3

Download a File

Action

In Make“Downloads a file by its handle.”

Fetches a file stored in Filestack by its handle and brings its content into the scenario. From there, the next module can attach it to a message or copy it into another storage tool.

When to use it
you keep only the handle in a spreadsheet or CRM and need the actual file to send it somewhere.
Watch out
downloaded content counts toward your Make file size limits, which are tighter on the Free plan.
Filestack4

Make an API call

Action

In Make“Performs an arbitrary authorized API call.”

Sends a request of your choice to the Filestack API, reusing the connection you already created. It is the way out when the five other modules do not cover a feature you rely on.

When to use it
you need a Filestack endpoint that has no dedicated module in Make.
Watch out
you build the request yourself from the Filestack API documentation, so test it with Run once before switching the scenario on.
Filestack5

Run a Workflow

Action

In Make“Starts your Filestack Workflow.❗️Security fields should be filled in the connection for proper usage (even if your Filestack Security is disabled).”

Starts one of your Filestack Workflows from Make, so the processing you designed in Filestack runs without a click in the dashboard. Make simply gives the signal at the right moment in the flow.

When to use it
right after an upload, when every new file should go through the same processing.
Watch out
the security fields must be filled in the connection, even if Filestack Security is disabled on your account.
Filestack6

Upload a File

Action

In Make“Uploads a file by URL/File Data.”

Stores a file in Filestack from a URL or from file data sent by a previous module, and gives back its handle. Most Filestack scenarios begin their Filestack part here.

When to use it
a form, an inbox or another app delivers a file and you want it kept in Filestack for later processing.
Watch out
on the Free plan, Make handles files up to 5 MB, so check the size of what you send.
Need help

Need help automating Filestack with Make?

A person reads every message.

FAQ

Filestack and Make: common questions

01Is the Filestack Make integration free?
Yes, on the Make side. Filestack is a standard app, available from the Free plan like the 3000+ other standard apps. The Free plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in credits each month. Your Filestack subscription is separate and depends on Filestack pricing.
02What do you need to connect Filestack to Make?
You need an active Filestack account and its API key. In Filestack, open Security, then Policy & Signature, click Copy API key, then Show next to App Secret and copy the secret. In Make, add a Filestack module, click Create a connection, optionally name it, and paste those credentials. If you plan to use Run a Workflow, fill the security fields in the connection, since that module needs them even when Filestack Security is disabled.
03Can Filestack start a Make scenario in real time?
No. Filestack has no trigger module in Make, so nothing in Filestack can launch a scenario by itself. You have two ways to start one anyway. The first is a schedule on the first module, every 15 minutes by default, with 1 minute possible on paid plans. The second is to open the scenario with another app whose trigger fires when a file or a link arrives, then pass that file to Upload a File.
04What if a Filestack module is missing in Make?
It depends on the feature, but Make an API call usually covers it. That module sends any request to the Filestack API with the connection you already set up, so you are not limited to the five dedicated modules. You write the request from the Filestack API documentation and test it with Run once. Also note that the Make documentation for this app is AI-generated from the Filestack docs, so verify important details with Filestack directly.
05Should you use Make or n8n for Filestack?
It depends on the tool your team already runs. On Make, Filestack comes with 6 modules, including Make an API call, and the editor lets you test each step with Run once before switching the scenario on. The same app often exists as an n8n node, so the choice rests less on Filestack itself than on which platform your other automations live on. Pick the one where your existing scenarios and connections already sit.
Same platform

Other docs you might need on this stack.

Browse all integrations