Webhook Integrations
TestingBot webhooks connect your test results to the tools your team already uses. Each integration below ships with a ready-made payload template: when you create a webhook in the members area, the Start from a template tiles prefill the HTTP method, URL, headers and payload body for the service you pick.
A template is only a starting point: every prefilled value stays fully editable, so you can tweak the payload, add variables or change the triggers before saving.
Supported services
Slack
Post a Block Kit message with the test result, browser, platform and duration to a Slack channel.
Microsoft Teams
Send a MessageCard with a facts list of test meta-data and a button that opens the test details.
Discord
Post a rich embed to a Discord channel, with the title linking straight to the test.
PagerDuty
Trigger an incident through the Events API v2 and page your on-call engineer when a test fails.
OpsGenie
Create an alert through the Alert API, authenticated with a prefilled GenieKey header.
Jira
File a Bug issue through the Jira Cloud REST API v3 with the test result and a link back to the test.
Every walkthrough covers the service-side prerequisites (where to find the webhook URL or API key), the setup steps in TestingBot, the full template payload and how to test the connection.
Build your own
If your service is not listed, switch the payload toggle to Custom and write any JSON body you like. All built-in variables work in the body, the URL, header values and query parameter values, so you can target any HTTP API that accepts JSON.
Related: follow the Quick Start to create your first webhook, or read Core Concepts for triggers, delivery and limits.
