---
sourceDocument: Australia Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/impact

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Custom payload in alerts integration

# Custom payload in alerts integration {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

Instance Observer integrations enable you to define and manage custom JSON request payload for ServiceNow and third-party integrations.
You can now include additional fields in notification payloads, exclude specific data that is not required by the target system, format the payload to align with specific third-party API requirements or internal business logic,
eliminating the need for complex scripted REST APIs on the customer side.

* Use either the default payload or customize it to include additional data as needed.
* Modify the default payload, if needed, which is displayed in the Editor window on the left.
* Modify either the key or the value, or both as each parameter consists of a key and a value.
* The Preview section on the right displays the expected JSON payload after rendering.
* If the JSON is invalid, errors are highlighted, and the option to save is disabled.
{#custom-payload-help-guide-impact__ul_c33_xdz_bfc}

## Default mustache payload template {#custom-payload-help-guide-impact__section_xvl_sfz_bfc}

    {
      "alert_number": "{{alert_number}}",
      "alert_type": "{{alert_type}}",
      "alert_name": "{{alert_name}}",
      "alert_time": "{{alert_time}}",
      "instance": "{{instance}}",
      "description": "{{description}}",
      "alert_created": "{{alert_created}}"
    }

## Example: Default Payload + Custom Parameters {#custom-payload-help-guide-impact__section_lnr_c3z_bfc}

    {
    "alert_number": "{{alert_number}}",
      "alert_type": "{{alert_type}}",
      "alert_name": "{{alert_name}}",
      "alert_time": "{{alert_time}}",
      "instance": "{{instance}}",
      "description": "{{description}}",
      "alert_created": "{{alert_created}}",
      "Custom_message": "{{alert_name}}' of type {{alert_type}} generated for {{instance}} at {{alert_time}}. Please review.",
      "Severity": "High"
    }

## Custom parameters and limits {#custom-payload-help-guide-impact__section_jky_hjz_bfc}

The custom_parameter field allows you to insert custom message into the JSON template, you can also use the existing parameters as shown in the custom parameter samples.  
The limitations are:

* Required: At least one and at most 20 parameters to save the template.
* Maximum: 13 custom parameters.
* If exceeded, a warning appears: Template must have at least one default key and up to 20 keys. Adjust or select 'Reset to Default' to apply defaults.
{#custom-payload-help-guide-impact__ul_ln1_pjz_bfc}

## Samples of custom parameters for syntax reference {#custom-payload-help-guide-impact__section_yhl_slz_bfc}

"Information": "An alert {{alert_name}} has been triggered for {{instance}} at {{alert_time}} Description: {{description}}"

"Alert_message": "New alert '{{alert_name}}' of type {{alert_type}} generated for {{instance}} at {{alert_time}}. Please review."

"Event_type": "Severity-High! An alert {{alert_name}} has been triggered for {{instance}} at {{alert_time}} Description: {{description}}"

## Third-party request body mapping {#custom-payload-help-guide-impact__section_cgb_1wm_cfc}

Some third-party integrations require specific key names. You can modify the default payload to match their expected format.  
Example: Third-party request body:

    {
      "endTime": 1,
      "entitySelector": "string",
      "eventType": "AVAILABILITY_EVENT",
      "properties": {},
      "startTime": 1,
      "timeout": 1,
      "title": "string"
    }

## Modified IO payload to match third-party format {#custom-payload-help-guide-impact__section_gzv_xvm_cfc}

## Actions and validation {#custom-payload-help-guide-impact__section_wsz_xmz_bfc}

Revert Changes
:   Restores the last saved content.

Reset to Default
:   Resets the template to its default payload.

Syntax Validator
:   Ensures JSON validity before saving. Errors prevent saving.

Test Integration
:   Sends a sample notification to verify webhook integration.