Notifications

In the notifications settings, you can manage how Testiny tells your team about test activity. The page has two sections: User notifications for personal preferences, and Organization notifications for organization-wide notification channels that post into chat tools or your own HTTP endpoints.

info

Notifications are not available in the free plan. If you want to use them, please upgrade to the Starter plan or any higher tier — see our Pricing site.

Notifications can be sent for the following events:

• Test case assigned — a test case is assigned.
• Test run closed — a test run is closed.
• Test run comment — a comment is added to a test run.

User notifications

Choose how you want to be notified about events that concern you. For each event, you can pick a notification frequency per delivery method:

• Email — notifications are sent to your account's email address.
• Browser — native browser notifications (your browser asks for permission the first time).
• App — most recent 100 notifications appear in the notification inbox inside Testiny, opened via the bell icon in the top bar.
  Unread notifications are preserved for at least 14 days, read notifications for at least 24 hours after they have been read.

Notifications are sent in case they are relevant for your user:

• Test case assigned — a test case is assigned to you.
• Test run closed — a test run is closed.
• Test run commented — a comment is added to a test case that is assigned to you, or to one you have commented on before.

Click a dropdown to choose how often you want to be notified. What you pick under Organization-wide counts for all your projects. To receive more or fewer notifications about one particular project, select it under Project-specific and choose a frequency just for that project.

The following frequencies are available:

• Never — no notifications for this event.
• Immediate — each event is delivered right away.
• Shortly — similar events are combined and sent within a few minutes.
• Hourly — similar events are combined and sent out at the top of each hour.
• Daily — similar events are combined and sent out once a day. The frequency editor shows the exact delivery time in your time zone.

Notifications send out directly in the app only support Never and Immediate. The combining frequencies (Shortly, Hourly, Daily) are available for the email and browser methods.

Click Save at the bottom of the page to apply your changes.

Organization notifications

Configure organization-wide notification channels for Slack, Microsoft Teams, Discord, Google Chat, or any custom HTTP endpoint. Each channel delivers notifications to a webhook URL. Only users with the admin role can manage these.

The section shows two groups:

• Configured channels — channels that are already set up, with their type, name, and whether they are enabled. Open a channel to edit it, or remove it with the delete action.
• Available channels — channel types you can add.

To add a channel, click Add on the channel type you want, then fill in:

• Name — a friendly label that helps you tell channels apart.
• Webhook URL — the URL you obtained from the chat tool, or your own endpoint for the custom channel. (See here where to get the Webhook URL.)
• Language — the language of the notification messages sent to this channel.

Click Send test message to send a sample notification to the URL. Testiny posts a test event and shows whether the endpoint accepted it.

Click Continue to switch to the Notifications tab, where you choose a frequency for each event — with the same organization-wide default and project-specific overrides as for user notifications. Then click Save to create the channel.

After saving, open the channel from the Configured channels table at any time to change its details or notification frequencies. The Enabled checkbox on the Details tab lets you pause a channel without deleting it.

Webhook delivery

See how to obtain a webhook URL for a supported chat tool, or how to use the custom channel for your own endpoint:

info

These are third-party platforms, so their setup steps can change at any time without notice – if something doesn't match what you see, please let us know so we can update this guide.

Slack

1. Open the Slack app creation page and click Create New App → From scratch.
2. Enter an app name, pick the Slack workspace that should receive notifications, and click Create App.
3. In the app's left sidebar, select Incoming Webhooks and toggle Activate Incoming Webhooks on.
4. Click Add New Webhook to Workspace, choose the destination channel, then click Allow.
5. Copy the URL listed under Webhook URLs for Your Workspace and paste it into Testiny's Webhook URL field.

For the latest official instructions, see Slack's Sending messages using incoming webhooks.

tip

To post into a private Slack channel, you must already be a member of that channel before authorizing the webhook.

Microsoft Teams

1. In Microsoft Teams, go to the channel where notifications should arrive, select More options (⋯) next to the channel name, and choose Workflows.
2. Search for and select the template Send webhook alerts to channel.
3. Confirm the Team and Channel, then click Save.
4. Copy the URL (Copy webhook link) from the confirmation dialog and paste it into Testiny's Webhook URL field.

