Content & Documents · Integration
Parseur
Add Parseur to your product for your customers, and give your AI agents governed access to it.
Parseur organises everything under a mailbox, and each mailbox carries its own set of parsing templates and named fields, so the JSON returned for a document has a different shape in every mailbox rather than a single fixed schema. The API is token authenticated with a Token prefix and behaves like a Django REST framework service: list endpoints are paginated with next and previous links, and an unauthenticated call returns a not authenticated error rather than a plain 401 body. Documents arrive by forwarded email, upload or direct API post and land in states such as processed or quarantined, and a document that matches no template stays unparsed until a template is created or the layout is trained. Table fields come back as arrays of row objects, which is where naive flatteners break. fastn stores each customer's Parseur token, keeps their mailbox field maps separate, and handles reconnection when a token is rotated.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Parseur account and pick which mailboxes your product should read
Pull parsed invoice or order documents into your own records as soon as they reach the processed state
Surface quarantined and unparsed documents in your UI so a customer can fix a template without leaving your product
Map each mailbox's field names to your internal schema once and reuse that map for every later document
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent fetch a specific document's parsed fields and table rows to answer a question about it
Have an agent flag documents that failed to parse and summarise what was missing, without changing templates
Audit per tenant which mailboxes an agent read and which documents it opened
Example prompt
What line items did Parseur extract from the invoices that arrived in the AP mailbox yesterday?
Set up Parseur in 4 steps
- 01Enable the Parseur connector from your fastn dashboard.
- 02Have each customer authorise their own Parseur account, so calls run under their credentials rather than a shared key.
- 03Decide which files, documents and versions your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Parseur integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Parseur integration without building it. Your customers connect their own Parseur account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Parseur update is not your on-call problem.
- One integration serves your product and your agents. The same governed Parseur connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Notion
Box
DocusignOften used alongside
Tools the same teams tend to run next to Parseur, across other categories.
Shopify
Stripe
Jira
AsanaParseur integration FAQ
How do I add a Parseur integration to my product?
Enable the Parseur connector in your fastn dashboard, then let each customer authenticate their own Parseur account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Parseur client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Parseur account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Parseur account and only ever sees their own files, documents and versions. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Parseur integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent fetch a specific document's parsed fields and table rows to answer a question about it
Who maintains the Parseur integration?
fastn does. When Parseur changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose permissions does the Parseur integration run under?
Each customer's own Parseur grant. Where Parseur holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in Parseur automatically?
Where Parseur supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the Parseur integration?
A common starting point: let a customer connect their own Parseur account and pick which mailboxes your product should read. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Parseur integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Parseur does not change your per-connector cost. You can start free with 3 connected accounts.
Add Parseur to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.