Zapier

Start DoesQA Runs from Zapier with the Universal Webhook.

Connect Zapier to DoesQA so Zaps can start a Run from the apps your team already uses. A Webhooks by Zapier step calls the Universal Webhook.

Why use it

• Start DoesQA from CRM updates, form submits, deploy events, or any Zapier trigger.

• Keep the same key, tags, and Recipes you use in CI.

• Let DoesQA Notifications deliver results while the Zap moves on.

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. Keep the key in a Zapier storage field or vault your team already trusts.

Add a Webhooks step

1. Add Webhooks by Zapier → Custom Request (or POST).

2. Set Method to POST.

3. Set URL to:

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

1. Leave the body blank for a simple start, or send x-api-key as a header with your CI/CD key and omit key from the query string.

2. Test the step and open DoesQA to confirm the Run appeared.

Pro tip: Map dynamic Zap fields into label or URL-encoded values so each Run shows which Zap and record started it.

Select Flows and Values

Use the same query options as the Universal Webhook. Example with a Recipe:

https://app.does.qa/api/hook/ACCOUNT_ID?key=YOUR_KEY&recipe=4sJz2&label=zapier-release

Related

• Integrations

• Universal Webhook

• Make

• n8n

• CI / CD

• Notifications