Alerts
Everything the monitoring feed is reporting, ordered by what needs doing first.
No alerts
Nothing is being reported by the monitoring feed right now.
Simulated feed — not a live integration with any
monitoring product. A real one would write into the same alerts table.
Everything the monitoring feed is reporting, ordered by what needs doing first.
Nothing is being reported by the monitoring feed right now.
Rules that watch the alert feed and queue the right actions automatically — who to call, what to search for, what to open.
An automation never contacts anyone. It puts recommended actions on an alert for you to act on — the call, the email, and the purchase are always yours to make. The one exception is Open an incident record, which is internal bookkeeping and can be closed again at any time.
Create a rule to have alerts queue their own actions.
Every time a rule matched an alert. A rule fires at most once per alert.
Try a broader search term, or clear a filter.
Track an active event (an outage, a forced shutdown) and see every inquiry or purchase pursued because of it, in one place.
Create one to start attributing inquiries and purchases to it.
Hand-researched independent suppliers and service shops, not scraped listings — a starting point for who to call, not a verified directory. Always confirm details yourself before relying on them.
Data is a scraped snapshot, not live inventory. Scraping runs offline on a schedule, not from this page.
| Source | Listings | Last scraped | Status |
|---|
User-Agent and robots.txt checked before each run.The agent only drafts messages and discusses strategy in this thread — it never contacts a seller itself. You send each message yourself through the original listing, and you alone decide whether to approve a purchase.
Pick a conversation on the left, or start a new one from a listing.