Use case · Monitoring
Prices, stock, statuses.Hear only when they change.
Watch values that live behind a sign-in: a supplier's price list, a claim's status, an account's limits. Kaabist runs the program on a schedule, compares each result with the last, and calls your webhook only when something changed.
The problem
Polling a page and diffing HTML is noisy: banners, timestamps and layout shifts all look like changes. Behind a login it is worse, because the session keeps expiring between runs.
How it works
01
Compare fields, not pages
Change detection compares the extracted data, limited to the fields you name. A new banner or a reordered menu is not a change; a new price is.
example{ "program": "supplier-prices", "cron": "0 */6 * * *", "timezone": "Europe/Istanbul", "change_detection": { "enabled": true, "fields": ["price", "stock"] } }02
Signed events with the difference
A change arrives as schedule.changed with the paths that changed and a link to the JSON Patch between the two runs. Deliveries are signed and retried with backoff; they can also go straight to Slack or Discord.
03
The login takes care of itself
The program saves its session after signing in and reuses it on the next run. When the session expires, it signs in again; when a code is needed, you get a link to type it in.
Questions
Askedbefore you ask.
More use cases
Scrape a website that requires login
Portals, dashboards, supplier sites: the data you need sits behind a sign-in form. Kaabist runs the login as part of a program, keeps the session between jobs, and reads the pages as typed, validated fields.
Automate logins with 2FA
One-time codes by e-mail or SMS, authenticator prompts, approval screens: a second factor is a step only the account owner can finish. Kaabist pauses the job there, emails a link to you (or the teammate or customer who owns the account), and resumes the program the moment the code is typed.
Forms that must submit exactly once
Some forms change the world when they are sent: an order is placed, money moves, an application is filed. Kaabist records those steps just before and just after they run (a fence), so a crash, a retry or a redeploy can never send them twice.