{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":19977,"path":"impact/io-receive-notification-third-party.md","title":"Configure alert notifications for a third-party application","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure alert notifications for a third-party application\n\nSet up a basic integration between Instance Observer \\(IO\\) and third-party integrations to route IO alert notifications to an external system in addition to emails and SMS.\n\n## Before you begin\n\nRole required: admin\n\n**Important:** Third-party integrations are not supported in Regulated Market.\n\n## About this task\n\n**Note:** Third-party integrations support platforms such as Slack, Microsoft Teams, AWS, GCP, and Azure.\n\nFor Third-party integrations, webhook URLs may expire if a subscription is not renewed, or API keys may be invalid over time. Ensure that your integration credentials are kept up to date to avoid missed alert deliveries.\n\n## Procedure\n\n1.  Navigate to **Impact** &gt; **Platform Health** &gt; **Monitor** &gt; **Go to Instance Observer**.\n\n2.  Log in to Instance Observer and navigate to **Alerts** &gt; **Configure Notification**.\n\n3.  Select **+ Create Integration**.\n\n4.  On the form, fill in the fields.\n\n    For a third-party integration, enter the following:\n\n<table id=\"table_vt4_ww5_z3c\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nIntegration type\n\n</td><td>\n\nThird-party. ServiceNow is selected by default.\n\n</td></tr><tr><td>\n\nIntegration Name\n\n</td><td>\n\nName to identify the integration.\n\n</td></tr><tr><td>\n\nAuthentication Type\n\n</td><td>\n\nBasic Authentication or an API key for the integration.For API Key, provide the key or username and password for the integration.\n\n</td></tr><tr><td>\n\nUser name\n\n</td><td>\n\nUser name associated with the integration.\n\n</td></tr><tr><td>\n\nPassword\n\n</td><td>\n\nPassword for the integration.\n\n</td></tr><tr><td>\n\nEnter URL\n\n</td><td>\n\nWebhook URL as configured on your third-party \\(external\\) application.For more information, see [Create a scripted REST API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/t_CreateAScriptedRESTService.md)\n\n</td></tr></tbody>\n</table>    \\[Omitted image \"io-webhook-third-party-integ.png\"\\] Alt text: Create a webhook integration for a third-party application.\n\n5.  Select **Test Integration** to validate your configuration and verify if you can successfully send the payload to the configured application.\n\n    If you do not have the correct URL details at hand, you can save the integration as **Draft** and return to complete it later.\n\n    -   If the test is successful, you receive a `HTTP response 200 is successful` response. You can now proceed to submit the integration.\n    -   If the test fails, an error message is displayed in red. Review and correct your integration details—such as the webhook URL, username, or password—and test again.\n\n        **Important:** A successful test result is required before you can submit the integration. If you attempt to submit without testing, a validation message is displayed: `Successful Test Integration results required to submit your integration, or save as draft if you don't have a working URL.`\n\n6.  **Submit** the integration and save it when the test is successful.\n\n    The integration is created with a status **Enabled**.\n\n7.  Verify the integration status.\n\n    In the **Integrations** tab, confirm that the integration status shows as **Enabled**.\n\n    **Note:** Only integrations with an **Enabled** status appear in the **Notification Rules** tab to link with the notification rule. Draft integrations are not available for selection until they are completed and enabled.\n\n8.  To configure a notification rule for the third-party integration and send alerts to third-party applications, select the **Notification Rules** tab.\n\n    1.  Select \\[Omitted image \"ellipsis-horizontal-outline-24.svg\"\\] Alt text: ellipsis icon. for the notification rule, and select the **Edit** option.\n\n    2.  Enter a name for the rule in the **Name** field of the Edit Rule pop-up.\n\n    3.  Enter a description for the notification rule.\n\n    4.  Select the **Third Party Integration** option as the **Notification Type** and select a value from the list.\n\n    5.  Select **Save**.\n\n9.  Verify alert payload delivery in the **Alert Console** by navigating to **Alerts** &gt; **Alert Console**.\n\n    To confirm that your integration is working correctly after an alert is triggered:\n\n    1.  Select your instance and **Get Snapshot** in the **Alert Console**.\n\n    2.  From the **Generate Test Alert** list, select the alert you configured.\n\n        The test alert that you configured appears in the list. For example, **Database Response Time** alert on your instance.\n\n    3.  Verify that the alert payload is successfully delivered to the configured integration endpoint, which is third-party instance.\n\n        The alert payload reaches the third-party instance so long as the webhook URL accepts the HTTP calls.\n\n    4.  Check if the alert with the specified payload has reached its intended destination.\n\n        If the alert had failed, then you will see that the **Alert Type** is in red, which means it has failed. On selecting the failed **Self-Service** alert icon you will see the message **Third Party Integration – Failed**.\n\n10. To view, edit, or delete the URL in the Edit Integration pop-up, navigate back to **Alerts** &gt; **Configure Notifications** and select \\[Omitted image \"ellipsis-horizontal-outline-24.svg\"\\] Alt text: ellipsis icon. for the integration.\n\n    You can update the integration settings by selecting the **Edit** option. The **Delete** option remains inactive if the integration is associated with at least one notification rule.\n\n11. Identify and resolve integration failures.\n\n    If an integration fails after it has been enabled, for example, due to an expired webhook URL, an invalid API key, or expired credentials, then IO detects the failure and flags it for your attention. To identify and resolve a failed integration:\n\n    1.  In the **Alert Console**, look for alerts displayed in red under the **Alert Type** column. A red indicator means the alert payload failed to deliver the notification.\n    2.  Select the **Failed** link to view the full error details. For example, a `404` error indicating that the URL is invalid or the API key has expired.\n    3.  Select **Update Integration** to edit the integration with the correct credentials or webhook URL, test it successfully, and resubmit to restore the integration to **Enabled** status.\n    4.  Alternatively, you can navigate to **Alerts** &gt; **Configure Notification**, and select the integration with Failed status in the **Integration** tab. **Edit** the integration configuration, test the integration, and when it is successful, resubmit it to restore the integration to the Enabled status.\n    The **Delete** option remains inactive if the integration is associated with at least one notification rule.\n\n    **Important:** Until the integration is fixed and re-enabled, alert payloads will not be delivered to the failed endpoint.\n\n    -   **IO alert notification channels**\n\n        You can view the integration failures as alerts in three places:\n\n        1.  As **Alert Type** in **Alert** &gt; **Alert Console**\n        2.  As Notifications from \\[Omitted image \"io-bell-icon.png\"\\] Alt text: bell icon. Select **View Notification History** and filter with `Integration Failed`.\n        3.  As an email notification with the integration name, error number, and the message.\n\n**Parent Topic:**[Use alerts to monitor your instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/impact/io-alerts-intro.md)\n\n"}}