---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-service-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Create a webhook endpoint in SR Ops

# Create a webhook endpoint in SR Ops {#ariaid-title1}

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

Create webhook endpoint so that the Application Performance Management (APM) tools
can send automated real-time messages or information to SR Ops.

## Vorbereitungen

Role required: evt_mgmt_integration

## Warum und wann dieser Vorgang ausgeführt wird

The Event Management Connectors plugin makes the APM tools available to SR Ops.  
You configured a web service account on your instance. The APM tool uses the account to authenticate the instance so it can send alerts to this service on SR Ops. In this task, you configure the following items:

1. In SR Ops:
   * Specify whether to create an incident for each alert.
   * Specify whether to send a notification to team members when an alert is received or when an incident is created.
   * Specify the APM tool that forwards alerts from the service.
   {#sro-webhook-endpoint__ul_zfp_4wm_xnb}
2. On the management console for the APM tool, configure the authentication header following settings for actions on alerts:
   * The secured endpoint to which the APM tool sends alerts.
   * The service account that the APM tool uses to send alerts. You typically use the account to generate the authentication header for the endpoint for alerts.
   {#sro-webhook-endpoint__ul_ujs_3pm_xnb}
{#sro-webhook-endpoint__ol_ryh_w4m_xnb}

## Prozedur

1. Navigate to AllSite Reliability OperationsSite Reliability Ops Workspace.
2. In the Site Reliability Ops Workspace, us one of the following methods to open a service record:
   * In the Services section on the home page (![Home page icon]()), open a service.
   * On the Services Overview page (![Services page icon]()), open a service.

   {#sro-webhook-endpoint__choices_alw_gg4_n4b}  
   The service page displays the Details, Relationships, and Integrations tabs.
3. Click the Integrations tab and then click New.
4. On the form, fill in the fields.  
   {#sro-webhook-endpoint__table_chn_2xl_xnb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the integration. |
   | Source | The push connector that will send messages from the service. SR Ops uses this information to determine how to decode incoming messages. Click the Search icon (![Search icon]()) in the Source field and then select the source to use for the service. |
   | Create incident | Option to create an incident for each received alert. |
   | Trigger notification / Notify on | Option to send notifications when an alert is received or when an incident is created. Select the Trigger notification check box to send notifications. The Notify on setting specifies whether to send the notification when an alert is received or when an incident is created. If an on-call schedule is configured for the group, then the notification goes to the on-call shift members. If no schedule is defined, then the system sends the notification to all members of the group. The system sends notifications on the channels that are specified by the sn_sro.notification_communication_channels property. See [SR Ops system properties](https://servicenow-prod.fluidtopics.net/v7FsEFdvRKUJ_pQ_jWWf2w "You configure the system properties that support operations in SR Ops.") for details. Hinweis: The base-system SR Ops application supports the actions of sending notifications when an alert is received and when an incident is created. You can define both custom actions and custom conditions that trigger an action. See [Define a custom condition to trigger actions](https://servicenow-prod.fluidtopics.net/VjHCjtmmKgrMDF_AncvCxA "The base-system SR Ops application supports the actions of sending notifications when an alert is received and when an incident is created. You can define both custom actions and custom conditions that trigger an action. Control when a flow takes a specific decision outcome or waits for a specific resume event.") and [Define a custom action](https://servicenow-prod.fluidtopics.net/c3OCfohia6d8Av5BDaIutw "The base-system SR Ops application supports the actions of sending notifications when an alert is received and when an incident is created. You can define both custom actions and custom conditions that trigger an action."). |
   [Tabelle : 1. Integrations form]

   {#sro-webhook-endpoint__table_chn_2xl_xnb}
5. Click Save.  
   The Integrations tab is replaced by two tabs: The Details and Integration Actions tabs for the new integration.
   * The Details tab displays the values that you have defined so far.
   * The base-system SR Ops application supports the actions of sending notifications when an alert is received and when an incident is created. You can define both custom actions and custom conditions that trigger an action. Custom condition/action pairs for the integration appear on the Integration Actions tab. See [Define a custom condition to trigger actions](https://servicenow-prod.fluidtopics.net/VjHCjtmmKgrMDF_AncvCxA "The base-system SR Ops application supports the actions of sending notifications when an alert is received and when an incident is created. You can define both custom actions and custom conditions that trigger an action. Control when a flow takes a specific decision outcome or waits for a specific resume event.") and [Define a custom action](https://servicenow-prod.fluidtopics.net/c3OCfohia6d8Av5BDaIutw "The base-system SR Ops application supports the actions of sending notifications when an alert is received and when an incident is created. You can define both custom actions and custom conditions that trigger an action.").
   {#sro-webhook-endpoint__ul_kqt_nn4_ynb}

   The system generates a Webhook URL that is the secured
   endpoint to which the APM should send messages. The URL appears on the
   Details tab for the integration. You copy the URL
   for use in the next step.