GTM Signals is a signal source you add to Clay, not another dashboard. The data flows to your stack. Your reps never log into ours.
Pull the signal into any table, or have us push it the moment a call is scored. Both work today with a standard Clay workspace.
Add an HTTP API column to your Clay table and point it at our enrich route. Clay templates the domain from your Domain column and saves the key once, workspace-wide.
The response comes back flat, so mapping is trivial: signal.summary, signal.quote, signal.why_now, signal.audio_clip_url, and signal_score. Map them into columns; the signal sits right beside your ZoomInfo waterfall.
Private company in the row? You get a clean 200 with signal_found: false, never an error. Most prospect lists are mostly private companies; the column just stays quiet for those rows.
Paste your Clay "Monitor Webhook" URL into your GTM Signals account. The moment a call is scored, we POST a signal record: signal_source, signal_timestamp, domain, signal_payload_url, plus the flat signal fields above.
A new CFO statement becomes a row, and the row fires your sequence.
We coexist in the same Clay waterfall: the table that waterfalls ZoomInfo for contacts adds our column for the earnings signal. Your ZoomInfo seats stay exactly where they are.
Claude, or any agent-native GTM tool, connects with your key. The tool get_earnings_signal(domain) returns the verified signal plus the audio clip. Callable alongside ZoomInfo's GTM AI layer.
Others scrape text transcripts across every public event. We go deep on earnings and executive statements, and verify every quote against the actual call audio. The clip is attached. You can play this one right now.