--- 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 an event push connector # Configure an event push connector {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Integrate with an event push connector to connect to an external event source and push event information to your ServiceNow instance. ## Before you begin Role required: evt_mgmt_admin ## Procedure 1. Navigate to WorkspacesService Operations Workspace. 2. From the navigation pane, select the AIOps configuration center icon ![ITOM AIOps configuration center icon](). The ITOM AIOps configuration center page appears. The configuration center is a centralized workspace. Use it to configure and manage AIOps features from a single place. 3. On the ITOM AIOps configuration center page, under the SetupIntegrations section, select Manage Installed integrations. 4. In the Browse Integrations tab, select the All integrations drop-down list and select Push. Only push connector tiles are displayed. Figure 1. Push connectors 5. Select a push connector type tile. 6. Provide details about the connector type on the Provide details screen. Figure 2. Push connectors details page 1. In the Connector name field, enter a unique name for the connector type. 2. **Optional:** In the Tags field, enter tags to help locate and identify connectors of this type on the Express List. To add additional tags, select the plus sign next to the Tags field. The Add tags window opens. 1. In the Key field, enter a tag key. 2. In the Value field, enter a tag value. 3. Select Add. {#push-connector__ol_fzm_l3w_mbc} 3. **Optional:** In the Description field, enter information to help identify this connector type. 4. Verify that the vendor name in the Source field is correct. 5. **Optional:** From the Assignment group drop-down list, select the group or team that is responsible for managing and maintaining the Push connector. 6. Select Next. The connector is saved in draft mode, and the process advances to the Set-up push connector section. {#push-connector__substeps_hyg_lzd_vzb} 7. In the URL parameter value field, select Copy to clipboard to copy the auto-generated URL parameter value to the clipboard. This URL is generated by the code that depends on the ServiceNow instance and connector type to receive events from the third-party connector. Pasting the URL in your third-party connector configuration creates a webhook that enables it to send events to the ServiceNow instance. 8. In the Select authentication method, select the authentication type. Integration Launchpad shows authentication options based on the supported authentication types. You can either create new credentials, if you have the required roles, or select from existing credentials. * Basic: Sends a username and password (Base64-encoded) with each request. The user_admin role is required to create new Basic Auth credentials. The drop-down list displays users who have the evt_mgmt_integration role. Users with the evt_mgmt_admin role are excluded from the drop-down. * OAuth: Grants apps limited, token-based access to resources without sharing credentials, using scoped, expiring access tokens. The oauth_admin role is required to create new OAuth client credentials. * API Keys: Uses a unique secret key to identify and authorize an application or user when calling an API. Creates a new API key credential. Associates the API key with the sn_em_connector.integration user, which is exported as part of the plugin. {#push-connector__ul_aq3_1yv_3kc} 9. Select Activate and then select OK. 10. In the Details tab, view the connector details and the URL link. Integration Launchpad uses these fields to render the latest error details for the push connector instance: * Last error time: Stores the timestamp of the latest error. This uses the glide_date_time field type, allowing the Details page to show when the last failure occurred. * Last error message: Stores the latest error message returned for the push connector instance. This read-only string field has a maximum length of 4,000 characters. * Last error payload: Stores the detailed error payload associated with the latest failure. This read-only string field has a maximum length of 10,000 characters. {#push-connector__ul_r2r_nyv_3kc} 11. Follow the step-by-step instructions to integrate your third-party connector with Event Management. The connector is saved and a notification is sent after the connector is active. {#push-connector__steps_srm_zfk_5wb} ## What to do next To confirm the successful configuration of the pull connector and the flow of events into the system, go to the Related events tab. If the setup is successful, proceed to Add automation to establish an alert automation. For details on Related events tab, see [Review integration and configuration health](https://www.servicenow.com/docs/J~zWvArGQYkze~WWD2b99A "Review your events to ensure alerts are created as intended. Start this process by checking the health status of your integration. This provides useful statistics to highlight where you can make improvements. You can enrich alerts with relevant business context, group them for better noise reduction, escalate critical alerts promptly, and notify your team for swift response and resolution.") and for information on alert automation, see [Alert automation in Service Operations Workspace for ITOM](https://www.servicenow.com/docs/Q6UexC2xawi9XYPPwXUCYA "Alert automation is crucial as organizations deal with increasing number of alerts and complex IT infrastructures. Manual alert handling is slow, error-prone and inefficient, underscoring the need for automated systems. Automation can improve the mean time to resolve alerts, improve service reliability and better scale staff resources."). *[\>]: and then