Connect a webhook

What you need

• An address that accepts a POST with JSON, starting with https://. Most automation tools give you one (see Examples).
• Admin rights in your UAT Studio workspace.

Connect your webhook

2

Add the webhook in UAT Studio

Open your workspace, click Connections, choose Webhook under Add a connection and click Add. Then fill in:

• Webhook address: the address from step 1.
• Send automatically:
  • Only when I click Send on an issue (the default): an admin decides which issues go out.
  • Every new issue and every status change, by itself: everything goes out straight away.

Click Save settings. The choice under Send automatically is saved as soon as you change it.

{ "event": "test", "message": "Test message from UAT Studio" }

When it sends

An issue merged into another one as a duplicate doesn't send a new issue.created.

What it sends

A POST with Content-Type: application/json. All issue events have the same shape:

{
  "event": "issue.status_changed",
  "project": { "id": "6b1f…", "name": "CRM UAT" },
  "issue": {
    "id": "a41c…",
    "key": "ISS-012",
    "title": "Save button greyed out",
    "description": "After changing the phone number, Save stays grey.",
    "severity": "High",
    "priority": "High",
    "status": "Ready for retest",
    "assignee": "Dev team",
    "ticket": "PORTAL-41",
    "ticket_url": "https://acme.atlassian.net/browse/PORTAL-41"
  },
  "test_case": { "num": 4, "title": "Edit a contact", "step": 3 },
  "reported_by": "Tess Tester",
  "from": "In progress",
  "to": "Ready for retest",
  "url": "https://app.uat.studio/p/6b1f…/issues"
}

Fields can be null and we may add fields later, so let your flow ignore what it doesn't know. Screenshots and files are never sent; they stay in UAT Studio.

Building the receiving end

Power Automate

1. Create an Instant cloud flow with the trigger When an HTTP request is received, for Anyone.
2. Under Request Body JSON Schema, click Use sample payload to generate schema and paste the example above.
3. Add a Condition on event (for example: is not equal to test), then the actions you want: a Planner task, a row in Excel, a mail, an item in SharePoint.
4. Save the flow. The trigger now shows the HTTP URL: that is the webhook address.

Note: the HTTP trigger is a premium connector in Power Automate. For posting in a Teams channel you don't need it: use the Microsoft Teams connection.

Zapier

Create a Zap with the trigger Webhooks by Zapier › Catch Hook, copy the address, click Test connection in UAT Studio and then send one issue, so Zapier learns the fields. Then add the action you want, such as a message in Slack.

Make

Start a scenario with Webhooks › Custom webhook, copy the address and click Redetermine data structure before you send an issue from UAT Studio.

Your own service

Accept a POST with JSON, check the Authorization header against your secret, answer 200 quickly and do the slow work afterwards. Messages are not sent again after a failure, so log what you receive.

If something goes wrong

Still stuck? Mail [email protected] with the message you see. Never send us the secret itself.

What leaves UAT Studio

• Messages go out over HTTPS only.
• They contain the issue text, the test and the name of the tester, never files or screenshots. Send them only to a service your organisation trusts with that information.
• The secret is stored encrypted (AES-256), with the key kept separately from the database. Nobody can read it back.
• Switch the connection Off or remove it, and nothing is sent any more.