Send notifications for test plan results

This page explains how to use Autify Nexus to send test plan execution results to external tools (Slack, Microsoft Teams, and more) via Webhooks.

When you configure Webhooks notifications, a request is sent to the specified URL when the test plan execution finishes, so you can share results in your team’s chat tool.

How to use

1. Prepare a Webhook URL in an external tool

Before you configure notifications in Nexus, create a Webhook URL in the destination tool. Refer to each tool’s documentation for detailed steps.

• Slack

• Microsoft Teams

2. Add a webhook to a test plan

1. Click the target test plan to open the details page.

2. In the Webhooks section, click Add webhook.

3. In the screen that appears, configure the following:

   1. Condition: Select when to send a notification after execution completes.

      • Always send: Send regardless of the execution result.

      • If all tests passed: Send only when the entire test plan succeeds.

      • If tests failed: Send when the overall test plan result is anything other than success.

   2. URL: Paste the Webhook URL you obtained in Step 1.

   3. Headers: (Optional) Configure this when sending notifications to an external system with specific requirements such as authentication.

      • Click Add custom header, and enter any string in Header name and Header value.

      *Repeat this step to configure multiple headers.

   4. Format: Select a format that matches your destination tool.

      • Slack message

      • Microsoft Teams message

      • Google Chat message

      • Plain-text chat message: POST as plain text

      • Raw JSON request: Send detailed test results as JSON (for custom integrations)

   5. Language

      • If you select anything other than Raw JSON request, you can choose the language for the notification message.

4. After you finish entering the settings, click Add.

5. Click Save at the top of the screen to save your test plan changes.

Notes

• You can configure multiple Webhooks for a single test plan. You can separate conditions and destinations for each webhook.

• Even if sending a webhook fails, it does not affect whether the test execution itself succeeds or fails (only the notification fails).

• Webhook requests have a timeout, so notifications may fail for destinations with slow responses.

• When using custom headers, you must know in advance the HTTP header names and values required by the destination system.

• If you enter sensitive information such as authentication tokens in the Header value of a custom header, handle it carefully as it will be saved as part of the test plan settings.

• Custom headers must be configured individually for each webhook in a test plan.