AI Document Extraction

Parseur, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Parseur account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • AI Document Extraction
  • Connects with a key
  • 10 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Parseur is

Parseur is an AI-powered data extraction tool that automates the parsing of emails, PDFs, and other documents into structured data.

You paste in a key from your own Parseur account. It is kept encrypted, and you can withdraw it from inside Parseur whenever you like.

How a run works

One message in, the work done in Parseur.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Parseur. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Parseur account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

10 tools it already has

What it can do in Parseur

These are the ready-made tools your AI employee already has in Parseur. It is not limited to them, but it never has to be taught these.

  • Create webhookTool to create a new webhook in parseur. use when you need to send parsed data via http post in real time.
  • Delete webhookTool to delete a specific webhook. use when permanently removing a webhook after confirming its id.
  • Enable webhookTool to enable a paused webhook for a mailbox. use after confirming the webhook is correctly configured.
  • List Documents in MailboxTool to list documents within a specific mailbox. use when you need to paginate, search, or sort the documents of a given mailbox after obtaining its id.
  • List MailboxesTool to retrieve a list of all mailboxes. use when you need to browse or filter mailboxes via pagination, searching, or sorting.
  • List Templates for MailboxTool to list all templates in a given mailbox. use after fetching mailbox details when you need to page through and inspect available templates for further actions.
  • List Webhooks for MailboxTool to list all webhooks for a mailbox. use when you need to retrieve both active and paused webhooks for a given mailbox.
  • Pause webhookTool to pause (disable) an existing webhook. use when you need to stop sending parsed data via a webhook after confirming the correct mailbox and webhook ids.
  • Retrieve a webhookTool to retrieve details of a specific webhook. use after creating or listing webhooks.
  • Update webhookTool to update an existing webhook’s settings. use when you need to change the webhook’s target url, event type, headers, or name after creation.
Access, and who is in charge of it

You stay the boss of your Parseur account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Parseur account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Parseur is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Parseur and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

Questions people ask about Parseur

Can an AI employee really work inside Parseur?
Yes. It signs in to your own Parseur account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Parseur?
No. Nothing moves and nothing is replaced. Your records stay in Parseur, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Parseur account?
You paste in a key from your own Parseur account. It is kept encrypted, and you can withdraw it from inside Parseur whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Parseur?
It has 10 ready-made tools in Parseur today, among them Create webhook, Delete webhook and Enable webhook. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Parseur and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Parseur and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Parseur?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Parseur is written down with what it did and when.