Integrations
Endtest
Overview
This document provides a detailed guide to integrating Endtest with Callgoose SQIBS for real-time Incident Management, test-failure alerting, and automated incident resolution.
Endtest supports webhook notifications that can deliver test execution results (pass/fail, status updates, metadata) directly to Callgoose. Callgoose then uses API Filters to create and resolve incidents automatically, based on the incoming Endtest webhook payloads.
This integration enables:
- Automatic incident creation when Endtest tests fail
- Auto-resolution when tests pass again
- Centralized incident visibility for automated test pipelines
- Near real-time alert correlation between QA automation and incident response
Prerequisites
Before beginning, ensure you have the following:
- A Callgoose SQIBS account with permissions to create API Filters and access the integration endpoint.
- An Endtest account with access to Test Suites, API, and Webhooks.
- A valid Callgoose API token and API endpoint URL.
- A test case or test suite inside Endtest to validate webhook delivery.
1. Prepare Callgoose: Obtain Endpoint and Token
1.1 Retrieve Callgoose API Endpoint
Generate or locate your Callgoose process endpoint in the integration section.
Example format (Do not modify structure):
https://****.callgoose.com/v1/process?from=Endtest&token=xxxx
Store the API token securely and never commit it to source control.
2. Configure Endtest Webhook
2.1 Locate Endtest Webhook Settings
- In Endtest, webhook configuration can be done under:
- Account Settings → Webhooks
- Or Project / Test Suite-level Webhook Settings
- Endtest webhooks are capable of sending JSON event bodies whenever tests:
- Start
- Finish
- Fail
- Recover
2.2 Configure Webhook Fields
Set the following options:
- Webhook URL:
- The Callgoose endpoint from Step 1
- HTTP Method:
- POST
- Content Type:
- application/json
- Send All Test Events:
- Recommended
- Enable Notifications for:
- Test Failure, Test Success, Test Completion
Save and enable the webhook.
2.3 Verification Headers
Endtest includes the following standard webhook headers:
- X-Endtest-Event — Indicates type of event (e.g., test_failed, test_passed)
- X-Endtest-Signature — HMAC signature depending on webhook security settings
- X-Endtest-Timestamp — Test execution timestamp
If using an intermediate receiver, validate these headers before forwarding to Callgoose.
3. Example Endtest Payloads
3.1 Test Failure Payload
(Exact structure based on Endtest documentation; no assumptions.)
{
"event": "test_failed",
"test_id": "et-49215",
"test_name": "Login Test",
"suite_name": "Authentication Suite",
"status": "failed",
"browser": "chrome",
"execution_time": 42,
"failed_step": "Verify login button responds",
"timestamp": "2025-11-01T12:05:00Z",
"details": {
"environment": "staging",
"os": "windows",
"video_url": "",
"screenshot_url": ""
}
}
3.2 Test Success (Resolved) Payload
{
"event": "test_passed",
"test_id": "et-49215",
"test_name": "Login Test",
"suite_name": "Authentication Suite",
"status": "passed",
"timestamp": "2025-11-01T12:15:22Z"
}
Inspect your actual payloads inside Callgoose API Log and match JSON keys exactly in API Filters.
4. Create API Filters in Callgoose SQIBS
Callgoose API Filters convert incoming Endtest webhook payloads into incidents.
You will create:
- Trigger Filter (for failed tests)
- Resolve Filter (for passed tests)
4.1 Trigger Filter — Create Incident
Use the following settings:
- Payload JSON Key: "status"
- Key Value Contains: failed
- Map Incident With: "test_id"
- Incident Title: "test_name"
- Incident Description: Leave blank to store full JSON payload
This filter will create an incident whenever Endtest includes a failed test event.
4.2 Resolve Filter — Auto-Resolve Incident
Use the following settings:
- Payload JSON Key: "status"
- Key Value Contains: passed
- Incident Mapped With: "test_id"
This ensures the correct test incident is resolved when a success event arrives.
5. Verify and Test the Integration
5.1 Test Initial Delivery
- Create a temporary broad API filter in Callgoose
- Trigger a sample webhook using the Endtest "Send Test Webhook" option
- Confirm Callgoose receives the payload in API Logs
5.2 View Exact Payload
Use Callgoose’s API request logs to inspect JSON bodies sent by Endtest.
Make sure your filters use exact field names.
5.3 Final Verification
- Run a failing test → Incident should be created
- Re-run test until passed → Incident should be auto-resolved
- Verify the same test_id is used for both creation & resolution
6. Troubleshooting
- Incoming Payload Not Received
- Check Endtest webhook logs
- Verify the webhook URL and token
- Ensure Callgoose API Filter conditions match incoming fields
- Confirm network connectivity
- Incidents Not Auto-Resolving
- Ensure Endtest sends status=passed
- Confirm mapping uses the same test_id for both events
- Re-check filter JSON key/value
- Wrong or Missing Payload Fields
- Inspect real payloads in Callgoose logs
- Ensure Endtest is not using custom payload templates
- Update your API filters accordingly
7. Conclusion
Integrating Endtest with Callgoose SQIBS enables fully automated incident creation and resolution based on test failures and recoveries. With the Trigger and Resolve filters properly configured, teams gain real-time insights into test pipeline stability and can correlate automated testing failures directly with operational incidents.
This improves quality assurance workflows, reduces resolution time, and strengthens the reliability of CI/CD test processes.
For further customization or advanced use cases, refer to the official documentation for both Endtest and Callgoose SQIBS:
