> For the complete documentation index, see [llms.txt](https://docs.seedata.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seedata.io/features/alerts.md). # Alerts Each alert will be configured to send a specific formatted messages, to a defined destination, under a certain trigger condition. ### List of Existing Alerts A list of all Alerts you have already configured for your organisation is available on [https://app.seedata.io/alerts](/welcome.md) Each existing alert can be edited or deleted by clicking on the actions menu to the right side of the table \[...] ### Alerts Marketplace If you want to add a new alert, click the ADD NEW button to the top right, or go directly to our Alerts Marketplace, on Each tile can be clicked on to show further details on how the alert integration works, plus a filtered list of any installed instances of that alert integration. The pages below this provide further detail on the features of each Alert integration. If there's an alert integration you really want us to add, let's talk ()
### Custom Alert Templates We provide a default payload for any alert integrations you make. This will include the basic essentials including a link back to the event in the seedata.io platform. You may prefer to customise this though, either to make certain data available, or to better suit the expected format of your intended recipient (a webhook with a specific schema, for example) You can do this whilst configuring the alert integration, with the ability to add any text or seedata.io built-in variable. ### Baseline Events Opt-In All alerts can be configured to include "Baseline Events", or not. A typical event will have a Priority allocated of between 1 to 5 (read more [here](/features/events.md)) and will be sent to all configured alerts. We also make use of "Baseline" to denote events that we consider not of any priority. This will be used for events where the source is already whitelisted, or if the event is generated as a test by a user on the seedata app. Turning on this toggle for baseline events opt-in means that this alert will also be used for any baseline events --- # 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, and the optional `goal` query parameter: ``` GET https://docs.seedata.io/features/alerts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.