Resources · Zapier integration

Parseur Zapier integrationAutomate Parseur with Zapier.

6 triggers, 2 actions, 0 searches. The Parseur Zapier integration works in both directions: it starts automations when Parseur processes a document, fails one or gets a new mailbox, and it can push emails, PDFs or spreadsheets into a mailbox.

See the 8 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Parseur Zapier integration does

Parseur reads documents sent to a mailbox you set up (emails, PDFs, spreadsheets) and extracts the data you ask for. Zapier connects that mailbox to the rest of your tools: data out when a document is processed, files in when they arrive somewhere else.

Three results come up most often, each tied to a real operation.

Clean rows from every document. New Document Processed sends each parsed document to a sheet or a CRM, one record per document, tables flattened.

Files fed in from anywhere. Create Document From File takes a PDF or a spreadsheet that landed in another app and drops it into a Parseur mailbox for extraction.

Nothing silently stuck. New Document Not Processed and New Document Export Failed warn someone when a document needs a new template or its export did not go through.

One detail decides how fast things move. Five of the six triggers are instant: Parseur tells Zapier itself. Only New Mailbox polls, so on the free plan it can lag by up to the plan interval. What Zapier does not do for Parseur: there is no search, so a Zap cannot look up an older document, and no action edits or deletes a document or a mailbox. The same mailboxes can also be wired through Make: see the Parseur Make integration.

Vocabulary

Zapier vocabulary in one minute

Eight words come back all over this page. Here they are once, in plain English, so the rest reads without a dictionary.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan is a count of those.
Polling vs instant
Polling: Zapier checks the app on a timer and keeps only what is new. Instant: the app reports the event itself, so nothing waits.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
Search step
A step that looks up something already stored in an app, so the steps after it can reuse what it found.
Connection
Your account on an app, linked to Zapier once, then reused by every step that touches that app.
Cost

What Parseur on Zapier really costs

Zapier bills in tasks, and the rule is shorter than the pricing page suggests: the trigger is free, each action that works counts once.

  • Trigger0 tasks
  • Each successful action1 task
  • Failed actionNot counted
  • Free plan100 tasks a month, 2-step Zaps

Watching for new events never costs a task, however often Zapier checks. An action that fails is not counted either. A few apps and actions do use more than one task per run, so keep an eye on the counter early on. The free plan gives you 100 tasks a month, unlimited Zaps and two steps per Zap: one trigger, one action. Add a second action, a filter or a search step and the Zap turns multi-step (any Zap beyond one trigger and one action), which takes a paid plan. Parseur is open to the free plan. Five Parseur triggers are instant and ignore the grid below; only New Mailbox polls, so it follows your plan's interval.

Connect

Connect your Parseur account to Zapier

  1. 01

    Open Apps and add a connection

    On the Apps page of your Zapier account, click + Add connection. One connection covers all eight Parseur operations, whether a Zap reads from a mailbox or sends a file into one.

  2. 02

    Find Parseur and confirm

    Look up Parseur in the dialog, select it and click Add connection. Zapier attaches an existing Parseur account, the one that holds your mailboxes; it will not sign you up.

  3. 03

    Sign in and grant access

    A Parseur tab opens: sign in and give Zapier access. If a mailbox you want to use was set up by someone else, or the Zap writes to a tool you do not own, your account needs access to it before you build.

First Zap

Your first Parseur Zap, step by step

GoalEach delivery note Parseur processes lands as a row in your stock sheet, but only when it meets your condition.

  1. 01

    Pick the trigger

    In the editor, pick Parseur as the app and New Document Processed as the event that starts the Zap, then choose your Parseur connection and the Mailbox to watch.

  2. 02

    Test with a real document

    Run the test. Zapier brings back the three most recent items from your connected account, so you map real parsed values instead of guessing their shape.

  3. 03

    Add the filter

    Add a Filter from the plus icon, then in Configure & test pick one of the fields your Parseur template extracts, a rule and a value. This step makes the Zap multi-step, so it needs a paid plan; on the free plan, leave it out.

  4. 04

    Add the action

    Add Google Sheets with Create Spreadsheet Row and map the Parseur values into your columns. Test it, then open the sheet and check the row before you publish.

  5. 05

    Publish

    Publish the Zap to switch it on. Each document processed in that mailbox from then on adds its row. For larger builds, there is a Zapier training.

