Snag Watcher

Guides

Recipes

Send any of these to POST /v1/watchers with your own webhook URL in notify.

Size back in stock

One size of a product on a Shopify store comes back in stock.

JSON
{
  "target": { "query": "https://www.allbirds.com/products/mens-wool-runners", "match": "url", "attributes": { "size": 10 } },
  "conditions": { "all": [{ "field": "availability", "op": "=", "value": "back_in_stock" }] },
  "where": { "sites": ["allbirds.com"] },
  "schedule": { "every": "1h", "until": "+30d" }
}

back_in_stock is only true on the check where the size comes back. To hear as soon as it's available, even on the first check, use in_stock.

Price drop from today

The price is 10% or more under what it was on the first check.

JSON
{
  "target": { "query": "https://www.sweetwater.com/store/detail/SM58--shure-sm58-cardioid-dynamic-vocal-microphone", "match": "url" },
  "conditions": { "all": [{ "field": "price_drop", "op": ">=", "value": "10%", "compare_to": "first_snapshot" }] },
  "where": { "sites": ["sweetwater.com"] },
  "schedule": { "every": "6h", "until": "+90d" }
}

Cheapest of several stores

You get the cheapest of three stores that has size 10 in stock at $120 or less.

JSON
{
  "target": { "query": "Brooks Ghost 17", "match": "exact", "attributes": { "size": 10 } },
  "conditions": { "all": [{ "field": "availability", "op": "=", "value": "in_stock" }, { "field": "price", "op": "<=", "value": 120 }] },
  "where": { "sites": ["brooksrunning.com", "runningwarehouse.com", "zappos.com"], "aggregate": "best" },
  "schedule": { "every": "1h", "until": "+30d" }
}

New product at a store

Keychron lists anything new with "Q1" in its name, other than the Q1 Pro.

JSON
{
  "target": { "query": "Q1", "match": "line", "exclude": ["Q1 Pro"] },
  "conditions": { "all": [{ "field": "availability", "op": "=", "value": "in_stock" }] },
  "where": { "sites": ["keychron.com"] },
  "schedule": { "every": "1h", "until": "+60d" },
  "notify": { "channels": ["webhook"], "repeat": "on_change", "webhook": { "url": "https://you.example/hook", "events": ["matched", "changed"] } }
}

The first webhook lists what already matches, and after that you get changed for each new product.

New post on a subreddit

Someone on r/Pen_Swap sells a Pilot Custom 823 for $250 or less, leaving out "want to buy" posts.

JSON
{
  "target": { "query": "Custom 823", "match": "line", "exclude": ["WTB"] },
  "conditions": { "all": [
    { "field": "availability", "op": "=", "value": "in_stock" },
    { "field": "price", "op": "<=", "value": 250 }
  ] },
  "where": { "sites": ["reddit.com/r/Pen_Swap"] },
  "schedule": { "every": "5m", "until": "+30d" },
  "notify": { "channels": ["webhook"], "repeat": "on_change", "webhook": { "url": "https://you.example/hook", "events": ["matched", "changed"] } }
}

Each result is a post: url links to it, seller is the author, date is when it was posted, and price is the first dollar amount in the title, or in the text if the title has none. A post is out_of_stock once its flair says sold (or closed, pending, traded and so on), its title has [SOLD], or it's removed. The first webhook lists the posts that already match, and after that you get changed for each new one.

Next release of a repo

Node.js ships its first release at version 25 or above, and the watcher stops.

JSON
{
  "target": { "query": "node", "match": "line" },
  "conditions": { "all": [{ "field": "version", "op": ">=", "value": 25 }, { "field": "release_status", "op": "=", "value": "available" }] },
  "where": { "sites": ["github.com/nodejs/node"] },
  "schedule": { "every": "1h", "until": "after_first_match" }
}

Prereleases come through as announced, so available skips them.

Two sizes at the same store

One store has both size 10 and 10.5 in stock at the same time.

JSON
{
  "target": { "query": "Brooks Ghost 17", "match": "exact", "attributes": { "size": [10, 10.5] } },
  "conditions": { "all": [{ "field": "availability", "op": "=", "value": "in_stock", "over": { "key": "sizes", "require": "all", "same": "seller" } }] },
  "where": { "sites": ["runningwarehouse.com", "zappos.com"] },
  "schedule": { "every": "1h", "until": "+14d" }
}

