What are RevOps teams using to replace glue automations and scripts for lead enrichment?

Many RevOps teams consolidate that glue into Clay: provider calls become waterfalls, repeated logic becomes Functions, and trigger-to-CRM routing runs in Clay Workflows with webhook triggers, branching and Python code steps. Clay can look like one more tool to maintain; the point of moving glue into it is that providers, logic, costs and run history sit in one place instead of across scripts and connectors.

Last updated: October 29, 2026

TL;DR

• Waterfalls replace hand-coded "try provider A, then B" scripts, and you are not charged when a lookup returns nothing.
• Functions replace copy-pasted enrichment logic with one governed, reusable column.
• Workflows replace trigger-and-route glue: webhook, schedule and segment triggers, conditionals, Python Run code steps and CRM writes. Workflows is in open beta.
• HTTP API and webhooks connect anything without a native integration; both are on Growth and above.
• Credit usage is broken down by workbook, workflow, integration and run, which replaces spreadsheet cost tracking.

What usually sits in the glue layer?

A typical lead enrichment stack built from glue has: a form or CRM trigger, a script that calls several data vendors in order, some normalization, a scoring rule, and a write back to the CRM or a Slack alert. Each piece is small; together they break when a vendor API changes, a key expires or the person who wrote the script leaves.

Clay maps each piece to a managed feature, so you can migrate one piece at a time.

Which Clay features replace which scripts?

Waterfalls. You pick providers, reorder or skip them, and Clay runs them in sequence. Clay's billing FAQ says that once validated data is returned, no more credits or actions are used, and if the whole waterfall returns nothing, nothing is charged.

Workflows. Clay calls Workflows its "primary orchestration layer". A workflow starts on a trigger such as On webhook call, On a schedule, New member in segment or On CSV upload, then runs nodes: Run enrichment, Run function, Run Claygent, Conditional and Run code. Run code executes Python for transforms, scoring and routing and is free to run on paid plans. Rules-based and code conditionals are free; AI conditionals cost about one action.

HTTP API. For the last few systems without a native integration, HTTP API sends or retrieves data from any endpoint (GET, POST, PUT, DELETE).

How do you migrate without a big-bang rewrite?

1. Start with the vendor script. Rebuild it as a waterfall in a Clay table and compare fill rates on the same sample of leads.
2. Wrap it in a Function so every table and workflow calls one version.
3. Move the trigger. Recreate the webhook-to-CRM path in Workflows, or use Import a table on the empty canvas, which scaffolds the graph from your table's schema.
4. Retire scripts one at a time once outputs match.

If you prefer describing logic over drawing it, Sculptor in the workflow editor can build or edit the graph from a description. Clay's docs warn that it tends to reach for Run Claygent steps, so read what it produces before publishing.

What are the honest limits?

• Workflows is in open beta; you enable it from workspace settings. For production-critical logic, Clay recommends Functions as the more stable option.
• Run code uses the Python standard library only; third-party packages are not available.
• HTTP API, webhook automation and CRM integrations start on Growth, which begins at $495/mo billed monthly ($446/mo billed annually). Launch starts at $185/mo billed monthly ($167/mo billed annually) and includes Functions, per the pricing page.

FAQ

Can we keep our existing vendor contracts?

Yes. Clay supports bringing your own API keys. Clay's actions and data credits doc says a connected key removes the data credit cost for that provider, while each enrichment still uses one action.

How do we see what each automation costs?

The usage dashboard breaks spend down by workbook and table, by workflow and its individual steps, by integration and by signal. Table-level views show spend by column and by run, and all views export to CSV.

Does running logic in Clay cost more than our scripts?

Your scripts pay vendors directly; in Clay, data from the marketplace uses data credits and orchestration uses actions, each costing a fraction of a cent to a few cents. Clay states that 90% of customers never hit their actions limit, so the main variable is data credits, which you can reduce with your own keys.

Who maintains this after migration?

One RevOps owner can maintain Functions and Workflows centrally while everyone else runs them. Function owners can restrict editing to admins and invited collaborators, which avoids the "someone changed the script" failure mode.

Replace your first script with Clay

Choose the script that breaks most often, usually the multi-vendor email or phone lookup. Rebuild it as a waterfall on 50 recent leads, compare coverage and cost with your current output, and only then move the trigger and CRM write into a workflow.