Resources · Make integration

eFileCabinet Make integrationAutomate eFileCabinet with Make.

What if your documents filed themselves in eFileCabinet? The eFileCabinet Make integration gives you 5 action modules to create, upload, rename and download. This page shows how to link your account and build a first working flow, step by step.

Try the eFileCabinet integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the eFileCabinet Make integration do for you?

It lets Make act inside eFileCabinet for you. You build a scenario, which is the automation itself: a chain of modules, each module being one brick that does one job. The eFileCabinet bricks create folders, drawers or cabinets, send files in, rename items and pull files back out, so filing stops being a manual chore.

A folder ready before the paperwork arrives. A deal closes in your CRM, and Create an Item opens a matching folder in the right cabinet. The next module, Upload a File, drops the signed contract inside, so nobody has to remember where it goes.

Names that follow your convention. Files often land with whatever name the sender chose. Rename an Item applies your own pattern, such as client name plus document type, the moment the file is stored.

Documents that travel to other tools. Download a File hands a stored document to the next module, which can attach it to an email or copy it to another storage app.

There is a real limit to know: eFileCabinet has no trigger in Make, so something else has to start the scenario, either another app or the schedule. Make also flags its own documentation for this app as limited. When you want the wider picture, read the Make review or check Make pricing. If you also work with n8n, the n8n vs Make comparison helps you pick a tool.

Connect

How do you connect eFileCabinet to Make?

  1. 01

    Add an eFileCabinet module

    In your scenario, search for eFileCabinet and pick any of its modules. Then click Create a connection. A connection is your eFileCabinet account linked to Make once, and every eFileCabinet module reuses it afterwards.

  2. 02

    Name the connection

    Giving it a name is optional, but it pays off the day you manage two accounts, for example a test cabinet and the live one. Pick something your colleagues will recognize at a glance in the list.

  3. 03

    Authorize and save

    Follow the screen eFileCabinet shows you: approve access on its page, or paste the key the app provides. Then click Save. From here on, Make can list what your account is allowed to see.

First scenario

Your first scenario with eFileCabinet

GoalWhen another app sends a new document, Make creates a folder in eFileCabinet and uploads the file into it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Since eFileCabinet has no trigger, start with the app that produces your documents, such as a form or email tool.

  2. 02

    Add Create an Item

    Click the + to the right of the first module, search eFileCabinet and choose Create an Item. Link your account, then map a name from the first module, like the client name.

  3. 03

    Add Upload a File

    Add one more module, Upload a File. Map the file coming from the first app and point it to the folder you just created. Each file moving along is a bundle, one item passed between modules.

  4. 04

    Test with Run once

    Click Run once to run the scenario a single time. Open each module to read the bundles it received, then check in eFileCabinet that the folder and the file really appeared.

  5. 05

    Schedule and switch on

    On the first module, open the clock and set the schedule: every 15 minutes by default. Switch the scenario on. From then on, each new document gets its own folder without you lifting a finger.

Modules

What each eFileCabinet module does

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

eFileCabinet1

Create an Item

Action

In Make“Creates a new folder, drawer, or cabinet inside of eFileCabinet.”

Builds a new folder, drawer or cabinet in eFileCabinet, so the structure exists before any file needs a home. It gives your documents a clear place to land in later steps.

When to use it
a new client or project shows up in another app and deserves its own space right away.
Watch out
each run creates a new item, so a test repeated with Run once leaves duplicates you will have to tidy up.
eFileCabinet2

Download a File

Action

In Make“Downloads a file from eFileCabinet.”

Pulls a stored file out of eFileCabinet and passes it to the next module as a bundle. From there, any later module can use the file content.

When to use it
a contract kept in eFileCabinet must go out as an email attachment or be copied to another storage app.
Watch out
on the Free plan, Make handles files up to 5 MB, so check the size of heavy scans before you rely on this module.
eFileCabinet3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the eFileCabinet API with the connection you already set up. It covers everything the four ready-made modules leave out, without a second login.

When to use it
you need an operation that has no dedicated module, and you have the API reference of eFileCabinet at hand.
Watch out
this module relies on your knowledge of the eFileCabinet API: you write the request yourself and read the raw answer in Run once.
eFileCabinet4

Rename an Item

Action

In Make“Renames a file, folder, drawer, or cabinet in eFileCabinet.”

Changes the name of a file, folder, drawer or cabinet, which keeps your archive readable when documents arrive with vague names like scan or document.

When to use it
right after an upload, to apply your naming pattern built from data of an earlier module.
Watch out
the new name replaces the old one for everyone who browses the cabinet, so test the pattern with Run once before you switch the scenario on.
eFileCabinet5

Upload a File

Action

In Make“Uploads a file to eFileCabinet.”

Sends a file from another step of the scenario into eFileCabinet. It is the module that actually files your documents for you, wherever they come from.

When to use it
an attachment, a signed PDF or a form export has to be archived in a precise folder.
Watch out
Make documents no field for this module, so test it once with a real file and check in eFileCabinet that it landed in the right folder.
Need help

Need help automating eFileCabinet with Make?

A person reads every message.

FAQ

Questions about the eFileCabinet Make integration

01Is the eFileCabinet Make integration free?
Yes, eFileCabinet is a standard app in Make, available from the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Each module run on one item counts as an operation, which is what Make measures on your plan. Paid plans such as Core, Pro, Teams and Enterprise lower the interval to 1 minute and remove the cap on active scenarios.
02What does it take to connect eFileCabinet to Make?
You need an eFileCabinet account and a Make account. Make's documentation lists no special prerequisite and gives no official connection steps for this app, so the generic flow applies. Add an eFileCabinet module, click Create a connection, give it a name if you like, then either authorize Make on the eFileCabinet page or paste the key the app provides. Click Save and every eFileCabinet module in your scenarios can reuse that connection. If something looks different on screen, follow what eFileCabinet shows.
03Does eFileCabinet trigger scenarios in real time?
No, eFileCabinet has no trigger module in Make, neither scheduled nor instant. A scheduled trigger is one Make checks at regular intervals, while an instant trigger is one the app calls through a webhook. Here, the scenario has to start elsewhere: on a trigger of another app, for example a form or an inbox, or on the schedule of the first module, every 15 minutes by default. The eFileCabinet modules then act as the following steps, creating folders, uploading or renaming files.
04What if an eFileCabinet module is missing in Make?
It depends on the task, but the Make an API Call module is the answer in most cases. It reaches any endpoint of the eFileCabinet API with the same connection as the other modules, so you are not limited to the 5 listed ones. The trade-off is that you write the request yourself, with the API reference of eFileCabinet next to you. Make also warns that its documentation for this app is limited, so test each call with Run once and read the answer before activating the scenario.
05Make or n8n for eFileCabinet automation?
It depends on the tool your team already runs. Make offers 5 eFileCabinet modules, including Make an API Call for anything they miss, and a visual editor where you test with Run once. The same app often has a node in n8n too, so check what that side offers for your use case before you decide. The practical criteria are the modules you actually need, the plan you already pay for and who will maintain the scenarios. Pick the tool where your other automations already live, so everything stays in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations