If SQL Server Audit is used to capture changes on instances, objects, and data, there is a way to create an appropriate alert by utilizing SQL Server Agent jobs. A job should be scheduled to perform as often as possible, every minute for instance, but that depends on how often you need to check the appropriate SQL Server Audit repository file (a .sqlaudit file, application logs, or security logs) in search of important event. The job should execute a stored procedure that reads and analyzes the repository, and finds the events that you want to raise alerts for. If you’re storing audit logs into a file, use the fn_get_audit_file function to read it.
In case the events are found, an email can be sent with appropriate message. Note that for sending emails SQL Server Database mail must be enabled and set properly.
Downsides of this method are that it requires advanced T-SQL knowledge, it can use significant SQL Server resources depending on the schedule frequency and the size of the repository that needs to be read each time, and it has to be manually set up for each event type and database.