What it is: You can now customize the JSON body and headers sent by webhook alert notifications and integrations in Atlas and Cloud Manager. Using simple ${field} syntax, you can shape the outgoing webhook payload and headers to match the exact format your receiving system expects.

Who it's for: Atlas and Cloud Manager customers using webhook notifications who need alert payloads to match a specific schema, such as internal incident management tools, ChatOps systems, or other services that expect a particular JSON structure.

Why it matters: Previously, webhook payloads used a fixed MongoDB format, often requiring a custom translation layer to reformat data for the receiving system. Now you can format the payload and headers directly, removing that extra integration step. If a custom template fails to render, MongoDB automatically falls back to the default payload so your notifications keep flowing.

How to get started: Configure custom templates directly in the Atlas or Cloud Manager alert configuration UI, using the "Test" button to preview the rendered output before saving. This is also available via the Atlas Admin API.