When should I use the Notification Type client extension type?

• You want to deliver Liferay notifications through a channel Liferay doesn't ship (SMS, Slack, WhatsApp). • You need central logging or throttling for notifications via your own service.

How do I create a Notification Type client extension?

1. Ship a paired `oAuthApplicationUserAgent`. 2. Implement delivery at `resourcePath`.

What fields are required on a Notification Type client extension?

resourcePath (string): Delivery handler path. oAuth2ApplicationExternalReferenceCode (string): Ref code of the paired `oAuthApplicationUserAgent`.

Notification Type

Custom notification delivery channel.

type: notificationType·Microservice·Liferay docs →

# description

Registers a delivery channel Liferay's notification engine can use — SMS, Slack, third-party push service. Your endpoint receives the payload and delivers it.

Externalize business logic — actions, validation, workflow, notifications.

# when to use

→You want to deliver Liferay notifications through a channel Liferay doesn't ship (SMS, Slack, WhatsApp).
→You need central logging or throttling for notifications via your own service.

# how to use

01Ship a paired oAuthApplicationUserAgent.
02Implement delivery at resourcePath.

# required fields

field	type	description
`resourcePath`required	`string`	Delivery handler path.
`oAuth2ApplicationExternalReferenceCode`required	`string`	Ref code of the paired `oAuthApplicationUserAgent`.

# optional fields

field	type	description
`name`	`string`	Display name.

# example

client-extension.yaml

slack-notify:
    type: notificationType
    name: Slack
    resourcePath: /notify
    oAuth2ApplicationExternalReferenceCode: my-oauth-ua

# related types

Usually shipped alongside Notification Type:

❯OAuth Application (User Agent)— Register a browser / SPA OAuth application.

# more in microservice

cd ..scaffold this type in VS Code →