CI / CD

Manage CI/CD webhook keys and options under Settings → CI/CD.

Settings → CI/CD is where you create the keys that let other systems start Runs in DoesQA. Each key has a title and an Active or Inactive status. The secret is shown once when you create the key.

This page documents that settings screen. To connect a pipeline, automation platform, or custom script to DoesQA, start with the Universal Webhook in Integrations.

Why create a key

• Let GitHub Actions, GitLab CI, Bitbucket, Azure DevOps, or a script start Runs without logging into DoesQA.

• Keep one key per environment or pipeline so you can turn access off without rewriting every workflow.

• Limit notification rules to specific CI/CD keys when only some pipelines should alert the team.

Create a webhook key

1

Open CI/CD settings

In DoesQA, go to Settings → CI/CD.

2

Create a key

Choose Create, then set:

Field	What it is
Title	A label for this key, such as CI - Staging. It appears on Runs started with the key.
Status	Active or Inactive. Only Active keys can start Runs.

DoesQA shows the secret key once. Store it in your pipeline secrets or automation platform. You will not see it again in the app.

3

Find your Account ID

Open Settings (Account Settings). Copy the Account ID. The Universal Webhook URL includes it.

Pro tip: Create separate keys for staging and production pipelines. Set a key to Inactive when a pipeline should stop starting Runs, without deleting the history of Runs that already used it.

Choose how to connect

Goal	Start here
Any HTTP client, script, or tool	Universal Webhook
GitHub Actions with PR Checks	GitHub
GitLab CI with the catalog component	GitLab
Bitbucket Pipelines	Bitbucket
Azure Pipelines	Azure DevOps
Make, Zapier, or n8n	Make, Zapier, n8n

Call the Universal Webhook with your Account ID and key. That page covers preview (GET), start Run (POST), selection order, Value overrides, and mode=wait.

Pair keys with Run Recipes or tags from Tag Test so each pipeline selects the right Flows. See Build smoke and regression coverage.

Notifications for CI/CD Runs

Notification rules can include the CI/CD Webhook run type, and can limit that type to All Keys or specific CI/CD Keys. See Notifications.

Related

• Universal Webhook

• Integrations

• GitHub

• GitLab

• Bitbucket

• Azure DevOps

• Make

• Zapier

• n8n

• Notifications

• Run Recipes

• Max Concurrency

• Build smoke and regression coverage