- Home
- Resources
- Integrations
- DocuWare
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 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.
How do you connect DocuWare to Make?
- 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.
- 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. - 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).
Your first scenario with DocuWare
GoalWhen DocuWare sends data to Make, Make reads the document's index and updates its fields.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
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.
Receive a Webhook
Instant triggerIn Make“Triggers 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.
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.
Modules index
- Append a File
- Convert the Index Fields to a Flat List
- Delete a Document
- Delete a File
- Download a Document
- Download a File
- Get Document Information
- Import to Document Tray
- Place a Stamp
- Replace a File
- Store to File Cabinet
- Update Index Fields
- Validation Webhook Response
- Get Dialogs
- Get File Cabinets and Document Trays
- Get Stamps
- Search in File Cabinet
- Transfer Documents
- List Documents in Document Tray
- Make an API Call
Append a File
ActionIn Make“Appends 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.
Convert the Index Fields to a Flat List
ActionIn Make“Converts 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.
Delete a Document
ActionIn Make“Deletes 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.
Delete a File
ActionIn Make“Deletes 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.
Download a Document
ActionIn Make“Downloads 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.
Download a File
ActionIn Make“Downloads 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.
Get Document Information
ActionIn Make“Gets 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.
Import to Document Tray
ActionIn Make“Imports 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.
Place a Stamp
ActionIn Make“Places 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.
Replace a File
ActionIn Make“Replaces 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.
Store to File Cabinet
ActionIn Make“Store 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.
Update Index Fields
ActionIn Make“Updates 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.
Validation Webhook Response
ActionIn Make“Creates 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.
Get Dialogs
SearchIn Make“Retrieves 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.
Get File Cabinets and Document Trays
SearchIn Make“Retrieves 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.
Get Stamps
SearchIn Make“Retrieves 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.
Search in File Cabinet
SearchIn Make“Search 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.
Transfer Documents
SearchIn Make“Transfers 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.
List Documents in Document Tray
SearchIn the docs onlyShows what is currently waiting in a document tray, each document coming out as its own bundle ready for the next step.
Make an API Call
ActionIn the docs onlyReaches any endpoint of the DocuWare API with the connection you already set up, which covers whatever the other DocuWare modules leave out.
Need help automating DocuWare with Make?
A person reads every message.