Triggers

The six Parseur triggers

6 events start a Zap when something happens in Parseur, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Document Export Failed

Instant trigger

In Zapier“Triggers when the parsed data export of a document failed.”

Parseur read the document, but sending its data on to the destination you set up did not work. This trigger turns that silent failure into a Zap run you can act on.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you rely on Parseur exports for invoicing or orders and someone has to know the same day when one did not arrive.
Watch out
it only covers the Mailbox picked in its settings, so check that it is the one your exports leave from.
2

New Document Not Processed

Instant trigger

In Zapier“Triggers when a document was not parsed (new template is needed).”

Some documents come in that Parseur cannot read with the templates it has. This one fires on exactly those, the ones waiting for a new template.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a new supplier starts sending invoices in a layout you have never seen, and the person who builds templates should hear about it.
Watch out
the Mailbox setting is required; documents in other mailboxes do not count.
3

New Document Processed (With List Items)

Instant trigger

In Zapier“Triggers when a new document is successfully parsed. Table fields are actual lists.”

Fires each time Parseur parses a document successfully, keeping table fields as real lists rather than squashing them into columns.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
the next step knows how to handle line items one by one, for example a tool that adds each order line separately.
Watch out
if your destination expects one flat record, use New Document Processed instead.
4

New Document Processed

Instant trigger

In Zapier“Triggers when a new document is successfully parsed. Tables, if present, are flattened.”

The everyday trigger: a document parsed with success starts the Zap, and any tables inside it arrive flattened.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want one row or one record per document, the simplest way to fill a sheet or a CRM.
Watch out
flattened tables are easy to map but awkward when the line count varies from one document to the next.
5

New Table Field Processed

Instant trigger

In Zapier“Triggers when a document is parsed and contains new row(s) in the selected table field.”

Here the focus narrows to one table field: the Zap starts when a parsed document contains new rows in the table field you selected.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
only the lines of a table matter, such as the items of a purchase order headed for your stock tool.
Watch out
it needs both a Mailbox and a Table field, so the table must already exist in that mailbox's template.
6

New Mailbox

Polling trigger

In Zapier“Triggers when a new mailbox is created.”

Unlike the five others, this trigger is about your Parseur setup, not your documents: it starts the Zap when a new mailbox is created.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
you keep an inventory of mailboxes for the team, or want a channel message each time a colleague adds one.
Watch out
being the only polling trigger here, it can lag behind the event by up to your plan's interval.
Actions

The two Parseur actions

Parseur gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Document

Action

In Zapier“Creates a new document in your mailbox.”

Drops text from an earlier step into a Parseur mailbox as a fresh document, named after whatever subject or title you map in.

When to use it
text that arrives somewhere else, like a form reply, should be parsed by Parseur like any email.
Watch out
both the Mailbox and the Name are required.
2

Create Document From File

Action

In Zapier“Creates a new document in your mailbox from a file such as PDFs, Emails or Excels.”

Hands Parseur a file picked up by an earlier step, a PDF, a saved email or an Excel sheet, so the mailbox reads it like anything else it receives.

When to use it
attachments land in a shared drive or an inbox and you want Parseur to read them without forwarding by hand.
Watch out
it requires a Mailbox and a File from an earlier step.
When it breaks

When the Parseur Zap breaks

Zapier links no help article to Parseur, and the app page states no Parseur limit. The cases below are general Zapier rules, which play out a little differently here because Parseur mixes five instant triggers with one polling trigger.