New product, then its price

When Keychron lists a new "Q6 HE", a second watcher starts on that product page and waits for a price under $200. See Follow-up watchers.

JSON
{
  "target": { "query": "Q6 HE", "match": "line" },
  "conditions": { "all": [{ "field": "availability", "op": "=", "value": "in_stock" }] },
  "where": { "sites": ["keychron.com"], "aggregate": "first" },
  "schedule": { "every": "1h", "until": "+180d" },
  "then": {
    "conditions": { "all": [{ "field": "price", "op": "<", "value": 200 }] },
    "schedule": { "every": "6h", "until": "+90d" }
  }
}

A booked time opens up

A 15-minute slot opens on a Cal.com page between November 9 and 13, in New York time.

JSON
{
  "target": { "query": "cal.com/peer/15", "match": "listing", "attributes": { "from": "2026-11-09", "to": "2026-11-13", "time_zone": "America/New_York" } },
  "conditions": { "all": [{ "field": "availability", "op": "=", "value": "open_slot" }] },
  "where": { "sites": ["cal.com/peer/15"] },
  "schedule": { "every": "5m", "until": "+7d" }
}

Cal.com only lists open times, so a booked time drops out of the results. If someone cancels, it comes back and you get changed, even inside the cooldown. Each result's date is the start with its UTC offset.

A job at a company

Discord posts a new remote engineering job on its Greenhouse board. Internships don't count.

JSON
{
  "target": { "query": "engineer", "match": "line", "attributes": { "remote": true }, "exclude": ["intern"] },
  "conditions": { "all": [{ "field": "availability", "op": "=", "value": "in_stock" }] },
  "where": { "sites": ["boards.greenhouse.io/discord"] },
  "schedule": { "every": "15m", "until": "+30d" },
  "notify": { "channels": ["webhook"], "repeat": "on_change", "webhook": { "url": "https://you.example/hook", "events": ["matched", "changed"] } }
}

An open job counts as in_stock. The first webhook lists the jobs that already match, and after that you get changed for each new one. Lever, Ashby and Workday boards work the same way.

A token moves 0.5% in 10 minutes

BONK on Solana moves 0.5% up or down within 10 minutes, read from DexScreener every minute.

JSON
{
  "target": { "query": "https://dexscreener.com/solana/DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263", "match": "url" },
  "conditions": { "all": [{ "field": "price_move", "op": ">=", "value": "0.5%", "compare_to": "window", "window": "10m" }] },
  "where": { "sites": ["dexscreener.com"] },
  "schedule": { "every": "1m", "until": "+7d" },
  "notify": { "channels": ["webhook"], "repeat": "every_match", "cooldown": "5m", "webhook": { "url": "https://you.example/hook", "events": ["matched"] } }
}

The link can be a pair or a token address. We keep exact prices, so a move on a $0.000028 token is measured on the real number. The window compares with the oldest check in the last 10 minutes (compare_to).

A status page incident

Cloudflare's Durable Objects component stops being operational, or an incident mentions it.

JSON
{
  "target": { "query": "Durable Objects", "match": "line" },
  "conditions": { "any": [
    { "field": "status", "op": "changed" },
    { "field": "status", "op": "in", "value": ["partial_outage", "major_outage"] }
  ] },
  "where": { "sites": ["statuspage:www.cloudflarestatus.com"] },
  "schedule": { "every": "5m", "until": "+30d" }
}

Each component, incident and maintenance is a record with a status and a record_type (component, incident, maintenance or page). For the whole page, use match: listing. A status page on its own domain needs the statuspage: or instatus: prefix.

A page's text changes

Python's downloads page lists 3.16.0, or its release list changes at all.

JSON
{
  "target": { "query": "https://www.python.org/downloads/", "match": "url", "attributes": { "selector": ".download-list-widget .release-number", "contains": "Python 3.16.0" } },
  "conditions": { "any": [
    { "field": "contains", "op": "=", "value": true },
    { "field": "text_hash", "op": "changed" }
  ] },
  "where": { "sites": ["change:https://www.python.org/downloads/"] },
  "schedule": { "every": "1h", "until": "+30d" }
}

A text watch can't tell a release from a typo fix, only that the text changed or the phrase appeared. Preview it to check the selector picks the part you meant. Every attribute is in Page changes.

A haircut at a salon, under a price

