Content & Documents · Integration
Onna
Add Onna to your product for your customers, and give your AI agents governed access to it.
Embed an Onna integration so your product can work with the content a customer has already collected and indexed rather than reaching into a dozen source systems itself. Onna, now part of Reveal, indexes data from sources like Slack, Google Workspace, Microsoft 365, Confluence and Jira into searchable collections, and legal and IT teams use it for eDiscovery, information governance and archiving. The units that matter are sources, indexed files and their metadata, collections and exports. Each customer authorises their own Onna account, so searches and reads run under their grant and their existing access rules apply rather than being widened by your integration. fastn owns the auth, token refresh, pagination, rate limits and API upkeep, and the same governed connection is what your AI agents use.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Onna account so your product can search across their indexed content with no per-customer code.
Read a file and its metadata from a collection so your product shows the original context rather than a copy nobody can trace.
Read collection and export detail per tenant so your product can report what was gathered for a matter and when.
Support customers whose sources and collection structures differ as per-tenant configuration rather than a branch in your code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent runs a scoped search across one customer's indexed content and cites the files it used, with every read audited.
An agent summarises what a collection contains before a reviewer opens it, reading only that tenant's account.
An agent reports which sources have been indexed for a customer and when they were last refreshed.
Example prompt
Search our indexed Slack and email content for mentions of this vendor last quarter and list the files you found.
Set up Onna in 4 steps
- 01Enable the Onna connector in your fastn dashboard.
- 02Have each customer authorise their own Onna account so searches and reads run under their credentials and permissions.
- 03Map the source, file, metadata and collection fields your product uses, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Onna integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Onna integration without building it. Your customers connect their own Onna 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 Onna update is not your on-call problem.
- One integration serves your product and your agents. The same governed Onna 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
BoxWorks well with
Google Vault
SlackOften used alongside
Tools the same teams tend to run next to Onna, across other categories.
Shopify
Stripe
Jira
AsanaOnna integration FAQ
How do I add an Onna integration to my product?
Enable the Onna connector in your fastn dashboard, then let each customer authenticate their own Onna account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Onna client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Onna account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Onna 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 Onna integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent runs a scoped search across one customer's indexed content and cites the files it used, with every read audited.
Who maintains the Onna integration?
fastn does. When Onna 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 Onna integration run under?
Each customer's own Onna grant. Where Onna 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 Onna automatically?
Where Onna 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 Onna integration?
A common starting point: let each customer connect their own Onna account so your product can search across their indexed content with no per-customer code. 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 Onna integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Onna does not change your per-connector cost. You can start free with 3 connected accounts.
Add Onna to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.