Competitor watch
Track a set of competitor pages on a schedule and push every meaningful change to your stack.
The outcome
Track a set of competitor pages on a schedule and push every meaningful change to your stack.
Backed by a real, installable recipe, not a generated stub. Install it, attach your own inputs, and run it on your own accounts.
Expected output
A successful run returns a structured result:
[{ "url": "...", "field": "price", "old": 0.00, "new": 0.00 }] 4 steps
Real step types from the 30+ in the workflow vocabulary. Edit any of them after you install.
- 1navigate
Open each tracked page.
- 2extract
Read the watched fields: price, copy, availability.
- 3evaluate
Diff against the last run and keep only real changes.
- 4api_call
POST each change to your destination.
Inputs
page_urlslist must match^https?://destination_webhookurl must match^https?://
Input shape
Inputs are validated against per-slot regex rules before a run starts.
{
"page_urls": "<list>" // matches ^https?://,
"destination_webhook": "<url>" // matches ^https?://
} Estimated runtime: 5-10s per page, on your chosen interval.
Install in one click
Open the template in the app, attach your own inputs and resources, and run it on your machine or the cloud.
Local runs have no compute charge and do not use Writ cloud compute. Paid plans are for cloud execution, faster monitors, teams, managed AI, and fleet features.
Point it at a site
This recipe adapts to any of these, all on your own authorized accounts.
Competitor watch questions
What does the Competitor watch template do?
Where does it run?
Can I edit the recipe after installing?
Related templates
Start with the Competitor watch template
Install it, attach your own inputs, and run it on your own account in minutes.