Resources · Make integration

DocuWare Make integrationAutomate DocuWare with Make.

Want DocuWare documents to file, index and move themselves? The DocuWare Make integration gives you 21 modules: 1 instant trigger, 14 actions and 6 searches. This guide is for teams that already run DocuWare Cloud and want to connect their account, then build a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the DocuWare Make integration do for you?

The DocuWare Make integration links your DocuWare Cloud system to Make, a no-code tool where you build a scenario, meaning the automation itself: a chain of modules, each one a brick that triggers, acts or searches. DocuWare can call Make the moment something happens, and Make can then store, index, stamp, download or move documents for you.

Invoices that land in the right cabinet. A scanned supplier invoice arrives from another app; Store to File Cabinet places it in DocuWare, and Update Index Fields fills in the index values your accountants search on later.

A reaction to what happens in DocuWare. Receive a Webhook starts the scenario when DocuWare sends data, Get Document Information reads the full index, and the next module pushes it wherever your team works. Place a Stamp can then mark the page as processed.

Tidy trays instead of piles. List Documents in Document Tray shows what is waiting in a tray, and Transfer Documents moves those files to their final location.

What Make does not do here: the documentation requires a running DocuWare Cloud system, so check that first. When a listed module falls short, Make an API Call reaches the rest of the DocuWare API. The same app often exists as an n8n node too; the n8n vs Make comparison helps you pick. New to the editor? The Make training starts from zero, and Make pricing explains what each plan allows.

Connect

How do you connect DocuWare to Make?

  1. 01

    Add a DocuWare module

    Inside your Make scenario, add any DocuWare module and click Create a connection. A connection is your DocuWare account linked to Make once, then reused by every DocuWare module. You can give it a name in Connection name so you spot it later.

  2. 02

    Enter your server URL

    In DocuWare Server URL, type the address of your DocuWare Cloud system, shaped like organization.docuware.cloud. Use the address your team opens every day, without guessing: Make talks to that exact system.

  3. 03

    Sign in or paste credentials

    Enter the credentials you copied from DocuWare, or follow the on-screen prompts. For OAuth2, open Configuration in DocuWare, then App Registrations, and copy the Client ID (and the Client secret when it is shown).

First scenario

Your first scenario with DocuWare

GoalWhen DocuWare sends data to Make, Make reads the document's index and updates its fields.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add your first module. The canvas stays empty until then.

  2. 02

    Add Receive a Webhook

    Search for DocuWare and pick Receive a Webhook. Click Create a webhook, then Create a connection. Set up the matching webhook on the DocuWare side as well.

  3. 03

    Read the document

    Click the + on the right, add Get Document Information and map the document from the webhook data. Make lists the file cabinets it can read once your connection exists.

  4. 04

    Update the fields

    Add Update Index Fields and map the values to write, taken from the previous module. Each item passed along is a bundle: here, one document and its index.

  5. 05

    Test with Run once

    Click Run once, then trigger the event in DocuWare. Open each module's bubble to read the bundles it received and check that the fields changed as planned.

  6. 06

    Switch it on

    Turn the scenario on. Since the trigger is instant, DocuWare calls Make as soon as the event happens, and each module run counts as one operation on your plan.

Triggers

What starts a DocuWare scenario

1 module starts a scenario when something happens in DocuWare. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by DocuWare as soon as it happens.

DocuWare1Receive a Webhook

Receive a Webhook

Instant trigger

In MakeTriggers when webhook receives data from DocuWare. Configure webhook also in DocuWare.

This trigger opens a door for DocuWare: the moment DocuWare sends data, your scenario starts with that data in hand, ready for the next module. It is the only DocuWare trigger in Make, so every reactive scenario begins here.

How it fires
instant, DocuWare calls Make through a webhook as soon as the event happens, with no polling.
When to use it
when a document needs follow-up right after something happens in DocuWare, such as a filing your finance team waits on.
Watch out
creating it in Make is half the job; the webhook must also be configured inside DocuWare, or nothing ever arrives.
Modules

Everything the DocuWare modules can do

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

DocuWare1

Append a File

Action

In MakeAppends a file to a document.

Adds one more file to a document that already exists, so a signed page or an attachment joins the original record instead of creating a second one.

When to use it
a customer returns a signed contract and you want it inside the same DocuWare document as the draft.
Watch out
it adds, it never replaces; for a corrected version, Replace a File fits better.
DocuWare2

Convert the Index Fields to a Flat List

