Document intake

Google Drive import, email forwarding, inbound webhooks, and Zapier.

Beyond manual upload, Parsedit offers four automated ways to get documents into a parser. All intake channels share the same format and size limits and the same duplicate protection: a file the parser has already seen is skipped without consuming quota.

Google Drive

Import files from Google Drive using the Google Picker:

Open a parser and choose the Google Drive intake option.
Sign in with Google if you have not connected yet. Parsedit uses the drive.file scope only, so it can access exactly the files you pick and nothing else in your Drive.
Select up to 25 files. They are imported and processed like regular uploads.

Email forwarding

Every parser can receive documents by email:

Open the parser's email intake settings to find its dedicated inbound address, in the form parser-<id>@ your Parsedit intake domain.
Forward emails with attachments to that address, or set up an automatic forwarding rule in your mail client.
Attachments arrive as pending documents in the parser, ready for processing.

Because each parser has its own address, you can route invoices to one parser and receipts to another with simple mail rules.

Inbound webhook

Push files to a parser programmatically:

POST /api/parsers/inbound/[parserId]

Send the file in the request body.
If your workspace has an inbound secret configured, include it in the x-parsedit-inbound-secret header. Requests without a valid secret are rejected.

This is the simplest way to connect an internal system or a low-code tool that can make HTTP requests.

Zapier

The Parsedit Zapier app works in both directions:

Into Parsedit: send files from Gmail, Dropbox, Google Drive, or any of 6,000+ apps to a parser.
Out of Parsedit: trigger Zaps from parsed documents and route extracted data anywhere Zapier reaches.

Connect Zapier by authorizing it against your Parsedit account inside the Zap editor. You can revoke access anytime under Integrations → Connected applications.

REST API

For full programmatic control, create documents via multipart upload, base64, or a URL with the REST API.

Google Drive

Import files from Google Drive using the Google Picker:

Open a parser and choose the Google Drive intake option.

Sign in with Google if you have not connected yet. Parsedit uses the drive.file scope only, so it can access exactly the files you pick and nothing else in your Drive.

Select up to 25 files. They are imported and processed like regular uploads.

Email forwarding

Every parser can receive documents by email:

Open the parser's email intake settings to find its dedicated inbound address, in the form parser-<id>@ your Parsedit intake domain.

Forward emails with attachments to that address, or set up an automatic forwarding rule in your mail client.

Attachments arrive as pending documents in the parser, ready for processing.

Because each parser has its own address, you can route invoices to one parser and receipts to another with simple mail rules.

Inbound webhook

Push files to a parser programmatically:

POST /api/parsers/inbound/[parserId]

Send the file in the request body.

If your workspace has an inbound secret configured, include it in the x-parsedit-inbound-secret header. Requests without a valid secret are rejected.

This is the simplest way to connect an internal system or a low-code tool that can make HTTP requests.

Zapier

The Parsedit Zapier app works in both directions:

Into Parsedit: send files from Gmail, Dropbox, Google Drive, or any of 6,000+ apps to a parser.

Out of Parsedit: trigger Zaps from parsed documents and route extracted data anywhere Zapier reaches.

Connect Zapier by authorizing it against your Parsedit account inside the Zap editor. You can revoke access anytime under Integrations → Connected applications.