Parseur already hands you two triggers to catch its own failures, New Document Not Processed and New Document Export Failed, so wire one of them to a channel before anything else. For trouble on the Zapier side, the Zapier troubleshooting page is the next stop.

  • Nothing from before the switch-on

    Documents Parseur processed before the Zap went live never reach it, and neither do mailboxes created earlier. Pulling that history across is a separate job; the Zap only handles what comes next.

  • A Zap that keeps setting itself off

    If a Create Document step writes into the very mailbox a processed-document trigger watches, each run creates a new document, the Zap starts again and tasks drain fast. Write into another mailbox.

  • A sudden flood gets held back

    Forward a whole archive into a mailbox at once and New Document Processed can report a huge batch in one go. Zapier's flood protection may then hold those runs back rather than fire them all.

  • Duplicates are kept out on New Mailbox

    On New Mailbox, the polling trigger, Zapier remembers what it has already seen, so the same mailbox does not start the Zap twice, however many checks run.
Need help

Need help automating Parseur with Zapier?

A person reads every message.

FAQ

Parseur and Zapier: the questions people ask

01Is the Parseur Zapier integration free?
Yes. Parseur is open to the Zapier free plan: 100 tasks a month, unlimited Zaps, two steps per Zap. A Zap from New Document Processed to one spreadsheet row fits, and so does a trigger from another app followed by Create Document From File. What the free plan cannot hold is a third step, such as a filter that keeps only certain documents, or a row plus an alert: that makes the Zap multi-step and needs a paid plan. No prices here, they change too often; check the current Zapier plan table.
02How many tasks does a Parseur Zap use?
None for the trigger, whichever of the six you use. Zapier counts a task only when an action completes successfully. A two-step Zap that turns each processed document into one spreadsheet row costs one task per document. Add a second action, say a chat message, and each document costs two tasks, since every successful action counts on its own. On the other side, each Create Document or Create Document From File that works counts as one task in the Zap that runs it. A failed action is not billed, and a few apps and actions use more than one task per run.
03Does Parseur work in real time with Zapier?
Mostly, yes. Five of the six triggers are instant: Parseur tells Zapier itself when a document is processed, left unprocessed or fails to export, or when a table field gets new rows, so the Zap starts straight away on any plan. New Mailbox is the exception. It is a polling trigger: Zapier checks on a timer, every 15 minutes on the free plan, 2 on Professional, 1 on Team and Enterprise. In the editor, Zaps built on instant triggers show a lightning bolt, so you can tell at a glance which kind you picked.
04What do you need to connect Parseur to Zapier?
A Parseur account with at least one mailbox already set up, since five triggers and both actions ask for a Mailbox. The link itself: the Apps page in Zapier, + Add connection, Parseur, Add connection, then sign in on the tab that opens and grant access. That connection serves every later Parseur Zap, reading or writing. New Table Field Processed also needs its table field to exist in that mailbox. If the Zap writes into a tool someone else owns, that person has to give your account access first.
05Which Parseur trigger should you use for processed documents?
It depends on what the next step can handle. New Document Processed flattens tables, so each document arrives as one record with columns: the easy choice for a sheet or a CRM. New Document Processed (With List Items) keeps table fields as real lists, which suits a step that handles each line on its own. New Table Field Processed starts only when a chosen table field gets new rows, and needs both a Mailbox and a Table field. Not sure? Test each: the test brings back the three most recent items, so you see the shape before mapping.
06What if the Parseur operation you need is not on Zapier?
Then it is not on Zapier, and no setting brings it in. Parseur's visible list there is six triggers and two actions, with no search: a Zap cannot look up an older document, and no action edits or deletes a document or a mailbox. Template work and mailbox settings stay inside Parseur. If one of those steps has to be automated, check first whether Make or another automation tool offers it for Parseur before you build around the gap.
07Zapier, Make or n8n for Parseur?
Decide on criteria, not on a ranking. Zapier covers Parseur in both directions: five instant triggers, one polling trigger, and two actions that feed mailboxes. Look at the trigger first: if your flow starts on New Mailbox, the 15-minute check of the free plan applies. Then billing: one task per successful action, two steps on the free plan. Then compare: which Parseur operations Make and n8n expose, whether they can search past documents, and what your exact flow would cost per document there.
Same platform

Other docs you might need on this stack.

Browse all integrations