To enrich Clay records with website change signals, define a business-relevant change, monitor it with a Clay Custom Signal or a scheduled enrichment, and keep a dated history keyed to a stable company identifier. Compare each new result with the previous one, then route only meaningful changes to an appropriate follow-up. Clay documents this as a periodic workflow—not a real-time change alert.
Define the website change you want to detect
Start with a change that could alter a sales, growth, or operations decision. For example, Clay uses compliance changes as an example of a signal: a company adds compliance information to its trust center. Before building anything, write down three specifics:
As an Amazon Associate I earn from qualifying purchases.
- Where to look: Name the page or evidence, such as a trust center or product page.
- What counts as a change: State the condition precisely, such as newly published compliance information—not merely any page edit.
- What happens next: Identify the team or action that should receive the signal.
This definition keeps routine wording edits from becoming noisy alerts. Clay’s documentation describes product capabilities and workflows, but does not establish complete website coverage, detection accuracy, or a latency guarantee.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Choose a monitoring approach
| Approach | Use it when | Main consideration |
|---|---|---|
| Clay Custom Signals | You want to monitor a website or another digital source for a defined change on a recurring schedule. | Set the source and frequency; Clay’s documentation does not promise exact-time or real-time monitoring. |
| Scheduled enrichment with run history | You already have an enrichment output and want to know how it changes between runs. | Preserve outputs in a separate history table, use a stable company identifier, and compare successive results. |
Clay describes Custom Signals as a way to monitor websites and other digital sources for specific changes on a regular schedule. Choose this path when you need to define and monitor a signal from a source. Choose scheduled enrichment plus history when the useful evidence is an existing enrichment result that you can retain and compare.
Build a run history for enrichment changes
Clay’s documented pattern is to schedule an enrichment, write its identifier and output to another table, retain each run as a new row, and compare records across runs. The exact fields and comparison depend on the enrichment output you want to track.
- Prepare the company table. Start with target companies and create the enrichment whose output you want to monitor.
- Schedule the enrichment. Enable scheduled reruns for the enrichment in the source table.
- Write each result to a separate history table. Send a stable identifier—such as company name or domain—along with the enrichment output. Clay calls this identifier essential to the run-history workflow because it lets you associate results from different runs with the same company.
- Keep each run as a new row. In the history table, turn off “Update existing rows on re-run” so recurring results are retained rather than overwriting prior rows.
- Expose the comparison fields. Make the company identifier, output, and creation time available in the history table.
- Retrieve and compare prior results. Use a lookup table to find earlier runs for the same identifier, then configure the comparison logic. For a numeric output, Clay’s guide specifies a run condition of “if the change is not 0.” For other output types, define a comparison appropriate to the data rather than assuming the numeric rule applies.
- Align dependent schedules. Match the lookup schedule to the source schedule and leave a short delay between the first table’s scheduled job and the dependent lookup job to avoid a timing conflict.
Clay’s guide describes scheduled runs every 24 hours from the time they are first scheduled; it does not describe selecting a particular clock time. Treat the result as periodic monitoring, not an immediate alert when a page changes.
Turn a detected difference into a useful signal
A difference between two enrichment outputs is not automatically meaningful. Set a qualifying condition that reflects the business question—for example, whether the company newly published compliance information—before routing the result. Clay describes converting an enrichment or AI query into a signal, including Claygent analysis of website-content changes.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Clay documents optional follow-up enrichments such as Slack notifications or Salesforce updates, and describes broader signal workflows that can connect with a CRM and other destinations. Choose the destination to fit the action: a notification can prompt review, while a record update can change CRM data. For changes that should not automatically alter customer-facing records, route the finding to a human for review first.
Account for freshness and schedule limits
There are two separate timing questions: when a scheduled workflow runs, and whether the underlying enrichment searches again or reuses a recent result. Clay’s Enrich CRM documentation describes freshness by specific action; those details should not be generalized into a rule for every Clay enrichment.
| Enrich CRM action or result | Documented freshness behavior |
|---|---|
| Enrich contact; Reverse email lookup; Find work email; Get homepage content | Searches fresh each time, according to Clay’s Enrich CRM documentation. |
| Company firmographics and certain French registry actions | May reuse a recent result for up to 30 days. |
| Latest funding; monthly website traffic; website tech stack | May reuse a recent result until the end of the calendar month. |
| Live technology scan | Can return no data if it cannot reach the site. |
If your goal is to detect a live page change, check the freshness behavior of the particular action you use. A scheduled rerun does not by itself establish that every action performs a fresh search each time. Likewise, the documented schedule is a 24-hour recurrence from initial scheduling, not a selectable exact run time.
Rank #4
Or skip the browser setup
If your workflow needs a screenshot as additional website evidence, ScreenshotNeo offers a screenshot API and MCP server. Its endpoint can return an image or PDF with one GET request; this is an optional way to capture a page, not a replacement for defining and comparing Clay signals.
ScreenshotNeo API documentation
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Only clean shots are billed: bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and the response identifies the page verdict and billing status in headers. Its MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000.
Sign up free for 1,000 screenshots a month, with no card required.
Frequently Asked Questions
Can Clay website change signals alert me immediately when a page changes?
No real-time guarantee is documented. The Custom Signals guide describes recurring runs every 24 hours from initial scheduling.
What identifier should I store in the history table?
Use a stable company identifier such as its name or domain so results from different runs can be associated with the same company.
Free tools Windows power users keep installed
One-click scans. No signup required.
Does every scheduled Enrich CRM action search the website again?
No. Clay documents freshness by action: some search fresh each time, while others may reuse recent results for specified periods.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