Robert's regular haircut at a Booksy barber shop costs $40 or less.

JSON
{
  "target": { "query": "https://booksy.com/en-us/388730_barber-shop-nyc_barber-shop_30067_new-york-city", "match": "url", "attributes": { "service": "Regular Haircut", "staff": "Robert" } },
  "conditions": { "all": [{ "field": "price", "op": "<=", "value": 40 }] },
  "where": { "sites": ["booksy.com/en-us/388730_barber-shop-nyc_barber-shop_30067_new-york-city"] },
  "schedule": { "every": "6h", "until": "+30d" }
}

On Booksy and Fresha we read the service menu: one result per service, with its price, length and staff. We can't read open times there, because Booksy's robots.txt disallows its time-slot API and Fresha opens a cart and can show a captcha for each search. Vagaro and Boulevard are waiting on a review. To hear when a time opens, the salon has to book through a site where we read times, like Cal.com (A booked time opens up) or Jane App for clinics.

A bill's next action

Senate bill 3331 has a new action, like being reported, passed or signed into law.

JSON
{
  "target": { "query": "https://www.congress.gov/bill/119th-congress/senate-bill/3331", "match": "url" },
  "conditions": { "all": [{ "field": "latest_action", "op": "changed" }] },
  "where": { "sites": ["congress.gov"] },
  "schedule": { "every": "1h", "until": "+180d" }
}

Each check reads the bill's latest action and its date, and we work out a status from its wording (introduced, reported, passed, to_executive, became_law, vetoed, failed or in_progress), so { "field": "status", "op": "=", "value": "became_law" } waits until it's law. Congress.gov doesn't publish a status, so this is our reading of the text. State bills work the same way through Open States (openstates.org/nc/bills/2025/HB1105). If Congress.gov or Open States isn't connected yet, creating the watcher fails with site_unavailable.

A PDF changes, and what changed

The IRS posts a new revision of Form W-9.

JSON
{
  "target": { "query": "https://www.irs.gov/pub/irs-pdf/fw9.pdf", "match": "url" },
  "conditions": { "all": [{ "field": "text_hash", "op": "changed" }] },
  "where": { "sites": ["change:https://www.irs.gov/pub/irs-pdf/fw9.pdf"] },
  "schedule": { "every": "1d", "until": "+180d" }
}

A link ending in .pdf is read as a PDF, and the result is a document with the text of every page, pages, pdf_title and pdf_modified. When the text changes, last_change says what moved, like changed "Rev. October 2018" to "Rev. March 2024", and how many paragraphs were added, removed and changed. Add "summarize": true to the attributes for a one or two sentence summary written by an LLM. A scanned PDF with no text layer reads as empty. We store the last version, so a deploy on our side doesn't lose the "before" text.

Something new on a list

CISA posts a new press release on its newsroom.

JSON
{
  "target": { "query": "https://www.cisa.gov/news-events/news", "match": "url", "attributes": { "list": "article.c-teaser" } },
  "conditions": { "all": [{ "field": "items", "op": "added" }] },
  "where": { "sites": ["change:https://www.cisa.gov/news-events/news"] },
  "schedule": { "every": "1h", "until": "+30d" }
}

list is a CSS selector for the item that repeats. Each match becomes a record keyed by its link, with its title, href, position and the date from its <time> tag. The first check sets the starting list, so nothing counts as added on it. { "field": "items", "op": "removed" } tells you when an item leaves. items works on any site where we read the whole list, like exchange listings or a dataset (Lists).

A change an AI checks for you

Notion's pricing page changes, and an LLM reads the change to decide whether a price went up.

JSON
{
  "target": { "query": "https://www.notion.com/pricing", "match": "url" },
  "conditions": { "all": [
    { "field": "text", "op": "judge", "value": "a plan's price went up, or a plan was removed" }
  ] },
  "where": { "sites": ["change:https://www.notion.com/pricing"] },
  "schedule": { "every": "6h", "until": "+90d" }
}

We only ask the judge when the text has changed. It reads change_excerpt, the changed lines with one line either side, so a change far down a long page still gets judged. The judge's reason is in the event's judged. Each watcher gets 20 judge calls a day, and a change held back by that limit is judged on a later check and fires then. That's why there's no text_hash changed next to it: on that later check the text hasn't changed again, so both could never be true. Previews don't call the judge (Judged conditions).

