> ## Documentation Index > Fetch the complete documentation index at: https://docs.worldvisagroup.com/llms.txt > Use this file to discover all available pages before exploring further. # Notification event > Understand the WorldVisa notification lifecycle and the key entities - workflows, triggers, subscribers, jobs, and messages - that make up a notification. In WorldVisa, notifications are the core building blocks of your product’s communication experience. When your user receives a message via an in-app alert, an email, or a push notification, what they’re seeing is the final output of a notification. Notifications represent the complete journey of a message triggered by an event in your application and delivered to a specific user across one or more channels. They encapsulate all the execution logic and delivery metadata in a single traceable unit. ## Notification lifecycle A notification doesn't exist in isolation, it’s the result of a sequence of interconnected entities working together. Here’s how it works in WorldVisa: ![Notification lifecycle](https://mintcdn.com/wv-enterprise/l3bkwl1N_3mOn9aW/images/developers/concepts/notifications/notification-life-cycle.png?fit=max\&auto=format\&n=l3bkwl1N_3mOn9aW\&q=85\&s=3ba1625b2529947581a557e6dbb0a946) ### Event Something meaningful happens in your application, such as a user signing up, a password reset being requested, or a comment being posted. You emit this event to WorldVisa using the Event Trigger API. Each event contains: * A name that maps to a specific workflow (user\_signed\_up) * A payload with dynamic data * One or more subscribers * Optional overrides or metadata This is how your application tells WorldVisa, “It’s time to send something.” ### Workflow WorldVisa matches the incoming event to a predefined workflow. This workflow is your logic for determining: * What channels to use (email, in-app, SMS, etc.) * What message templates to render * When and how messages should be sent The workflow is where message personalization, conditional logic, and multi-channel orchestration happens. > [!TIP] > > Refer to the [Workflows documentation](https://docs.worldvisagroup.com/developers/concepts/workflows.md) to learn more. ### Notification Once the workflow starts executing, WorldVisa creates a notification for each subscriber involved. This notification acts as the central entity tracking everything that happens - every job, message, and delivery status. It includes: * The subscriber details * The workflow (template) used * The event payload * Jobs executed * Messages generated * Delivery status updates and errors Think of it as the container for all activity triggered by a single event for a single user. > [!NOTE] > > In simpler terms, when a workflow is triggered to a subscriber, it creates an event. One event is one notification. ### Message Each channel step in the workflow results in one or more messages. These are the actual pieces of content sent to users' emails, push notifications, SMS, and in-app alerts. Messages are live entities, tracked in real-time, with full visibility into: * Rendering logic * Channel used * Delivery status * Provider responses or errors > [!NOTE] > > Each message has a unique ID and status, learn more about this in the Messages API. ## Notification structure A notification in WorldVisa is more than just a message, it’s a full record of what happened from the moment an event was triggered to when one or more messages were delivered or failed to deliver. Each notification encapsulates a set of properties that describe its creation, context, execution, and result. These properties are essential for debugging, analytics, and tracking user communications. ### Notification properties | Property | Description | | - | - | | `transactionId` | A unique identifier for this specific notification execution run. Useful for tracing across APIs and logs. | | `template` | The workflow (template) that was executed. Defines the steps and channels used. | | `subscriber` | The user who received the notification. Includes subscriber ID and metadata. | | `payload` | Dynamic data passed in from the event, used to render personalized message content. | | `jobs` | A list of steps (jobs) that were executed as part of the workflow. Each job corresponds to a workflow action, for example, send email or run delay. | | `messages` | The individual messages generated for each channel. Contains delivery status, content, and provider response. | | `status` | The current execution state of the notification (`pending`, `completed`, `failed`, and so on). | These fields are accessible via the Notifications API and are also displayed in the WorldVisa dashboard’s Activity Feed for visual traceability. ## Frequently asked questions These are some of the most frequently asked questions about notifications in WorldVisa. > [accordion] What is the difference between a notification and an event? > > A notification is the result of an event. An event is the trigger of a workflow to a subscriber that causes a notification to be created. > [accordion] What is the difference between a notification and a message? > > One notification event can have multiple messages as per the workflow configuration. Messages are the actual "notification message" to the end user. ## Related topics - [WorldVisa Developer Platform](https://docs.worldvisagroup.com/developers/overview.md) - [How do workflows work in WorldVisa?](https://docs.worldvisagroup.com/developers/concepts/workflows.md) - [Notification Click Behavior](https://docs.worldvisagroup.com/developers/inbox/advanced-customization/notification-click-behavior.md) - [Activity Tracking](https://docs.worldvisagroup.com/developers/integrations/push/push-activity-tracking.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.