For the latest official instructions, see Microsoft's Create incoming webhooks with Workflows for Microsoft Teams.

Discord

1. In Discord, open Server Settings → Integrations.
2. Open Webhooks, then click New Webhook (or Create Webhook if none exist yet).
3. Click the new webhook to expand it, choose the Channel it should post to, and optionally rename the webhook or set an avatar.
4. Click Copy Webhook URL, paste it into Testiny's Webhook URL field, and click Save Changes in Discord.

For the latest official instructions, see Discord's Intro to Webhooks.

Google Chat

1. Open Google Chat in a web browser and go to the space where notifications should arrive. Webhooks can only be added to a named space, and only from the browser — not from the mobile app.
2. Click the space name at the top, then choose Apps & integrations.
3. Click Add webhooks.
4. Enter a Name - for example Testiny - optionally add an Avatar URL, then click Save.
5. Open the webhook's More menu (⋮), choose Copy link, and paste the URL into Testiny's Webhook URL field.

For the latest official instructions, see Google's Send messages to Google Chat with incoming webhooks.

tip

Incoming webhooks require a Google Workspace account — personal Google accounts cannot create them. If Add webhooks is missing, your Google Workspace administrator has not allowed incoming webhooks for your organization.

The webhook URL contains a key and a token parameter, so treat it as a secret.

Custom

Use the Custom channel to deliver notifications to your own HTTP endpoint — for example, an automation platform like Zapier or n8n, an internal service, or a workflow engine. Instead of a chat-formatted message, Testiny sends a generic JSON event envelope that you can parse and route however you like.

The endpoint must:

• Be reachable over https:// on port 443.
• Accept POST requests and answer with a 2xx status code.
• Answer directly — redirects are not followed.

Failed deliveries are retried and eventually disabled — see Retry policy.

Each event is sent as a JSON body with this shape:

{
  "event": "testiny.app_notification",
  "id": "ntf_<unique id>",
  "tenant": "<your tenant slug>",
  "timestamp": "<ISO 8601 UTC timestamp>",
  "data": {
    "type": "tc_assigned",
    "userId": 42,
    "originatorUserId": 7,
    "projId": 3,
    "projLabel": "DF",
    "projUrl": "https://app.testiny.io/DF",
    "runId": 123,
    "runLabel": "Smoke run",
    "runUrl": "https://app.testiny.io/DF/testruns/run/123",
    "tcIds": [12345],
    "tenant": "<your tenant slug>"
  }
}

The data.type field tells you which event was raised. Possible values:

• tc_assigned — a test case was assigned (Test case assigned).
• tr_closed — a test run was closed (Test run closed).
• tr_comment — a comment was added to a test run (Test run comment).

Additional fields inside data vary by event type (for example, comment events include the commenter, closed-run events include who closed the run). Treat unknown fields as informational and key your integration on data.type.

tip

Use Send test message to receive a sample tc_assigned event at your endpoint. The sample uses placeholder identifiers (project TestProject, run ExampleRun, test case 12345), which is handy for verifying your parser without waiting for a real notification.

Retry policy

A failed delivery is retried up to 5 times with an increasing delay, for a total of roughly 3 minutes. Each individual attempt times out after 15 seconds.

Only failures that might succeed on a retry are repeated:

Response from your endpoint	Behaviour
2xx	Delivered
421, 429, 500–504	Retried
Connection error or timeout	Retried
Any other status, for example 403 or 404	Dropped immediately, not retried

Channels disabled after repeated errors

Testiny counts consecutive delivery failures per channel. A single successful delivery resets that count to zero, so occasional failures never accumulate.

If more than 10 consecutive deliveries fail, the channel is disabled automatically and stops sending notifications. Its Details tab then shows Channel is disabled, along with the number of delivery errors and the last error message Testiny received.

To bring a disabled channel back:

1. Fix the cause on your side — for example a webhook URL that was rotated, or a chat channel that was deleted.
2. Open the channel and click Activate channel. Testiny marks it as enabled again and immediately sends a test message, so you can confirm the fix right away.
3. Click Save to apply the change.

Use Reset errors to clear the recorded error count and the last error message. This only clears the errors — it does not re-enable a disabled channel.