Capability

Integration

Liferay is designed to be standards-compliant and highly interoperable. Connect Liferay DXP with external systems using SOAP, REST, GraphQL, and more to unite third-party software, legacy systems, and data.

Headless APIs, Remote Apps (Client Extensions), API Builder, and integrations with SSO platforms are some of the examples of the features in this area.

Category
Category
Using Zapier to Sync Object Data with Google Sheets
This recipe guides you through the steps required to use webhooks to trigger sync tasks between Liferay Objects and Google Sheets using Zapier.
Add-ons and Connectors
Add-ons and Connectors
HubSpot Lead Capture
HubSpot Lead Capture Subscription The HubSpot Lead Capture connects Liferay to the HubSpot CRM software. You can synchronize Liferay Objects data automatically to ensure the instant availability...
Configuring the MuleSoft Connector
Configuring the MuleSoft Connector Liferay's connector to MuleSoft uses OpenAPI 3.0 documents that describe Liferay's APIs. Each OpenAPI document is deployed dynamically in your Liferay instance...
Salesforce
Salesforce Deprecated in Liferay DXP 2024.Q4/Portal GA129 Subscription Liferay DXP 7.4 U35+ The Liferay Connector to Salesforce uses Talend job designs and Liferay's Job Scheduler to import data...
Installing HubSpot Lead Capture
Installing HubSpot Lead Capture Installing the Liferay connector HubSpot Lead Capture requires integrating a Liferay client extension and a Spring Boot micro-service client extension. Follow the...
Mulesoft
Mulesoft Subscription The Liferay Connector to MuleSoft connects Liferay DXP to other platforms and services in the MuleSoft ecosystem. You can access the connector via Anypoint Studio or Anypoint...
Designing Mule Flows
Designing Mule Flows After configuring the Liferay Connector to MuleSoft, you can start building Mule flows. These operations are available for Liferay's OpenAPI endpoints. Create Records ...
Liferay Commerce Connector to TradeCentric Reference Guide
Liferay Commerce Connector to TradeCentric Reference Guide Subscription There are several configuration terms in TradeCentric (formerly PunchOut2Go). TermDescription Punch out sessionThe set of...
TradeCentric (formerly PunchOut2Go)
TradeCentric (formerly PunchOut2Go)
Liferay Connector to TradeCentric (formerly PunchOut2Go)
Liferay Connector to TradeCentric (formerly PunchOut2Go) Subscription Liferay provides a TradeCentric (formerly PunchOut2Go) connector that integrates Liferay with a user's existing TradeCentric...
Liferay Commerce 2.1 Connector to PunchOut2Go
Liferay Commerce 2.1 Connector to PunchOut2Go Subscription Liferay provides a PunchOut2Go connector that integrates with a user's existing PunchOut2Go infrastructure. You can download this...
Integration
Integration
Headless APIs
Headless APIs
Custom Object APIs
Custom Object APIs Liferay 7.4+ When you publish a custom object definition, Liferay generates default REST APIs for interacting with the object and its data. These APIs vary depending on the...
Object API Basics
Object API Basics When you publish an Object, Liferay automatically generates REST APIs for it. These APIs differ for Company and Site scoped Objects, but they all use the c/[pluralobjectlabel]...
Using Batch APIs
Using Batch APIs When you publish an Object, Liferay automatically generates REST APIs for it. These include the batch APIs for bulk POST, PUT, and DELETE operations. Here you'll use cURL commands...
Using Object APIs With Base64 Encoded Files
Using Object APIs With Base64 Encoded Files Liferay DXP 2024.Q2+/Portal GA120+ When creating object entries with attachment fields through APIs, you can generally upload files from your computer...
Managing Object Entries Using GraphQL
Managing Object Entries Using GraphQL You can use GraphQL to manage custom object entries in Liferay efficiently. This API framework simplifies data interaction and serves as an alternative to REST...
Using nestedFields to Audit Entry History
Using nestedFields to Audit Entry History Liferay 7.4 U72+/GA72+ When you enable entry history for an object definition, you can use the nestedFields parameter with REST APIs to audit entry...