Send Novu service notifications with AI
Trigger an existing Novu workflow for a subscriber, a topic or a defined batch. Keep the intended audience, event payload and transaction identifier explicit.
Send Novu service notifications with AI when an application event has to trigger a workflow you already configured. The novu-trigger-notification skill covers single events, batches of individual events, topic delivery and environment-wide broadcasts. The workflow determines which configured channels deliver the message.
A receipt for one order needs the right subscriber and order fields. A planned maintenance notice might belong to an authorised project topic. A broadcast reaches everyone in the environment, so test with a narrow recipient first. Subscriber membership alone does not establish permission for a separate marketing campaign.
What it does
- Send a single order-status event.
- Batch events with different payloads for different customers.
- Notify the subscribed members of a project topic.
- Use a transaction ID for idempotency and cancellation.
- Cancel a delayed or digested notification while it is pending.
Install and use
- Install the skill and configure an authorised Novu environment, server-side secret and active workflow. Use the official API client or REST endpoint and begin with a test recipient.
- Ask, “Trigger the order update in our test environment for this subscriber only. Include the order reference and reuse its transaction identifier.”
- Verify recipient scope, workflow ID and delivery status before using the same integration for live service messages.
FAQ
Source
Made by Novu. Original skill: novu-trigger-notification, published on GitHub under the MIT licence.
View on GitHub