Skip to main content

Automate Sending Documents to Parseur via n8n

Updated yesterday

Parseur makes it easy to automate document parsing from emails, PDFs, and many other sources. If you use n8n, you can send files directly to your Parseur mailbox in two ways:

  1. Using the native Parseur n8n node (easiest option).

  2. Using n8n’s HTTP Request node with multipart/form-data (for advanced use cases where you need to send extra metadata alongside the document).


Option 1: Send documents with the Parseur n8n node

The Parseur n8n node is the simplest way to push files to your Parseur mailbox.

Steps:

  1. Add a trigger node, like Google Drive > On changes involving a specific folder:

  2. Add a Parseur node to your workflow:

    1. Select the ActionUpload Document.

    2. Choose your Mailbox.

  3. Point the node to the binary file field you want to send.

  4. Run the workflow. The file will appear in your Parseur mailbox, ready to be parsed.

Pros: Quick setup, native node, no need to configure HTTP manually.
⚠️ Limitations: At this time, the Parseur node only supports sending the file itself. You cannot send additional form fields (like custom IDs, tags, or metadata).


Option 2: Send documents with n8n’s HTTP Request node

If you need more flexibility - for example, sending a file plus additional metadata (like a UUID, customer ID, or workflow tag) - you can use the HTTP Request node instead.

Example configuration

  • HTTP Method: POST

  • URL:

    https://api.parseur.com/parser/<mailbox_id>/document/Authentication: API Key (found in your Parseur account settings).
  • Body Content Type: Form-Data

  • Body Parameters:

    • File:

      • Parameter Type → n8n Binary File

      • Name → file

      • Input Data Field Name → data

    • Extra field (example: uuid):

      • Parameter Type → Form Data

      • Name → uuid

      • Value → {{ $('get uuid').item.json.uuid }}

Here’s a screenshot of a working setup (sending both a binary file and a UUID):

Uploaded image

With this setup, n8n sends the file as multipart/form-data, and you can include any extra parameters Parseur (or your workflow) may need.

Pros: Full control - send files and metadata together.
⚠️ Cons: Slightly more setup, requires using the API endpoint directly.


When to use which option?

  • Use Option 1 (Parseur node) if you just need to send files quickly and don’t need to attach extra information.

  • Use Option 2 (HTTP Request node) if you need to send extra fields along with the document.


Useful links

Did this answer your question?