Turn a Website Change Into a Ticket, Automatically
Some page changes need a person to do something — review a supplier's new terms, match a competitor's price, patch a broken layout. Point Rendex Watch at the page and let Zapier's native Website Changed trigger open a Jira, Trello, or Asana ticket the moment it moves, titled with what changed and carrying a crop of the exact spot. No webhook, no code, no dashboard nobody checks.
Last updated 2026-07-21
The Problem
Change notifications that land in a chat channel get read once and scroll away — but some changes are work: a vendor quietly rewrites their SLA, a competitor drops their price, a regulator posts a new rule, your own pricing page breaks after a deploy. Those need an owner, a due date, and a place they won't be forgotten. Copying a Slack alert into your tracker by hand is exactly the manual step that gets skipped, and building your own page-diff-to-ticket pipeline means a scheduler, a headless browser, snapshot storage, and a diff step to maintain.
The Solution
Rendex Watch handles the monitoring and Zapier turns each change into a tracked task. Create a watch on the page, then build a Zap with the Rendex 'Website Changed' trigger — Zapier polls your watches natively and starts the Zap for each new change, no webhook to host. Because Rendex has already done the diff, the trigger hands over a plain-English summary and a crop of the exact region that moved. Map the summary into a Jira/Trello/Asana ticket title, drop the page URL and image links into the description, and every meaningful change opens itself as a ready-to-work card — assigned, dated, and impossible to lose in a feed.
How the Workflow Runs
Rendex Watch checks
Rendex re-renders your URL on a schedule and diffs it against the baseline in real Chrome. No cron, no storage, no diff library to run.
Website Changed fires
The native Zapier trigger polls your watches and starts the Zap for each new change — with a plain-English summary, a crop of the change, and before/after images.
Open a ticket
A Jira/Trello/Asana 'Create Issue' step opens a card titled with what changed and links the crop and before/after images in the description — assigned and ready to work.
Input → Rendered Output
Rendered by Rendex
What You Need
- A Rendex API key. Watch runs on Free (1 watch, a daily check); Starter and Pro add more watches and faster checks.
- The Rendex app connected in Zapier — search "Rendex" in the app directory and paste your key once.
- At least one Rendex Watch created on the page you care about (from the dashboard, the API, or the Create Website Watch action).
- Your tracker connected in Zapier — Jira, Trello, Asana, Linear, ClickUp, or a Notion database — with the target project or board.
What This Recipe Uses
A title that reads like a task
The change arrives with a one-line summary of what happened, so the ticket title ("Supplier cut the cancellation window from 30 to 14 days") is meaningful the moment it's created.
The change, cropped into the ticket
The trigger includes a crop of just the region that moved, plus before/after images — link them in the description so the assignee sees the change without opening the page.
Any tracker, assigned and dated
Route the change to Jira, Trello, Asana, Linear, ClickUp, or Notion. Set the project, assignee, labels, and due date in the same step — it's a normal Create-Issue action.
Native polling, zero infrastructure
The Website Changed trigger is native to Zapier — no webhook to host, no signature to verify. Rendex owns the schedule, the real-Chrome render, the storage, and the diff.
Build It
# Zapier — no code
Trigger: Rendex — Website Changed
(fires per change on the watches connected to your key)
Action: Jira Software Cloud — Create Issue # or Trello/Asana/Linear/ClickUp
Project: OPS
Issue Type: Task
Summary: "Page changed: {{ Rendex: Name }} — {{ Rendex: Ai Summary }}"
Description: |
{{ Rendex: Url }} changed on {{ Rendex: Changed At }}.
What changed: {{ Rendex: Ai Summary }}
Crop: {{ Rendex: Crop Url }}
Before: {{ Rendex: Before Url }} After: {{ Rendex: After Url }}
Assignee: (optional) Labels: monitoring
# No Ai Summary on a run? Fall back to a diff-score line + {{ Rendex: Diff Overlay Url }}.# Create a watch on the page you want to monitor. After this, the Zapier
# "Website Changed" trigger polls it automatically — no webhook needed.
# diffMode "both" flags a change to how the page LOOKS or its text; threshold
# is the 0..1 noise floor the visual diff must EXCEED to count as a change.
curl -X POST https://api.rendex.dev/v1/watches \
-H "Authorization: Bearer rdx_YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://supplier.example.com/terms",
"name": "Supplier terms",
"intervalMinutes": 1440,
"diffMode": "both",
"threshold": 0.02
}'
# => { "success": true, "data": { "id": "<uuid>", "lastStatus": "queued", ... } }
#
# intervalMinutes floor by plan: Free 1440 (daily), Basic 180, Starter 60, Pro 30.
# Create it here, from the dashboard, or with the "Create Website Watch" action.100 free API calls/month — no credit card required. Get your API key and start building.
Use this when a change isn't just news, it's a to-do. The distinction from the Slack version is where the work lives: a channel is fine for awareness, but a change that obligates someone — review these new terms, requote against this price, fix this broken hero — belongs on a board with an owner and a due date. Because the Website Changed trigger arrives pre-enriched, the ticket is genuinely actionable on creation: the plain-English summary becomes a title a teammate understands at a glance, and the crop of the changed region goes in the description so they see what moved without opening the site or hunting through a full-page screenshot. It's native Zapier polling, so there's no endpoint to stand up and no signature to verify — just a trigger and a Create-Issue step. Point it at Jira, Trello, Asana, Linear, ClickUp, or a Notion database; the same change can even fan out to a ticket and a Slack heads-up at once. Watch runs on the free tier, and each check costs one credit from your render pool.