> For the complete documentation index, see [llms.txt](https://docs.3q.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3q.video/user-guide-new-ui/modules/notifications.md). # Notifications The **Notifications** module allows you to create automated notifications and workflows for selected events in 3Q.
Notifications can be used to inform users or external systems when specific actions happen, for example when a new file has been processed, file metadata has changed, or a file has been deleted. Depending on the selected notification type, notifications can be sent by: * Webhook * Email * SMS This makes the module useful both for technical integrations and for editorial or operational alerts. From the Notifications module, users can: * View existing notifications * Create new notifications * Select the project the notification applies to * Select the event that should trigger the notification * Choose the notification type * Configure webhook, email, or SMS notifications * Filter notifications by project or type The Notifications module is available from the main navigation under **Modules**. *** ### Notifications Overview The Notifications overview displays all configured notifications in a table. Each row represents one notification and includes the most relevant information: * Notification ID * Title * Assigned project * Trigger event * Notification type * Creation date At the top of the page, users can switch between different views: * **All Notifications**\ Shows all configured notifications. * **Only for On-Demand**\ Shows notifications assigned to on-demand projects. * **Only for Podcasts**\ Shows notifications assigned to podcast projects. * **Only for Livestreams**\ Shows notifications assigned to livestream projects. The overview also provides search and filter options. Available filters include: * **Type**\ Filters notifications by notification type, such as webhook, email, or SMS. * **Project**\ Filters notifications by the assigned project. *** ### Creating a Notification To create a new notification: 1. Open **Modules** in the main navigation. 2. Select **Notifications**. 3. Click **Create Notification**. 4. The **Create Notification** side panel opens. 5. Enter a **Title**. 6. Select the **Project**. 7. Select the **Event** that should trigger the notification. 8. Select the notification **Type**. 9. Configure the type-specific settings. 10. Optionally add a **Description**. 11. Click **Save**. After saving, the notification appears in the overview and is triggered automatically when the selected event occurs. *** ### Notification Settings #### Title The **Title** is the internal name of the notification. Choose a clear title that describes the purpose of the notification. Example titles: * Webhook – New File Processed * Email Alert – File Deleted * SMS Alert – Livestream Event * Metadata Update Notification * Processing Workflow Trigger #### Project The **Project** defines where the notification is active. The available projects are grouped by project type, for example: * On-demand projects * Podcast projects * Livestream projects The selected project also determines which events are available for the notification. #### Event The **Event** defines what action triggers the notification. Available events depend on the selected project type. For on-demand file workflows, events include: * **New File Processed** * **New File in Pipeline** * **File Metadata Updated** * **File Source Updated** * **File Deleted** and many other events, also for podcasts or livestream projects. #### Type The **Type** defines how the notification is sent or executed. Available notification types include: * **Webhook** * **Email** * **SMS** The selected type determines which additional configuration fields are displayed. *** ### Webhook Notifications Webhook notifications are used to send event information to an external system. This is useful for building automated workflows and integrations, for example with a CMS, MAM, automation platform, monitoring system, or custom backend. When using a webhook notification, 3Q calls the configured endpoint when the selected event occurs. Typical webhook use cases include: * Triggering an external publishing workflow * Informing a CMS that a new video is ready * Updating an external database when metadata changes * Starting a downstream automation after processing * Synchronizing deleted files with another system Depending on the configuration, the webhook request method, such as **GET**, can be selected. *** ### Email Notifications Email notifications send an email when the selected event occurs. They are useful for editorial, support, or operational teams that need to be informed about important changes without connecting an external system. Typical email notification use cases include: * Informing editors when a new file has been processed * Notifying a team when metadata has been updated * Alerting responsible users when a file has been deleted * Sending operational updates for selected projects *** ### SMS Notifications SMS notifications send a text message when the selected event occurs. They are useful for time-sensitive workflows where users need to be informed quickly. Typical SMS notification use cases include: * Critical livestream-related alerts * Important processing notifications * Operational escalation workflows * Urgent project-specific events *** ### Building Automated Workflows Notifications can be used to build automated workflows around 3Q events. For example, when a new file is processed in an on-demand project, a webhook can notify an external system. That system can then publish the video, update a website, trigger a review workflow, or start additional processing. This allows 3Q to be connected to external tools and systems without requiring manual checks. Example workflow: 1. A new video is uploaded to a project. 2. The file is processed by 3Q. 3. The **New File Processed** event is triggered. 4. A webhook notification is sent to an external endpoint. 5. The external system continues the workflow automatically. *** ### Managing Existing Notifications Existing notifications can be reviewed in the Notifications overview. Depending on user permissions, users can open, edit, or delete notifications. When editing a notification, review the selected project, event, and type carefully. Changes may affect automated workflows or alerting behavior. *** ### Typical Use Cases Notifications can be used for different workflows, for example: * Sending an email when a new file is processed * Sending an SMS for urgent livestream-related events * Triggering a webhook when file metadata changes * Informing external systems when a file is deleted * Connecting 3Q with CMS, MAM, or automation systems * Building project-specific processing workflows * Notifying teams about content changes *** ### Notes The available events depend on the selected project type. The available notification types and configuration options may depend on the account configuration, enabled modules, and user permissions. For webhook workflows, make sure that the external endpoint is reachable and can process the event data sent by 3Q. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.3q.video/user-guide-new-ui/modules/notifications.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.