Content & Documents · Integration
Liferay
Add Liferay to your product for your customers, and give your AI agents governed access to it.
Embed a Liferay integration so your product can work with the documents and web content your customers already publish, in place. Access runs through each customer's own Liferay grant, so their existing permissions apply and your product cannot read content the connected account could not read itself. fastn handles per-customer authentication, pagination over large libraries and API upkeep, so an unusual site structure is configuration rather than code.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Liferay instance so your product works with the content they already publish.
Read and write files in document folders under the permissions the connected account already has.
Create or update web content so a page changes without someone copying text between systems.
Read versions so your product can show what changed, when, and by whom.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a document to answer a question grounded in the customer's own content.
An agent files a generated document into the right folder within governed permissions.
An agent compares versions of a page and explains what changed, with each read logged.
Example prompt
Find documents in this folder changed in the last month and summarise what is different in the latest version.
Set up Liferay in 4 steps
- 01Open the Liferay connector from your fastn dashboard.
- 02Have each customer authenticate their own Liferay instance.
- 03Map the sites, folders and content types your product may access, then enable actions.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Liferay integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Liferay integration without building it. Your customers connect their own Liferay 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 Liferay update is not your on-call problem.
- One integration serves your product and your agents. The same governed Liferay 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
Adobe Experience Manager
Contentful
BoxOften used alongside
Tools the same teams tend to run next to Liferay, across other categories.
Shopify
Stripe
Jira
AsanaLiferay integration FAQ
How do I add a Liferay integration to my product?
Enable the Liferay connector in your fastn dashboard, then let each customer authenticate their own Liferay account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Liferay client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Liferay account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Liferay 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 Liferay 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 reads a document to answer a question grounded in the customer's own content.
Who maintains the Liferay integration?
fastn does. When Liferay 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 Liferay integration run under?
Each customer's own Liferay grant. Where Liferay 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 Liferay automatically?
Where Liferay 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 Liferay integration?
A common starting point: connect their own Liferay instance so your product works with the content they already publish. 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 Liferay integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Liferay does not change your per-connector cost. You can start free with 3 connected accounts.
Add Liferay to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.