Make
Start DoesQA Runs from Make with the Universal Webhook.
Last updated
Start DoesQA Runs from Make with the Universal Webhook.
Connect Make to DoesQA so scenarios, schedules, and other apps can start a Run when your business process says it is time. Make’s HTTP module calls the Universal Webhook.
Trigger DoesQA from the same automation that deploys, opens a ticket, or updates a sheet.
Keep one CI/CD key and Flow selection model across Make and your pipelines.
Hand results to Slack or Teams with Notifications while Make continues the scenario.
Create an Active CI/CD webhook key under Settings → CI/CD. See CI / CD.
Copy your Account ID from Account Settings.
Store the key in Make as a connection secret or scenario variable.
Add an HTTP → Make a request module to your scenario.
Set Method to POST.
Set URL to:
https://app.does.qa/api/hook/ACCOUNT_ID?key=YOUR_KEY&withAll=smoke&label=make-scenarioLeave the body empty unless you prefer to send key as header x-api-key instead of a query parameter.
Run the module once to confirm DoesQA accepts the Run.
Pro tip: Keep the default fast mode in Make so the scenario does not sit waiting on a long Run. Use Notifications when the team needs the result in Slack or Teams.
Add the same query options as the Universal Webhook. URL-encode JSON values if you pass Value overrides, for example:
Last updated
...&values=%7B%22BASE_URL%22%3A%22https%3A%2F%2Fstaging.example.com%22%7D