Onboard a Subscriber and Send Their First Notification
A 4-step recipe with Novu. We can help you get access.
Recipe · 4 steps
Onboard a Subscriber and Send Their First Notification
with Novu
Create a subscriber then trigger and inspect their first notification.
- Create the subscriber. subscriberId is required; if the subscriber already exists it is updated rather than duplicated.
- Trigger the named workflow addressed to the newly created subscriber, passing the custom payload. Novu returns a transactionId for the trigger.
- List notification events for the environment filtered to the new subscriber, returning the most recent triggered event so its id can be resolved for a detailed lookup.
- Retrieve the full event detail (execution logs, status, generated messages) for the notification produced by the trigger.
What you'll need to have ready
- subscriberId: The external identifier of the subscriber (your system's user id).
- email: Email address of the subscriber.
- firstName: First name of the subscriber.
- lastName: Last name of the subscriber.
- workflowId: The trigger identifier of the workflow to send.
- payload: Custom payload object used to render the workflow.
For your developer
Arazzo workflow novu:onboard-subscriber-and-notify, 4 operations: SubscribersController_createSubscriber → EventsController_trigger → NotificationsController_listNotifications → NotificationsController_getNotification. Specs on APIs.io.