n8n

Start DoesQA Runs from n8n with the Universal Webhook.

Connect n8n to DoesQA so workflows can start a Run whenever your automation graph says go. An HTTP Request node calls the Universal Webhook.

Why use it

• Trigger DoesQA from self-hosted or cloud n8n workflows next to the rest of your ops graph.

• Share one CI/CD key with GitHub, GitLab, and no-code tools.

• Continue the workflow after DoesQA accepts the Run, and use Notifications for the human-facing result.

Before you start

1. Create an Active CI/CD webhook key under Settings → CI/CD. See CI / CD.

2. Copy your Account ID from Account Settings.

3. Store the key in n8n credentials or an environment variable.

Add an HTTP Request node

1. Add an HTTP Request node.

2. Set Method to POST.

3. Set URL to:

https://app.does.qa/api/hook/ACCOUNT_ID?key=YOUR_KEY&withAll=smoke&label=n8n

1. Optionally move the key to header x-api-key and drop it from the query string.

2. Execute the node once and confirm the Run in DoesQA.

Pro tip: Pass expression values into label or values so each Run carries the workflow name and the record that triggered it.

Select Flows and Values

Use the same query options as the Universal Webhook. Example waiting for the Run inside the workflow:

https://app.does.qa/api/hook/ACCOUNT_ID?key=YOUR_KEY&withAll=smoke&label=n8n&mode=wait

Raise the node timeout when you use mode=wait, or keep the default fast mode and let Notifications carry the result.

Related

• Integrations

• Universal Webhook

• Make

• Zapier

• CI / CD

• Notifications