---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Configure a push connector

# Configure a push connector {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Configure a push connector

This guide explains how to configure push connectors and listeners to send event information to your ServiceNow instance or MID Server for Event Management.
Event Management supports event collection through various methods including push connectors, scripts, SNMP traps, email, and direct instance or MID Server integration.
Proper configuration enables Event Management to receive and process external events effectively.
Show full answer Show less  

## Key Configuration Steps

* **Integration User Creation:** Create a dedicated integration user with the `evtmgmtintegration` role and ensure the user's Identify Type is set to Machine. This user authenticates event collection.
* **Standard Event Form:** All incoming events must conform to a standard event form format, regardless of delivery method, to ensure consistent processing.
* **Plugin Requirement:** To use push connectors, install the Event Management Connector plugin from the ServiceNow Store.

## Event Collection Modes

Event Management supports multiple event collection modes provided by the base system and the Event Management application, including:

* Listeners and connectors for popular platforms like AWS CloudWatch, Azure Monitor, BMC TrueSight, Datadog, Dynatrace, Google Cloud Platform, and New Relic.
* Generic event collection via MID Server or directly to the instance, including XML-based messages with example transform scripts.
* MID WebService API for pushing events to the MID Server.
* Custom listeners and transformations through MID WebServer API or custom payloads.
* SNMP trap listeners (e.g., SNMPv2) and email listeners for event collection.

## Practical Benefits for ServiceNow Customers

Configuring push connectors enables seamless ingestion of external event data into ServiceNow Event Management, improving your ability to monitor, manage, and respond to IT events from diverse sources. It supports both out-of-the-box integrations and custom event sources, providing flexibility for your operational environment.  
You can configure listeners and connectors to push event information to the instance
or MID Server.

Event Management receives external events through a push connector or script. If
you are using a script to collect events, no configuration is required. All other
methods of collecting events require configuration.  
After event collection configuration, Event Management can collect events that are sent directly to the instance, or via the MID Server, SNMP trap, or email.  
Note:  
Integrating with push connectors is only available by installing the Event Management Connector plugin from the ServiceNow Store.

## Create integration user {#push-event-listener__section_fsc_sgw_ckc}

Follow the steps in [Creating users](https://www.servicenow.com/docs/access?context=ua-creating-users&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US) to create a user and grant the \[evt_mgmt_integration\] role to the user.  
Note:  
Verify that the Identify Type of the user is Machine.

## Standard event form

All events must use a standard event form, regardless of how they arrive at the instance. For more information, see [Event field format for event collection](https://www.servicenow.com/docs/pMEhhjHwyBoERY_6mX39FA "Event Management requires all events to use a standard form, regardless of how they arrive at the instance.").

## Event collection

Event Management facilitates communication and movement of data between external applications, data sources, services, and the ServiceNow AI Platform instance.{#push-event-listener__simpletable_av2_cxd_gz__entry__2}

| Event collection modes | Description |
|-|-|
| Provided by the base system | Listeners and connectors provided with the Event Management application: * AWS CloudWatch, see [Integrate AWS platform as a data source](https://www.servicenow.com/docs/aSdW53fb2EftB6dZpu2NHg "Integrate Amazon Web Services (AWS) with Event Management. To add AWS platform as a data source, configuration is required in the AWS platform."). * Azure event messages, see [Integrate Azure Monitor as an authenticated data source](https://www.servicenow.com/docs/6Ti_PdYMk1TtoICH4rCU_g "Integrate Microsoft Azure with Event Management by adding the Azure Monitor as an authenticated data source."). * BMC TrueSight events, see [Event collection from BMC TrueSight and BMC TrueSight_v2](https://www.servicenow.com/docs/5GG5u0x8lzrVaa3xEhPRIg "The MID WebService Event Collector enables you to collect JSON formatted event messages sent from BMC TrueSight Operations Management (TrueSight), previously known as BMC ProactiveNet Performance Management (BPPM). It uses event stream notification capabilities."). * Datadog events, see [Integrate Datadog platform events](https://www.servicenow.com/docs/W7_7e17WtCcd8LYZvBAYfg "Integrate Datadog with Event Management by adding a standard webhook in the Datadog console."). * Dynatrace events, see [Integrate Dynatrace platform events](https://www.servicenow.com/docs/ulTYG8gtCf4aiUW6nZTnMA "Integrate Dynatrace with Event Management by adding Dynatrace as an authenticated data source."). * Google Cloud Platform (GCP) events, see [Integrate Google Cloud Platform (GCP) events](https://www.servicenow.com/docs/f0KAxcQ9Lub6dbg9Tg28Ww "Integrate Google Cloud Platform (GCP) with Event Management by adding a standard webhook in the GCP console.") * New Relic events, see [Integrate New Relic platform events](https://www.servicenow.com/docs/ItqDI5VwzXRCSID_H7VsCA "Integrate New Relic with Event Management by adding a standard webhook in the New Relic old and new consoles."). * Generic event collection through the MID Server. * Generic event collection through the instance. {#push-event-listener__ul_bvm_qrl_gz}Where event messages are received in XML, you can base your script on the example XML transform script provided with the base system. |
| Via MID WebService | You can configure the MID WebService Event Collector to push event messages to the MID Server. For more information, see [Pushing events to the MID Server using web service API](https://www.servicenow.com/docs/F~u2IbKEQZ_HVfShDk5znQ "Configure the MID WebService Event Collector to provide a URL method to push event messages to the MID Server."). |
| Create your own content | You can configure your own listener: * Via MID WebServer API. See [Pushing events to the instance using web service API](https://www.servicenow.com/docs/jcphLYYrWC6m3GBvok8OrA "You can use a web service interface, supported by ServiceNow, that operates on the JSON object as the data input and output format."). * Via Custom Transformation. See [Event collection from custom payloads](https://www.servicenow.com/docs/FePVMb_fpMQYQj9~cDcdMg "The MID WebService Event Collector enables you to collect event information from custom payloads in JSON, XML, or plain text format."). {#push-event-listener__ul_j1r_1sl_gz} |
| Via SNMP | SNMP listeners provided with the Event Management application: Generic SNMPv2. See [Configure event collection for SNMP traps](https://www.servicenow.com/docs/puBMOXCoLwKyKUAFNp6lRA "The SNMP listener runs on the MID Server, which acts as a collection endpoint for SNMP traps. The MID Server sends the traps to the ServiceNow instance for further processing as an event by Event Management."). In addition, you can create your own custom listener. See [Integrate with push connectors](https://www.servicenow.com/docs/~iZZoToVk_C_QcvSav4dQA "Integrate with a push connector to connect to an external event source. Push connectors process the collected event messages and transform them to the required event format."). |
| Via Email | Email listener. See [Configure event collection from email](https://www.servicenow.com/docs/lDVZp9zfRRof9SunV7ZsdQ "Configure an inbound email action to send email notifications when events and alerts are triggered."). |
[ ]

{#push-event-listener__simpletable_av2_cxd_gz}
**Related reference**   

* [Push connector instance form](https://www.servicenow.com/docs/2x7gKDLoHOlSp5enhtnmqA "Push Connector Instance form displays the fields that you must fill when you create or modify a connector.")

