Trigger Zapier Zaps or Make scenarios when QuietDiff detects a change, then route the alert to Slack, email, your CRM, or anywhere else.
Use Zapier's "Webhooks by Zapier" trigger to receive QuietDiff change alerts.
Make's Custom Webhook module receives QuietDiff alerts in the same format.
QuietDiff sends this JSON when a change is detected. Map these fields in your Zap or Make scenario:
{
"event": "alert",
"alert": {
"id": "alert_abc123",
"type": "CHANGE",
"subject": "Stripe pricing page changed",
"message": "Price changed: Pro plan now $99/mo (was $89/mo)",
"createdAt": "2026-11-04T20:00:00Z"
},
"change": {
"id": "change_xyz789",
"monitor": {
"id": "mon_123",
"name": "Stripe Pricing",
"url": "https://stripe.com/pricing"
},
"field": "pro_price",
"oldValue": "$89/month",
"newValue": "$99/month",
"changeType": "price_change",
"summary": "Pro plan increased from $89 to $99 per month",
"significance": "SIGNIFICANT",
"createdAt": "2026-11-04T20:00:00Z"
}
}When setting up your Zap actions, map these fields:
change.monitor.namechange.monitor.urlchange.fieldchange.oldValuechange.newValuechange.summaryalert.subjectalert.messageIn Make modules, reference webhook data like this:
change → monitor → namechange → oldValue and change → newValuechange → summaryMake will show available fields after you've received the first webhook.
change.summary to a Slack channel when a competitor pricing page changesalert.subject and change.summary to your sales teamchange.monitor.name, change.oldValue, change.newValue, and alert.createdAtchange.significance equals SIGNIFICANT or CRITICALQuietDiff webhooks include an HMAC signature in the X-QuietDiff-Signature header when you provide a webhook secret.
To add a secret:
In Zapier or Make, verify the signature by comparing:
HMAC-SHA256(request_body, your_secret) === X-QuietDiff-Signature
This is optional but recommended if your webhook URL is publicly accessible.