Clay enrichment for thousands of records.
Your agent searches Clay's database for people and companies. It runs your Clay functions on single records or on thousands at once.
- Coverage: partial
- 14 tools · 4 of them make changes
Read and change.
Your agent works with exactly the permissions of the connected account. Read tools are quick to enable. Tools that change data stay off until you explicitly turn them on.
What your agent can read
- People and company search in Clay's database.
- Results of enrichment and workflow runs, with status and credit usage.
- Remaining credits in your Clay workspace.
- On the Enterprise plan: queries across up to five Clay tables, including joins and sums.
What your agent can change
- Run one of your Clay functions on 1–100 records.
- Or run it as a batch on up to 10,000 records per run.
- Have people deleted from Clay Audiences under GDPR, with a dry run.
Only once you enable it, per agent and per tool. If you want, a person also approves each action before it runs.
How teams use Clay.
Marketing, sales and RevOps run these as recurring routines or on request.
- 01
Enrich inbound leads right away
A new form submission comes in- Run your Clay function for company and person
- Write the result back to the CRM
- Prioritize the lead by fit
ResultSales sees company size, industry and role without doing any research.
- 02
Build a target account list
Before a new campaign- Search for companies that match your criteria
- Enrich decision-makers with your Clay function
- Hand the list to outbound
ResultA freshly enriched list, with no purchased data.
- 03
Batch database refresh
Once a quarter- Run existing contacts through your Clay function as a batch
- Detect changed titles and companies
- Prepare the results for import
ResultUp to 10,000 records per run are current again.
- 04
Keep an eye on credits
Before and after large runs- Check the credit balance
- Start the run
- Report usage and match rate
ResultFor every run, you know how many credits it used.
Built-in safeguards
- Every enrichment costs Clay credits. The agent can check the credit balance beforehand and report usage afterward.
- If you want, changes only run after a person approves them, for example the team lead: in the Data Hub, in Slack or via a link. On top of that, each agent has daily and hourly limits.
- Guardrails for every agent: deletes and changes to more than 10 records need approval by default, an emergency brake kicks in on a run of deletes, and you can set your own rules per tool.
- Each connection has an access level: Read, Write or Admin. Where the vendor allows it, the Data Hub only requests the permissions for that level.
- Credentials are stored encrypted in the Data Hub, and the agent never sees them. Every call is logged.
What it can't do
- Creating tables, adding columns, writing rows, triggering table enrichments and building functions: these only work in Clay itself.
- Tables and functions can't be listed. You'll find their IDs in the Clay URL.
- Table queries require the Enterprise plan. Clay's own command-line tool can do more, but it's only available to Clay itself.
What's possible here depends on what Clay offers through its API. We make available what the API allows, as ready-made tools or through the generic API request to Clay, and we check new API versions regularly.
Connect Clay to your agents.
In 30 minutes, we'll show you the Data Hub with your own tools.