To enrich Clay records with website change signals, monitor a narrowly defined change using Clay Custom Signals or rerun an existing enrichment on a schedule, save each result with a stable company identifier, and compare it with earlier runs. Route only changes that meet a clear business rule to a follow-up action. Clay documents this workflow, but it does not promise real-time detection or coverage of every website.
Define the website change you want to act on
Start with a change that has a clear business use, rather than monitoring a site for any difference. For example, Clay’s Custom Signals guide uses compliance changes as an example: you might watch a company’s trust-center page for newly added compliance information.
Before building the workflow, specify three things:
- Evidence: Which page, content, or enrichment output should be observed?
- Change condition: What counts as a meaningful change—for example, new compliance information or a change in a numeric value?
- Next action: Which team should be notified, or which record should be updated, when the condition is met?
This definition helps keep routine edits from becoming noisy alerts. Clay describes Custom Signals as a way to monitor data sources for specific changes on a regular schedule (Clay University: Custom Signals).
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
Choose a monitoring path
Clay’s documentation describes two related approaches. Choose based on whether you need to monitor a source directly or already have an enrichment result you want to compare over time.
| Approach | Use it when | What to plan for |
|---|---|---|
| Custom Signal monitoring | You want to monitor a website or another digital source on a recurring frequency. | Configure the source and frequency. The documentation does not establish exact-time or real-time detection guarantees. |
| Scheduled enrichment with run history | You already have an enrichment output and want to identify how it changes across runs. | Keep a stable company identifier and historical outputs, then compare runs through a lookup workflow. |
These are documented workflows, not guarantees that every site can be monitored or every change will be detected. Clay’s materials do not establish detection-coverage, latency, or accuracy benchmarks.
Build a run history for enrichment changes
For an existing enrichment, Clay documents a pattern that stores successive outputs in a separate table so they can be compared. Follow the table setup and schedule guidance in Clay’s Custom Signals guide; labels or available options can change, so check the current interface if a setting differs.
- Prepare the source table. Start with a table of target companies and create the enrichment whose output you want to monitor.
- Schedule the enrichment. Enable scheduled reruns for the enrichment in the source workflow.
- Write each run to a separate history table. Send the company name or domain together with the enrichment output to that table.
- Keep every run as a new row. In the history table settings, turn off “Update existing rows on re-run” so recurring outputs are retained instead of overwriting a prior row.
- Expose the fields used for comparison. Make the company identifier, enrichment output, and creation time available in the history table.
- Look up earlier runs for the same company. Use a lookup table to retrieve prior outputs for the matching identifier, then configure the comparison condition. For numeric outputs, Clay’s guide specifies a run condition of “if the change is not 0.”
- Coordinate the schedules. Set the lookup schedule to match the source schedule and leave a short delay between scheduled jobs in the first and second tables, reducing the chance that the lookup runs before new history rows are available.
Use a stable company identifier
The identifier connects a new output to the right company’s earlier runs. Clay’s guide identifies company name or domain as suitable examples and calls this information essential to the run-history workflow. Use the same identifier consistently; if a company’s name varies between rows, a stable domain can help avoid comparing unrelated records or missing a prior run.
Recommended Free Tools
Understand the schedule
Clay’s Custom Signals guide describes scheduled runs as recurring every 24 hours from when the schedule is first set, rather than at a selectable clock time. Treat the workflow as periodic, not real time. Leave a short delay between dependent scheduled jobs as Clay recommends, and allow for the possibility that a page change will not be reflected until a later run.
Set a useful threshold and choose a follow-up
Clay describes turning an enrichment or AI query into a signal, including Claygent analysis of website-content changes. Once the comparison identifies a candidate change, define an explicit threshold for what deserves attention. For example, a numeric change condition can exclude unchanged results; a content-based rule should specify the evidence that makes a change relevant to the team.
Clay documents optional follow-up enrichments such as Slack notifications or Salesforce updates, as well as broader signal workflows that connect to CRM and other destinations (Clay product page). Match the action to the change:
- Send a notification when a change needs investigation.
- Update a CRM field when the evidence and rule are reliable enough for an automatic record change.
- Keep a human review step for changes that could alter customer-facing records or trigger consequential outreach.
A signal is a reason to consider an action, not proof that the new information is correct or appropriate to publish. Preserve the observed output and the comparison context so a reviewer can assess what changed.
Account for enrichment freshness
Freshness depends on the specific action. Clay’s Enrich CRM documentation describes these behaviors for that integration; they should not be read as a universal rule for every Clay source or workflow.
| Documented Enrich CRM action or result | Freshness behavior described |
|---|---|
| Enrich contact; Reverse email lookup; Find work email; Get homepage content | Searches fresh each time. |
| 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 website. |
If the intended signal is a live page change, a reused result may not show it on the next scheduled run. Check the documented freshness behavior for the particular Enrich CRM action and interpret missing live-scan data as a possible reachability issue, not automatically as evidence that the company has no relevant technology.
Use ScreenshotNeo when you need a screenshot as evidence
If your workflow needs a visual record of a page alongside Clay’s signal, ScreenshotNeo is a website screenshot API and MCP server. It can return a screenshot or PDF, but it does not replace Clay’s documented signal and run-history workflow. A screenshot alone also does not establish that a particular business change occurred.
Or skip the browser setup
Make one GET request for a screenshot; see the ScreenshotNeo API documentation for request options and response details.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsRank #4
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 or consent banners like a visitor and removes 60+ known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and each response identifies the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.
Sign up for ScreenshotNeo free.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot common workflow problems
New results overwrite older results
Check that “Update existing rows on re-run” is turned off for the history table. The run-history comparison depends on retaining separate outputs from successive runs.
A company’s previous result is not found
Confirm that both tables use the same identifier and that the lookup matches it consistently. Clay’s guide names company name or domain as examples of the stable identifier needed by this workflow.
The comparison runs before the new history row exists
Check that both schedules are aligned and add a short delay between the source and lookup table jobs, following Clay’s scheduling guidance. Scheduled runs are frequency-based, not set to a precise clock time.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchA page change does not appear in the output
First check whether the enrichment action searches fresh each time or may reuse a recent result. Then check whether the source is accessible to the action: Clay notes that a live technology scan can return no data if it cannot reach the site. The documentation does not establish complete detection coverage for websites.
Too many changes trigger action
Refine the condition so it matches the evidence and business action you defined. For consequential CRM updates or outreach, add human review rather than treating every changed output as a verified fact.
Frequently Asked Questions
Does Clay’s website-change workflow run in real time?
No real-time guarantee is documented. The Custom Signals guide describes recurring scheduled monitoring, with runs every 24 hours from initial scheduling.
Can I compare changes when the enrichment output is numeric?
Yes. Clay’s Custom Signals guide gives “if the change is not 0” as the run condition for numeric outputs.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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.
