# Liferay integrations: blog postings and documents

> Create a blog posting and upload a document in Liferay. Connect Liferay to the rest of your documents and e-signature stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/liferay-integrations/
**Categories:** Documents and e-signature
**Connects through:** HTTP Connector

## Overview

Liferay is a digital experience platform for building websites, portals and online stores, with content, documents, user accounts and commerce managed in one system. Tray.ai connects to Liferay through the HTTP Connector, so your workflows can call the Liferay API alongside the rest of your stack.

## Use cases

### Blog postings

Read, create, update, and delete blog postings in Liferay from any Tray.ai workflow. The Liferay API covers calls such as list blog postings and get a blog posting.

- List blog postings
- Get a blog posting
- Create a blog posting

### Documents

Read, create, update, and delete documents in Liferay from any Tray.ai workflow. The Liferay API covers calls such as list site documents and get a document.

- List site documents
- Get a document
- Upload a document

### Accounts

Read, create, update, and delete accounts in Liferay from any Tray.ai workflow. The Liferay API covers calls such as list accounts and get an account.

- List accounts
- Get an account
- Create an account

## Challenges Tray.ai solves

### Keeping Liferay credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Liferay credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Liferay API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Liferay API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Liferay?

Yes. Tray.ai connects to Liferay through the HTTP Connector, which calls the Liferay API directly. Any call the Liferay API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Liferay?

The Liferay API uses OAuth 2.0 and basic authentication. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Liferay connector?

Liferay runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Liferay connector from the Liferay API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/