Incapon · — In progress, on track for the 24th. Field picking works on all five now — you click the value on a rendered snapshot and we resolve it to something more durable than a CSS path, then re-verify it on every run and tell you when a field stops resolving instead of silently reporting "no change". Alerts carry old and new, and numeric fields take a threshold so a three-lira move does not wake anybody.
Request board
Detector requests
Every public request tagged Detector, newest first.
What are you still doing by hand? Describe the work, not the software.
Posted publicly. Subscribers can send their problem privately instead.Solve my problem
3 requests
We watch price and lead time on five supplier catalogues. The pages change all day for reasons that have nothing to do with us, so a page-level alert is a page-level alert we have learned to ignore.
DetectorAutomationFinance
I
KAKaren Alvarez, Purchasing Manager ·
We look after 40-odd sites we did not build. We find out they are broken when the client calls, and we find out they were edited when something we wrote three months ago is gone.
DetectorAutomationIntegrations
I
Incapon · — Completed, one week from the call. Availability checks every minute from two regions, so a single failed probe does not page anyone; content checks hourly with the noisy regions of a page excludable by selector, which is what fixed your cookie banner. Both land in the same alert, tagged as "down" or "changed", and both go out on Slack as well as email. One limit: a site behind a login is out of scope for now — we check what a visitor can see.
RDRyan Delgado, Web Agency Partner ·
Page-change alerts land in one person's inbox. The team that has to act on them lives in Slack, so the alert arrives a day late by way of a forward.
DetectorIntegrations
I
Incapon · — In progress — the OAuth install is done and alerts are posting to a test workspace. Per-monitor routing is next.
LBLaura Bennett, Procurement Manager ·