# DigiParser + Zapier | Turn Documents into Zap Workflows

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

[<- All integrations](/integrations)

DigiParser x Zapier

# Your documents.  
The starting point for your next Zap.

An invoice arrives. A customer emails a purchase order. DigiParser extracts the fields, and Zapier puts them to work in the next app. Build the handoff with the DigiParser app in Zapier.

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

[The two-Zap workflow](#two-zaps)[Connect Zapier](#setup)[Workflow recipes](#recipes)

## Connect document intake and results with two Zaps.

Use one Zap to send files to DigiParser and a second to act on processed data. Extraction happens between the two workflows.

1.  1Send the source file with Import Document.
2.  2Start the second Zap with Document Processed.
3.  3Map the extracted fields to the destination action.

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

The essential pattern

## One Zap sends the file. A second sends the result.

Extraction takes place between the two Zaps. The upload action creates a document; use the separate **Document Processed** trigger when you need its completed fields.

### Zap 1 - Bring documents in

Example: supplier invoice intake

1.  01Gmail: new email with an attachment
2.  02DigiParser: Import Document
3.  03Invoice parser receives the file

Map a File or a public File URL. Choose a parser for a single document type or a classifier for mixed documents.

### Zap 2 - Put extracted data to work

Example: build an invoice register

1.  01DigiParser: Document Processed
2.  02Map invoice fields
3.  03Google Sheets: create a row

Select the parser that performs the extraction. If a classifier routes the file, select its target parser here.

[![Zap showing Schedule by Zapier followed by DigiParser Import Document](https://documents.digiparser.com/docs/screenshots/2026-07-23/live-zapier-import-workflow.png?sig=332ac46cc5cfe952f817a5f19c0636472575b20e2a1b9e6f72dfc0ae78412876)](https://documents.digiparser.com/docs/screenshots/2026-07-23/live-zapier-import-workflow.png?sig=332ac46cc5cfe952f817a5f19c0636472575b20e2a1b9e6f72dfc0ae78412876)

The DigiParser Import Document action inside the Zapier editor.

## Connect DigiParser to Zapier

1.  01
    
    ### Prepare a parser and a sample
    
    Define the fields and tables you want. Process a representative document so Zapier can load a useful sample.
    
2.  02
    
    ### Create a team API key
    
    In the DigiParser team menu, open API Keys. Grant access to the required parsers or classifiers and enable Open parsers and classifiers, View documents, Upload documents, and Manage Integrations.
    
3.  03
    
    ### Connect the DigiParser app
    
    Add DigiParser to a Zap, connect an account, and paste the key into API Key. Reuse that connection in your document Zaps.
    
4.  04
    
    ### Configure the upload Zap
    
    Choose Import Document. Select Parser or Classifier, map File or File URL, and use File Name only if you want to replace the source name. Test that the document arrives before publishing.
    
5.  05
    
    ### Configure the processed-data Zap
    
    Choose Document Processed, select the target parser, and load a sample. Add the destination action and map its fields. Test the destination record, then publish this second Zap.
    

## Map the fields your next action actually needs

Use invoice number, supplier, totals, dates, and any other fields you defined in the parser. Refresh the trigger sample after changing the parser schema.

Example mapping for an invoice register

DigiParser value

Google Sheets column

Invoice Number

Invoice ID

Supplier

Vendor

Total

Amount due

Document URL

Source document

To copy the original document to Drive or Dropbox, map **Document URL** as the file. Older Zaps may label this value Metadata URL.

[![Zapier Google Sheets action showing DigiParser fields mapped to spreadsheet columns](https://documents.digiparser.com/docs/screenshots/2026-07-23/live-zapier-processed-data-mapping.png?sig=5bfc9c7a2832850875bc8eb2de6703acb01ad2c01149a71b81df9b1724f7f44f)](https://documents.digiparser.com/docs/screenshots/2026-07-23/live-zapier-processed-data-mapping.png?sig=5bfc9c7a2832850875bc8eb2de6703acb01ad2c01149a71b81df9b1724f7f44f)

DigiParser values mapped to columns in a Google Sheets action in Zapier.

## Three useful Zaps to build next

### Supplier invoices -> AP register

Import invoice attachments, extract invoice headers, then use the processed-data Zap to create a Google Sheets row for accounts payable.

Keep supplier invoices in their own parser and map supplier identity, amount, due date, and source link.

### Customer POs -> sales operations

Send customer purchase orders to a PO parser. Use the completed order number and customer fields in your chosen CRM action.

Configure any line-item iteration in Zapier to match the destination app. A customer PO belongs to the sales workflow.

### Approved documents -> file archive

Use Document Processed and map Document URL into a Dropbox or Google Drive file action.

Build the destination filename from extracted fields when the destination action supports it.

## Before you publish the Zaps

Does the trigger wait for review?

If the parser requires review, the processed-data Zap waits until the document is approved.

Why are some fields missing?

Process a representative document with those fields and reload the Zapier trigger sample. Confirm that you selected the parser that performed extraction.

Why does a file URL fail?

It must download without signing in. Test it in a private browser window; a file preview or login page is not a downloadable document.

Can I use native Gmail or Drive import instead?

Yes. If DigiParser already receives the document through a native source, you only need the processed-data Zap to send its result to another app.

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