Content & Documents · Integration
Airparser
Add Airparser to your product for your customers, and give your AI agents governed access to it.
Airparser is built around inboxes: each inbox holds its own extraction schema, and documents reach it by email forwarding to a generated inbox address, by upload, or through the REST API at api.airparser.com with a key in the request headers. Because the schema is defined per inbox rather than globally, the JSON keys on a document's extracted data differ between inboxes, so field mapping has to be written per inbox and re-checked whenever a customer edits their prompt. Parsing is asynchronous, so a document fetched immediately after upload comes back with an empty or partial extraction and you must poll or wait for the completion callback before treating the result as final. The extraction is model-driven rather than template-driven, which means output for an unusual layout can be structurally valid but semantically wrong, and implementers usually need a confidence or review step on their side. fastn holds each customer's Airparser key separately, refreshes and rotates it, and keeps the inbox-to-field mapping working as their schemas change.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Airparser workspace so forwarded supplier emails land as structured fields in your product
Pull extracted line items from parsed invoices into your accounting screens without asking customers to re-key them
Show a per-inbox view of documents that failed extraction so an operator can correct the prompt and re-run
Trigger your own downstream workflow the moment a document finishes parsing rather than on a nightly sweep
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent which documents in a customer's inbox returned empty values for a required field over the last week
Have an agent upload a batch of PDFs to a named inbox and report which parses completed, with every call audited per tenant
Let an agent summarise the extracted data on one document and flag values that disagree with the source record
Example prompt
Which documents in our Supplier Invoices inbox parsed without a total amount this month?
Set up Airparser in 4 steps
- 01Enable the Airparser connector from your fastn dashboard.
- 02Have each customer authorise their own Airparser 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 Airparser integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Airparser integration without building it. Your customers connect their own Airparser 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 an Airparser update is not your on-call problem.
- One integration serves your product and your agents. The same governed Airparser 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 Airparser, across other categories.
Shopify
Stripe
Jira
AsanaAirparser integration FAQ
How do I add an Airparser integration to my product?
Enable the Airparser connector in your fastn dashboard, then let each customer authenticate their own Airparser account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Airparser client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Airparser account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Airparser 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 Airparser integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent which documents in a customer's inbox returned empty values for a required field over the last week
Who maintains the Airparser integration?
fastn does. When Airparser 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 Airparser integration run under?
Each customer's own Airparser grant. Where Airparser 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 Airparser automatically?
Where Airparser 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 Airparser integration?
A common starting point: let a customer connect their own Airparser workspace so forwarded supplier emails land as structured fields in your product. 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 Airparser integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Airparser does not change your per-connector cost. You can start free with 3 connected accounts.
Add Airparser to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.