# DigiParser + Make | Build Document Processing Scenarios

Source: https://www.digiparser.com/integrations/make

[<- All integrations](/integrations)

![](https://www.make.com/en/android-chrome-192x192.png) DigiParser for Make

# Give your Make scenarios structured document data.

Use dedicated DigiParser modules to upload files and receive extracted fields. Keep document intake and completed-data delivery in separate scenarios.

[Start free ↗](https://app.digiparser.com/auth/join)[Setup documentation ->](/docs/guides/integrations/setting-up-make)

## Two modules.  
Two clear jobs.

**Upload a document**  
Send a file or file URL into a parser or classifier.

* * *

**Watch processed documents**  
Start the next scenario when extracted data is ready.

## Give file intake and processed results their own scenarios.

Use an intake scenario to upload documents, then a separate scenario to deliver the extracted fields to your destination.

1.  1Send the file with Upload a document.
2.  2Start the results scenario with Watch processed documents.
3.  3Map the processed fields into the destination module.

![](/_next/image?url=%2Fimages%2Fintegrations%2Fmake-workflow-v1.webp&w=3840&q=75&dpl=dpl_4CEHPWQCJofunboV6oYnMCcudHh5)

## Choose the right data location first

Install the DigiParser app through **Integrations -> Make -> Open in Make**. Choose your Make organization. When you create a DigiParser connection, match its data location to the account that issued the API key.

DigiParser connection in Make

Data location

DigiParser account endpoint

Connection rule

United States

api.digiparser.com

Use the key from the US account

European Union

eu.digiparser.com

Use the key from the EU account

Create separate Make connections if you work with both locations. The API key needs Open parsers and classifiers, Upload documents, and Manage Integrations, plus access to the selected parser.

## Scenario A: upload documents

1.  01
    
    ### Add the source module
    
    Use the app that supplies your file, such as a Gmail attachment or new Dropbox file.
    
2.  02
    
    ### Add Upload a document
    
    Select your DigiParser connection and choose a parser, or a classifier for mixed document types.
    
3.  03
    
    ### Map the source file
    
    For File, map both the filename and file data. For File URL, provide a direct download link that does not require sign-in.
    
4.  04
    
    ### Run once, then enable
    
    Click Run once, create a test event, and check the DigiParser inbox. Turn on the scenario after the test succeeds.
    

[![Make Upload a document module showing the parser and file URL](https://documents.digiparser.com/docs/screenshots/2026-07-23/live-make-upload-module.png?sig=b2d5c8bc5166c018692dda65eb1ed470879f4f055891f75f36425af66e7a22ff)](https://documents.digiparser.com/docs/screenshots/2026-07-23/live-make-upload-module.png?sig=b2d5c8bc5166c018692dda65eb1ed470879f4f055891f75f36425af66e7a22ff)

Make's Upload a document module with the parser and file source configured.

## Scenario B: watch completed documents

Example: invoice reporting scenario

1.  01Watch processed documents
2.  02Extracted data + Metadata
3.  03Google Sheets or Excel action

Start a separate scenario with **Watch processed documents**. Select the extraction parser, add the destination module, and map values from Extracted data or Metadata. Make registers the trigger automatically; you do not need to paste a webhook URL.

[![Make mapping panel showing DigiParser extracted fields ready to map into later modules](https://documents.digiparser.com/docs/screenshots/2026-07-23/live-make-processed-data-mapping.png?sig=c2f663a3bc730167b50b942bf15c1eef0dea1c0ac52bcfbb61ebd4f612e5708f)](https://documents.digiparser.com/docs/screenshots/2026-07-23/live-make-processed-data-mapping.png?sig=c2f663a3bc730167b50b942bf15c1eef0dea1c0ac52bcfbb61ebd4f612e5708f)

The Make mapping panel exposes DigiParser extraction fields for downstream modules.

For a classifier intake, watch the target parser. Required document review must finish before the processed-data scenario runs.

## Build scenarios around the work your team owns

### Invoice data -> reporting

Upload supplier invoices in the first scenario. In the second, map invoice totals and due dates into an Excel or Sheets reporting action.

### Customer PO -> order operations

Extract customer order fields and line items. Add the destination ERP or CRM modules in Make, with iteration where its line-item actions require it.

### Document -> archive + notification

Use the document metadata in separate Make actions to store the original file and notify operations. Configure the destinations and any filters in Make.

## Check the connection, sample, and scenario state

The connection fails. What should I check?

Check the selected data location, API-key permissions, and access to the chosen parser or classifier.

I can upload, but I cannot see extracted fields.

The upload module receives the document. Map completed fields in a separate scenario using Watch processed documents.

How do I test changed fields?

Process a representative document, refresh the trigger data, and check each destination mapping before turning on the scenario.

[Start free ↗](https://app.digiparser.com/auth/join)[Setup documentation ->](/docs/guides/integrations/make-use-processed-data)