Webhook event types

content/docs/platform/developer/environments.mdx

@@ -4,16 +4,14 @@ description: 'Understanding and managing environments in Novu'
 icon: 'GitFork'
 ---
 
-Novu uses environments to separate your workflows and it's data. This lets you safely test changes, like a new workflow, in one environment before moving it to a live production environment.
+Novu uses environments to separate your workflows and its data. This lets you safely test changes, like a new workflow, in one environment before moving it to a live production environment.
 
 ## Types of environments
 
-When you create a Novu account, you are provided with a development and production environment by default. You can also create custom environments (on certain plans) to match your team’s workflow.
+When you create a Novu account, you are provided with a development and production environment by default. On certain plans, you can also create custom environments to match your team’s workflow.
 
 - **Development environment**: Use the development environment to build and test new workflows, layouts, translations, and experiment with different configurations before publishing to other environments.
-
-- **Production environment**: The production environment is used to send notifications to your subscribers. To ensure stability and prevent unintended changes, this environment is view-only for workflows, layouts, and translations. Changes are not made here directly, they are made from the development environment and then published to production.
-
+- **Production environment**: The production environment is used to send notifications to your subscribers. To ensure stability and prevent unintended changes, this environment is view-only for workflows, layouts, and translations. Changes are not made here directly, they are made from other environment and then published to this production environment.
 - **Custom environment**: Custom environments are only available on <a href="https://novu.co/pricing" target="_blank" rel="noopener noreferrer">Team and Enterprise plans</a>. You can use them to reflect your release process, for example, staging or QA.
 
 ## Create a custom environment
@@ -70,7 +68,7 @@ Each environment has two unique identifiers:
 
 <Callout>Configure these credentials in your application based on the active environment, similar to how you manage other service credentials.</Callout>
 
-## Publishing changes to other environments
+## Publish changes to other environments
 
 Novu provides a publish mechanism that allows you to promote changes from your development environment to production or other custom environments. This process ensures that all changes are deliberate, reviewed, and deployed in a controlled manner.
 

content/docs/platform/developer/webhooks/event-types.mdx

@@ -0,0 +1,37 @@
+---
+title: 'Event types'
+pageTitle: 'Webhooks event types'
+description: 'Learn more about the types of events that Novu sends webhook events for.'
+---
+
+Novu supports the following webhook event types:
+
+- **Message events**: Events about message delivery status changes.
+- **Preference event**: Event about subscriber preference changes.
+- **Workflow events**: Events about workflow creation, updates, and deletions.
+
+Each event includes detailed information about the affected resource and the changes that occurred.
+
+## Message events
+
+- `message.archived`: This webhook is triggered when a subscriber archives a message. The payload contains the details of the event.
+- `message.delivered`: This webhook is triggered when a message delivery provider acknowledged the message delivery to the end receiving client. The payload contains the details of the event.
+- `message.failed`: This webhook is triggered when Novu tries to send the message to the delivery provider and it got failed. The payload contains the details of the event.
+- `message.read`: This webhook is triggered when a message has been read by the subscriber. The payload contains the details of the event.
+- `message.seen`: This webhook is triggered when a subscriber opens a message. The payload contains the details of the event.
+- `message.sent`: This webhook is triggered when Novu sends the message to the delivery provider. The payload contains the details of the event.
+- `message.snoozed`: This webhook is triggered when a message is snoozed by the subscriber. The payload contains the details of the event.
+- `message.unarchived`: This webhook is triggered when an archived message is unarchived. The payload contains the details of the event.
+- `message.unread`: This webhook is triggered when a message is unread or marked as unread by the subscriber. The payload contains the details of the event. 
+- `message.unsnoozed`: This webhook is triggered when a message is unsnoozed by a subscriber. The payload contains the details of the event.
+
+## Preference event
+
+- `preference.updated`: This webhook is triggered when a subscriber preference is updated. The payload contains the details of the event.
+
+## Workflow events
+
+- `workflow.created`: This webhook is triggered when a workflow is created. The payload contains the details of the event.
+- `workflow.deleted`: This webhook is triggered when a workflow is deleted. The payload contains the details of the event.
+- `workflow.published`: This webhook is triggered when a `workflow` event occurs, that is when a workflow is synced from dev to prod environment. The payload contains the details of the event. 
+- `workflow.updated`: This webhook is triggered when a workflow is updated. The payload contains the details of the event.