Open a Ticket When a Web Page Changes (Rendex Watch + Make)
Point Rendex Watch at a page — a competitor's pricing, a supplier's terms, a compliance doc — and when it actually changes, Make opens a ticket in Trello, Jira, or Asana automatically. A real-Chrome visual diff decides what counts as a change, so your board fills with real work, not false alarms.
Last updated 2026-07-15
The Problem
Plenty of pages are worth watching — a competitor's pricing, a vendor's terms, a policy or compliance doc, a status page — and a change usually means someone has to do something, i.e. a ticket. Doing it by hand means remembering to check, and naive polling means diffing raw HTML, which fires on every ad rotation, session token, and timestamp. So teams either check manually and miss changes, or wire up a monitor so noisy that everyone learns to ignore its tickets.
The Solution
Rendex Watch does the hard part: it renders the page with a real browser on a schedule and runs a visual + text diff, firing only when the content meaningfully changes — with noise controls for regions and text you don't care about. Create the watch once with your Make custom-webhook URL as the target; when the page changes, Rendex POSTs a signed watch.changed event and a Trello/Jira/Asana module in Make opens a ticket with the URL, a summary, and a link to the diff image. The result is a board that reflects real changes worth acting on. (Watch runs on Free with a daily check and email alerts; webhook delivery for automations like this is Starter and up.)
How the Workflow Runs
Watch checks the page
Rendex renders the URL on a schedule and diffs it against the last baseline with a real browser.
watch.changed webhook
On a real change, Rendex POSTs a signed watch.changed event to your Make custom webhook.
Create a ticket
A Trello/Jira/Asana module opens a ticket with the URL, what changed, and the diff image link.
Input → Rendered Output
Rendered by Rendex
What You Need
- A Rendex API key on Starter or above — webhook delivery (what drives this scenario) is Starter+. Free includes 1 watch with daily email alerts to try the diff first.
- A Make account with a scenario that starts from a Custom Webhook (Webhooks > Custom webhook) module.
- A ticketing module connected in Make: Trello (Create a Card), Jira (Create Issue), or Asana (Create Task).
- The URL to monitor, and optionally a selector or ignore-regions to focus the diff.
What This Recipe Uses
Real-Chrome visual + text diff
Watch renders the page with a real browser and compares against the last baseline — it fires on genuine content changes, not on ad rotations, timestamps, or session tokens.
Signed webhook, only on change
Rendex POSTs a watch.changed event (HMAC-signed via x-rendex-signature) only when the page actually changes — no polling in Make, no busy scenario runs.
One change, one ticket
Map the payload — URL, change summary, diff-image link — into a Trello card, Jira issue, or Asana task so real changes land as actionable work on your board.
Scheduled, one credit per check
Set the check interval to match the page; each scheduled check is one credit from your shared pool, and faster intervals come with higher plans.
Build It
# Point a watch at the page; target = your Make custom-webhook URL.
curl -X POST https://api.rendex.dev/v1/watches \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://competitor.com/pricing",
"name": "Competitor pricing",
"intervalMinutes": 180,
"webhookUrl": "https://hook.make.com/your-custom-webhook-id"
}'
# Rendex now checks the page every 3h and POSTs watch.changed on a real change.// What Make receives on a change — a FLAT payload. Map these fields
// directly into your ticket module (no nested watch{}/change{} objects).
// Headers carry the auth signal: x-rendex-signature (HMAC-SHA256 over
// `${timestamp}.${rawBody}`), x-rendex-timestamp, x-rendex-delivery-id.
{
"event": "watch.changed",
"watchId": "6b1c...-uuid",
"runId": "9af2...-uuid",
"url": "https://competitor.com/pricing",
"diffScore": 0.038,
"diffPixels": 14820,
"beforeUrl": "https://api.rendex.dev/v1/images/...?sig=...",
"afterUrl": "https://api.rendex.dev/v1/images/...?sig=...",
"diffOverlayUrl": "https://api.rendex.dev/v1/images/...?sig=...",
"summary": "Pro plan price changed"
}
// Make: Create Trello Card -> Title = "Change on " + {{url}},
// Description = {{summary}} + {{url}} + "diffScore " + {{diffScore}},
// Attachment = {{diffOverlayUrl}} (short-lived signed URL — re-host
// if you need a permanent copy)100 free API calls/month — no credit card required. Get your API key and start building.
Reach for this when a page change is a task, not just a notification — pricing moves that need a competitive-response ticket, a supplier's terms update that legal has to review, a compliance page that must be re-checked when it shifts. Slack pings get lost; a ticket on the board gets done. The reason to route it through Rendex Watch rather than a DIY monitor is signal quality: a real-Chrome visual+text diff with region and text ignores fires on genuine changes, so the tickets it opens are worth opening — the fastest way to kill a monitoring automation is to let it cry wolf. In Make it's a custom webhook receiving the signed watch.changed event, then a Create Card/Issue/Task module that maps the URL, the change summary, and the diff-image link into the ticket. You create the watch once (a single HTTP call or the dashboard) pointed at your webhook, and the scenario runs itself. Watch is free to try with daily email checks; webhook delivery, which this recipe needs, is on Starter and up.