Action

In MakeConverts the index data of documents to a flat list.

Turns the index data of a document into a simple flat list, which makes the values far easier to map into a spreadsheet, a CRM or an email in the next module.

When to use it
right after Get Document Information, when you want to pick one field by name instead of digging through nested data.
DocuWare3

Delete a Document

Action

In MakeDeletes a document in a file cabinet.

Removes a whole document from a file cabinet, files and index included, so duplicates or test entries stop cluttering searches.

When to use it
at the end of a cleanup flow where Search in File Cabinet has already found the exact document to drop.
Watch out
treat the deletion as final and test with Run once on a throwaway document first.
DocuWare4

Delete a File

Action

In MakeDeletes a file in a document.

Takes a single file out of a document while the document itself and its index stay in place. Handy when one page was scanned twice or attached by mistake.

When to use it
a wrong attachment slipped into an otherwise correct record.
Watch out
pick the file carefully, because the rest of the document is kept and only that file disappears.
DocuWare5

Download a Document

Action

In MakeDownloads a document (e.g., original, PDF with annotations, or PDF without annotations).

Pulls a document out of DocuWare so the next module can send, archive or share it. You choose the version: the original, a PDF with annotations or a PDF without them.

When to use it
emailing a clean PDF to a client, or the annotated one to a colleague who needs the reviewer's notes.
Watch out
on the Free plan, Make handles files up to 5 MB.
DocuWare6

Download a File

Action

In MakeDownloads a file from a document.

Grabs one specific file from inside a document, rather than the whole thing, which keeps the data light when only one attachment matters.

When to use it
a record holds a contract plus its appendices and only the appendix has to go to a partner.
Watch out
for the full document in a chosen format, Download a Document is the better pick.
DocuWare7

Get Document Information

Action

In MakeGets all index data for a document.

Reads every index value of a document, so the rest of the scenario knows its supplier, date, number or whatever fields your cabinet uses.

When to use it
right after Receive a Webhook, to turn a bare document reference into data you can map.
Watch out
the values come back structured; pair it with Convert the Index Fields to a Flat List if mapping gets fiddly.
DocuWare8

Import to Document Tray

Action

In MakeImports a document to a document tray.

Drops a document into a document tray, the waiting area where someone reviews it before it is filed for good.

When to use it
files arriving from a form or a mailbox that a person should check and index by hand before storage.
Watch out
nothing is filed yet; for direct filing with index data, choose Store to File Cabinet instead.
DocuWare9

Place a Stamp

Action

In MakePlaces a stamp on a page of a document.

Puts a DocuWare stamp on a page of a document, the digital version of the rubber stamp that says approved, paid or received.

When to use it
once payment is confirmed in your accounting tool, to mark the matching invoice as paid in DocuWare.
Watch out
run Get Stamps first to see which stamps the tray or cabinet actually offers.
DocuWare10

Replace a File

Action

In MakeReplaces a file in a document.

Swaps a file inside a document for a newer one, so the record keeps its index and place while the content gets refreshed.

When to use it
a revised quote or a corrected scan must supersede the old file without creating a duplicate record.
Watch out
the old file is gone after the swap; keep a copy elsewhere if you need history.
DocuWare11

Store to File Cabinet

Action

In MakeStore a document to a file cabinet.

Files a new document straight into a DocuWare file cabinet, which is how files from email, forms or cloud drives end up in your archive without anyone uploading them.

When to use it
supplier invoices arriving by email that belong in the accounting cabinet.
Watch out
add Update Index Fields afterwards if the document must be searchable by more than its file name.
DocuWare12

Update Index Fields

Action

In MakeUpdates the index data of a document.

Changes the index values of a document already in DocuWare, keeping status, owner or reference fields in line with what happens in your other tools.

When to use it
a deal closes in your CRM and the matching contract's status field should say so.
Watch out
it overwrites the values you map, so leave untouched any field you want to keep.
DocuWare13

Validation Webhook Response

Action

In MakeCreates a response for the dialog validation.

Sends DocuWare an answer for a dialog validation, which lets a Make scenario decide whether what a user entered in a DocuWare dialog is accepted.

When to use it
at the end of a scenario started by Receive a Webhook, once Make has checked the entered values against another system.
Watch out
it only makes sense in a flow that DocuWare called; on its own it has nothing to respond to.
DocuWare14

Get Dialogs

Search

In MakeRetrieves a list of dialogs associated with the selected file cabinet.

