Two directions: Clay as an upstream enrichment/research layer pushing into turgo via webhook, or turgo pushing accounts to Clay tables for custom enrichment recipes. Most teams use Clay for bespoke research, turgo for the operating motion.
Clay → turgo
In Clay, add an HTTP API step pointing at your turgo inbound webhook (Settings → API → Inbound Webhooks → create one with a schema mapping). Clay-enriched rows land as Golden Record updates with Clay as the source.
turgo → Clay
A workflow action can push accounts/contacts into a Clay table (Clay API key required) for recipes turgo doesn't natively run — niche scraping, custom GPT research columns — with results returning via the webhook above.
Division of labor
Clay excels at bespoke research recipes; turgo owns the always-on motion (agents, sequences, signals). Use Clay for the exotic 10%, not as a parallel system of record.
Dedup caution
Round-tripping through Clay can create near-duplicate records if key fields get reformatted. Keep email/domain columns untouched in Clay recipes so identity resolution matches cleanly on return.