A city council agenda item

Seattle puts rezoning on a city council meeting agenda.

JSON
{
  "target": { "query": "rezoning", "match": "line", "attributes": { "days": 30 } },
  "conditions": { "all": [{ "field": "items", "op": "added" }] },
  "where": { "sites": ["legistar:seattle"] },
  "schedule": { "every": "6h", "until": "+90d" }
}

We look for your words in the agenda items of up to 12 meetings in the next days. Each matching item is a record with its matter file, type and status, the meeting's start time and the agenda PDF. The first check sets the starting list, and after that items added fires when an agenda with your words is posted. Any city or county on Legistar works the same way (legistar:<client>, or <client>.legistar.com). For every upcoming meeting, use match: listing.

A domain coming free

A domain you want is no longer registered, or it's pending delete and on its way back to the pool.

JSON
{
  "target": { "query": "shoe.dev", "match": "listing" },
  "conditions": { "any": [
    { "field": "available", "op": "=", "value": true },
    { "field": "pending_delete", "op": "=", "value": true }
  ] },
  "where": { "sites": ["rdap:shoe.dev"] },
  "schedule": { "every": "6h", "until": "+180d" }
}

We read the registry's RDAP record (the newer WHOIS), and available is true when there's no record. Reserved and premium names can look the same, and someone can register a name between our check and your purchase, so treat a match as a reason to go and look. For a domain you own, { "field": "days_to_expiry", "op": "<", "value": 30 } warns you before it lapses. We can't watch .de or .io because they have no RDAP server, or .uk and .xyz because their robots.txt keeps us out.

A Square appointment opening

A Tier 1 appointment opens between November 9 and 22 at a salon that books through Square.

JSON
{
  "target": { "query": "https://book.squareup.com/appointments/006k40agnfwses/location/L5TQE05VR6K90/services", "match": "listing", "attributes": { "service": "Medium (Tier 1)", "from": "2026-11-09", "to": "2026-11-22" } },
  "conditions": { "all": [{ "field": "availability", "op": "=", "value": "open_slot" }] },
  "where": { "sites": ["book.squareup.com/appointments/006k40agnfwses/location/L5TQE05VR6K90/services"] },
  "fetch": { "accept_site_terms": true },
  "schedule": { "every": "15m", "until": "+14d" }
}

Square's robots.txt disallows the API that lists open times, so you need fetch.accept_site_terms. Each open time is a slot with its start and offset, the exact price and the staff member, and a staff attribute watches one person. Watching the service menu (match: line) needs the same flag.

A Twitch channel going live

NASA's Twitch channel starts a stream.

JSON
{
  "target": { "query": "https://www.twitch.tv/nasa", "match": "url" },
  "conditions": { "all": [{ "field": "availability", "op": "=", "value": "back_in_stock" }] },
  "where": { "sites": ["twitch.tv/nasa"] },
  "fetch": { "accept_site_terms": true },
  "schedule": { "every": "2m", "until": "+30d" }
}

A channel counts as in_stock while it's live, so back_in_stock fires on the check where it goes live. The result has the stream title, game, viewer count and start time, and { "field": "stream_title", "op": "changed" } catches a new title. It needs fetch.accept_site_terms because robots.txt on Twitch's API disallows everything. If Twitch isn't connected yet, creating the watcher fails with site_unavailable.

A wallet's token transfer

USDC arrives at an Ethereum address.

JSON
{
  "target": { "query": "https://etherscan.io/address/0xd8da6bf26964af9d7eed9e03e53415d37aa96045", "match": "listing", "attributes": { "include": ["tokens"], "token": "USDC", "direction": "in" } },
  "conditions": { "all": [{ "field": "items", "op": "added" }] },
  "where": { "sites": ["etherscan.io/address/0xd8da6bf26964af9d7eed9e03e53415d37aa96045"] },
  "fetch": { "accept_site_terms": true },
  "schedule": { "every": "5m", "until": "+30d" }
}

Each transfer is a record with value in USDC as a number, the sender, the transaction hash and its time. The first check sets the starting list, so only later transfers fire. Polygonscan and Arbiscan addresses work the same way. You choose the address, and a wallet can belong to a private person, so that's your responsibility. It needs fetch.accept_site_terms. If Etherscan isn't connected yet, creating the watcher fails with site_unavailable.