Lists the dialogs attached to a chosen file cabinet, those store and search screens your users fill in, so the scenario can work with the right one.

When to use it
while setting up a flow that stores or searches through a specific dialog and you need to find it first.
Watch out
it is a search, so it can return several bundles, one per dialog.
DocuWare15

Get File Cabinets and Document Trays

Search

In MakeRetrieves a list of all available file cabinets and document trays.

Returns every file cabinet and document tray your connection can see, a quick map of where documents can go.

When to use it
a scenario that has to route documents to different cabinets and needs their identifiers.
Watch out
each cabinet or tray comes out as its own bundle, and the next module runs once for each of them.
DocuWare16

Get Stamps

Search

In MakeRetrieves a list of stamps associated with the selected document tray or file cabinet.

Fetches the stamps available in a chosen document tray or file cabinet, so you know exactly what Place a Stamp can apply.

When to use it
building an approval flow and checking whether the approved or rejected stamp exists where the documents live.
Watch out
stamps differ from one cabinet or tray to another, so query the right location.
DocuWare17

Search in File Cabinet

Search

In MakeSearch for documents in a file cabinet.

Looks for documents in a file cabinet and hands them over one by one, which is how a scenario finds the record it needs to update, download or stamp.

When to use it
an order number shows up in another app and you need the matching delivery note in DocuWare.
Watch out
a search can return zero, one or many documents; plan for each case before acting on them.
DocuWare18

Transfer Documents

Search

In MakeTransfers documents between different locations.

Moves documents from one place to another in DocuWare, for example from a tray to a cabinet, so filing does not rely on someone dragging files around.

When to use it
documents reviewed in a tray should reach their final cabinet once someone has checked them.
Watch out
check the source and target with Get File Cabinets and Document Trays before the first run.
DocuWare19

List Documents in Document Tray

SearchIn the docs only

Shows what is currently waiting in a document tray, each document coming out as its own bundle ready for the next step.

When to use it
a scenario that should process whatever the scanner or a mailbox has dropped into a tray.
Watch out
every listed document triggers the following modules once, so each one costs operations on your plan.
DocuWare20

Make an API Call

ActionIn the docs only

Reaches any endpoint of the DocuWare API with the connection you already set up, which covers whatever the other DocuWare modules leave out.

When to use it
you need a DocuWare feature that no listed module offers.
Watch out
you write the request yourself, so keep the DocuWare API documentation open while building it.
Need help

Need help automating DocuWare with Make?

A person reads every message.

FAQ

Questions people ask about DocuWare and Make

01Is the DocuWare Make integration free?
Yes, on the Make side. DocuWare is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and allow unlimited active scenarios, with usage counted in credits per month. You still need your own active DocuWare subscription, which is billed by DocuWare, not by Make.
02What do you need to connect DocuWare to Make?
An active DocuWare account running on a DocuWare Cloud system. In Make, add a DocuWare module, click Create a connection, enter your DocuWare Server URL (the organization.docuware.cloud style address) and then the credentials copied from DocuWare. For OAuth2, those come from App Registrations in the DocuWare Configuration page: the Client ID, plus the Client secret when it appears. If the registration asks for a callback URI, paste https://www.integromat.com/oauth/cb/docuware exactly as written.
03Does the DocuWare trigger in Make react in real time?
Yes. Receive a Webhook is an instant trigger: DocuWare calls Make through a webhook as soon as the event happens, so the scenario does not wait for a schedule. Two conditions apply. You must click Create a webhook before Create a connection in Make, and the webhook also has to be configured in DocuWare itself. Without that second half, the trigger waits and nothing comes in. Once both sides are set, a single Run once in Make followed by the event in DocuWare shows you the incoming bundle and confirms the link works.
04What if a DocuWare module is missing in Make?
It depends on what you need, but Make an API Call usually closes the gap. It calls any endpoint of the DocuWare API with the same connection as the other modules, so you are not limited to the 21 listed ones. The one hard limit from the documentation stays: DocuWare only works with Make through a running DocuWare Cloud system. If that is not your setup, no module will help.
05Should you use Make or n8n for DocuWare?
It depends on your criteria. On Make, DocuWare comes with 21 modules, including an instant trigger and a Make an API Call module for anything else, all usable from the Free plan. Many apps also have an n8n node, so check whether DocuWare has one and whether it covers the actions you need. Then weigh the tool your team already knows and the one your other apps connect to, rather than a general ranking.