Learn how to configure and implement notification functionality in your business processes using the FlowX.AI Notifications Plugin.
KAFKA_TOPIC_NOTIFICATION_INTERNAL_IN
(default: ai.flowx.plugin.notification.trigger.send.notification.v1
) - Topic for notification requestsKAFKA_TOPIC_NOTIFICATION_INTERNAL_OUT
(default: ai.flowx.engine.receive.plugin.notification.confirm.send.notification.v1
) - Topic for notification responsesKey | Definition | |
---|---|---|
templateName | The name of the notification template to use | Mandatory |
channel | Notification channel: SMS/MAIL | Mandatory |
receivers | Notification recipients: email addresses or phone numbers | Mandatory |
language | The language code of the template to use (e.g., “en”, “fr”) | Mandatory |
contentParams | Parameters for filling the template with dynamic content | Optional |
senderEmail | Email address of the notification sender | Optional |
senderName | Name of the notification sender | Optional |
attachments | Files to attach to the notification (only for MAIL notifications) | Optional |
${...}
to insert data from the process context${application.client.firstName}
retrieves and displays the client’s first nameCreate a notification template
Design the BPMN process
Configure the send message task
KAFKA_TOPIC_NOTIFICATION_INTERNAL_IN
environment variableflowx-notifications-devmain
contentParams
(object) for dynamic content, attachments
(array) for emailsConfigure the receive message task
KAFKA_TOPIC_NOTIFICATION_INTERNAL_OUT
environment variableai.flowx.updates.devmain.notification.request.v1
KAFKA_TOPIC_NOTIFICATION_INTERNAL_OUT
environment variable.Run and verify the process
KAFKA_TOPIC_NOTIFICATION_INTERNAL_OUT
topicKAFKA_TOPIC_NOTIFICATION_INTERNAL_OUT
topic similar to this:Missing Kafka topics
Notification not received
Template rendering issues
Dynamic key not resolving
Attachment problems