Resources · Make integration

EDRMS Docupile Make integrationAutomate EDRMS Docupile with Make.

Can Make file your documents in EDRMS Docupile for you? The EDRMS Docupile Make integration has 1 action module that uploads a file. This guide is for teams that archive documents by hand, and it walks you from the connection to a working first scenario.

Try the EDRMS Docupile integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the EDRMS Docupile Make integration do?

The EDRMS Docupile Make integration lets a Make scenario, the automation you build in Make, push a file into your EDRMS Docupile account without anyone dragging it there. It has a single module, Upload File to EDRMS, so the file always comes from an earlier step: another app, a form, an email.

Think of it as the last stop of a flow. Something produces a document somewhere else, and Upload File to EDRMS files it in Docupile. Three typical setups show the idea.

Signed paperwork lands in the archive. When a contract or a form comes back from another tool, the file travels to the upload module and ends up stored in EDRMS Docupile, with no download and re-upload by hand.

Email attachments stop living in inboxes. A mail app watches for new messages, and each attachment it passes along becomes one bundle (one item moving between modules) that the upload module sends to Docupile.

Form uploads reach the records system. A form tool such as the one described on the 123FormBuilder Make integration page can collect the file, and the upload module does the filing.

What the integration does not do: it has no trigger, so Docupile cannot start a scenario, and there is no search or download module. Make also notes that its documentation for this app is limited, because little public information exists about EDRMS Docupile. Test on a sample file before you rely on it. If you also look at n8n, the n8n vs Make comparison helps you weigh the two tools, and the Make training covers the editor from scratch.

Connect

How do you connect EDRMS Docupile to Make?

  1. 01

    Add the module and start a connection

    In your scenario, add the Upload File to EDRMS module and click Create a connection. A connection is your Docupile account linked to Make once, then reused by every module of the app.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, so you recognize it later. Then either approve Make on the Docupile page that opens, or paste the key Docupile gives you, depending on what the connection window asks for.

  3. 03

    Save and check

    Click Save. The connection now appears in the module, and you can go on to fill the rest of the module with data from the steps that come before it.

First scenario

Your first scenario with EDRMS Docupile

GoalWhen a file shows up in another app, Make uploads it to EDRMS Docupile.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Docupile has no trigger, this first module belongs to the app where your files arrive.

  2. 02

    Pick the source of the file

    Search that app by name, choose its module that produces a file, and click Create a connection to link your account there. Fill its fields; Make lists the folders or objects it can read.

  3. 03

    Add Upload File to EDRMS

    Click the + on the right of the first module, search EDRMS Docupile and pick Upload File to EDRMS. Connect your Docupile account, then map the file coming from the previous module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time, and you can open each module to read the bundles it received. Check in Docupile that the test file really arrived.

  5. 05

    Schedule and switch on

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

Modules

What the EDRMS Docupile module does

EDRMS Docupile gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

EDRMS Docupile1

Upload File to EDRMS

ActionIn the docs only

This action takes a file handed over by an earlier module and stores it in your EDRMS Docupile account, so documents get archived without a manual upload. It is the only module of the app and the natural end of any flow feeding Docupile.

When to use it
a contract, invoice or form attachment is produced in another tool and belongs in your document system.
Watch out
Make's documentation for this app is limited, so test one file with Run once and check it in Docupile first.
Need help

Need help automating EDRMS Docupile with Make?

A person reads every message.

FAQ

EDRMS Docupile and Make: frequent questions

01Is the EDRMS Docupile Make integration free?
Yes, EDRMS Docupile is a standard app in Make, so it works from the Free plan. That plan allows 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. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits, meaning operations, per month. What EDRMS Docupile itself charges is outside the scope of this page.
02What is needed to connect EDRMS Docupile to Make?
An EDRMS Docupile account and a Make account are the starting point. Make's documentation lists no specific prerequisite for this app and gives no official connection steps, so the generic Make flow applies: add the module, click Create a connection, optionally name it, authorize Make on the Docupile page or paste the key Docupile provides, then click Save. The same connection is then reused by every module of the app. Because documentation is limited, a quick test upload is the safest way to confirm the connection works.
03Can an EDRMS Docupile scenario start in real time?
Not from Docupile itself, because the app has no trigger module in Make. The scenario has to start from something else. The usual option is a trigger from another app, placed first, that passes a file to Upload File to EDRMS. If that trigger is scheduled, Make checks on the scenario's schedule, every 15 minutes by default. If it is an instant trigger, the other app calls Make through a webhook as soon as something happens. Either way, Docupile is the destination, never the starting point.
04What if a needed EDRMS Docupile module is missing?
It depends on what is missing. EDRMS Docupile has a single module, Upload File to EDRMS, and no Make an API Call module, so the integration offers nothing to read, search or delete documents in Docupile. When a flow needs more, the practical route is to do that part in another app that Make supports and keep Docupile as the upload step. For a setup that the module cannot cover, the Make agency team can study the case with you and suggest another route.
05Should EDRMS Docupile be automated with Make or n8n?
It depends on which tool the team already uses and on whether the needed feature exists there. On Make, EDRMS Docupile offers one upload action, no trigger and limited documentation, so the question to check first is whether that single action covers the job. The same app sometimes has an n8n node as well; when it does, compare what each side offers for Docupile rather than the platforms in general. Nothing on this page ranks one tool above the other on price or speed.
Same platform

Other docs you might need on this stack.

Browse all integrations