Alerts V2 Parameters

[halsgbs]

Hi, I'm working on using Databricks python SDK to create an alert using a notebook, but it seems with V1 there is no way to add subscribers and with V2 there is no option for adding parameters. Is my understanding correct or am I missing something? And if correct, is there a plan to add parameters to V2 soon? Thanks! 

[emma_s]

Hi, yes your assumption is correct, there is no currently no way of adding parameters to an alert.  This is a commonly requested feature, but as yet is not in the roadmap. There is potential it will come in Q2/Q3 once the feature is GA.

Here is an overview of functionality. 

Question	Databricks SDK V1	Databricks SDK V2
Add subscribers (recipients) at creation?	No (only via Jobs API)	Yes
Add parameters/parameterized alerts?	Yes (with jobs, templates)	No (not yet supported)
Supported by Databricks Asset Bundles (DABs)?	Unofficial/workarounds	Yes (as of Dec 2025)
Add alert as task in Jobs?	Yes	In progress/not yet GA

[iyashk-DB]

Alerts V2 (Public Preview) do not support query parameters yet. This is a documented limitation. Legacy alerts (V1) do support parameters and will use the default values defined in the SQL editor.

For notifications, both legacy alerts and Alerts V2 allow notifying users and notification destinations, so adding subscribers is supported in both.

If you’re using the Python SDK or REST APIs, parameterized alerts must still be created using the legacy (V1) APIs, since parameters are not available in V2 yet. There’s no published timeline for when parameter support will be added to V2.

Recommended workaround: continue using legacy alerts if parameters are required, or switch to Alerts V2 only if you can avoid parameters (for example, by using constants or reading values from a table/view).

[halsgbs]

Thanks. I cannot avoid parameters for my use case, so I must use legacy alerts. But my issue with legacy alerts currently is that I can't add emails of recipients using the python sdk. You mentioned this is possible, do you mind telling me how please? I can't seem to find this specific part in the documentation.