Add note about Legacy webhooks (#2595)

grafana · Jul 20, 2023 · bf3ea1e · bf3ea1e
1 parent 48db34d
commit bf3ea1e
Showing 1 changed file with 9 additions and 0 deletions.
diff --git a/docs/sources/outgoing-webhooks/_index.md b/docs/sources/outgoing-webhooks/_index.md
@@ -13,6 +13,15 @@ weight: 500
 
 # Outgoing Webhooks
 
+> ⚠️ A note about **(Legacy)** webhooks:  Webhooks that were created before version **v1.3.11** are marked as
+> **(Legacy)**.  Do not worry! They are still connected to their respective escalation chains and will continue to to
+> execute as they always have.
+> <br/><br/>
+> The **(Legacy)** webhook is no longer editable due to changes to the internal representation. If you need to edit it
+> you must use the `Make a copy` action in the menu and make your changes there.  This will create the webhook in the
+> new format.  Be sure to change your escalation chains to point to the new copy otherwise it will not be active. The
+> **(Legacy)** webhook can then be deleted.
+
 Outgoing webhooks are used by Grafana OnCall to send data to a URL in a flexible way. These webhooks can be
 triggered from a variety of event types and make use of Jinja2 to transform data into the format required at
 the destination URL. Each outgoing webhook receives contextual data when executed which can be processed by