Notification Type
Custom notification delivery channel.
❯
open diagram →How Notification Type runs at request time
Every microservice CX type walks the same auth + Headless flowchart — validate token, run logic, decide whether to call Headless as the user or escalate to a server token. See it animated.
# 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 |
|---|---|---|
resourcePathrequired | string | Delivery handler path. |
oAuth2ApplicationExternalReferenceCoderequired | 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: