Enrich a sheet of companies with Clay
On request, the agent runs your Clay function on every domain in a sheet and writes what it returns back to each row.
With Letaido's Clay integrations, an AI agent searches Clay and runs your Clay functions, then uses the results in 64 other apps.
Search and enrichment work, each checked step by step. Open one to watch it run.
On request, the agent runs your Clay function on every domain in a sheet and writes what it returns back to each row.
Every morning, the agent runs your Clay function on yesterday's new HubSpot companies and fills in their empty fields.
On request, the agent searches Clay's people database for the marketing leaders at the companies you name and lists them with their LinkedIn links.
On request, the agent searches Clay for the marketing lead at each account with an open deal and adds the missing ones as Salesforce contacts.
When someone mentions Letaido in Slack with a company domain, the agent runs your Clay function and replies in the thread.
On request, the agent searches Clay's people database for your buyer profile and adds new matches to a prospects tab.
How teams get Clay data into other tools, side by side.
| Option | Describe it in words | Uses your other apps | Runs without you | No code | Thousands of apps |
|---|---|---|---|---|---|
| Yes | Yes | Yes | Yes | No | |
| Clay's native integrations | No | Partly | Yes | Yes | No |
| HTTP API column and webhooks | No | Yes | Yes | Partly | Yes |
| Clay Public API | No | Partly | Yes | No | Partly |
| Clay MCP | Yes | No | No | Yes | No |
| Option | How it works | Best for | Watch out for |
|---|---|---|---|
| Letaido AI agent | You describe the job. The agent searches Clay, runs your Clay functions and writes the results to 64 other apps, on a schedule, on another app's event, or when you ask. | Getting Clay data into the CRM, sheet or Slack thread where your team works. | 65 apps, not thousands. Functions must already exist in Clay; the API can't build them. |
| Clay's native integrations | Built-in connections in Clay tables, such as Salesforce, HubSpot, Outreach and Salesloft. | Pushing table rows into your CRM or sales tools. | You build each table and its columns in Clay. |
| HTTP API column and webhooks | A table column that calls any web address, and webhooks that send rows to tools like Zapier. | Tools Clay doesn't connect to. | You set up each request and its fields. |
| Clay Public API | Developers call Clay with an API key to search, run functions and read workflow runs. | In-house tools and backend jobs. | Code to write and keep running. Reading a table needs API table sync turned on for it. |
| Clay MCP | Clay's MCP server lets reps use Clay's find and enrich tools from AI tools such as ChatGPT, Claude or Microsoft Copilot. | Research while you chat. | Only inside your chat app, while you use it. |
Connect Clay once. After that, you describe each job in plain English.
Allow all read operations once per app; approve each kind of write once.
Make it a daily automation.
A schedule or you asking. Another app's event, like a Slack mention, can start one too.
In Clay, open API and CLI, then API keys, and add a key with the Public API scope.
Add the key to Letaido's Clay connector.
To run a Clay function, open it in Clay, check API and CLI reads Enabled, and copy the Routine ID (function:t_...) from its Integrations panel.
Allow all read operations once per app; approve each kind of write once. Save the job as an automation when the result looks right.
15 actions in 6 groups, from search to functions and run history.
Create a Clay API key with the Public API scope under API and CLI, then API keys, and paste it into the Clay connector in Letaido.
Yes, by Routine ID. Open the function in Clay, check API and CLI reads Enabled, and copy the ID from its Integrations panel. Paste it into the chat when you ask for the job.
Yes. A function run spends credits the same way it would if you ran it in Clay.
Yes, Clay offers MCP for reps who work in AI chat tools. Letaido is not an MCP server: its Clay connector is built in, and saved jobs can write Clay results to HubSpot, Salesforce, Sheets or Slack on a schedule.
Through Clay's MCP, inside a chat. Letaido runs saved Clay jobs with nobody in the chat, like the 7am HubSpot company fill.
Only tables with Clay's API table sync turned on. Without it, the agent works with search and functions.
Allow all read operations once per app; approve each kind of write once.
Connect Clay, then ask for a job like "Enrich our sheet of companies with Clay". Leta gets it done on your schedule, or the moment you ask.
Get LetaidoSearch Clay's people and company database and page through the results.
Run your Clay functions on up to 100 items and read the results.
Run Clay functions on up to 5,000 items at once as a batch.
Read rows from Clay tables, with filters, grouping and sorting.
Search, count, and review Clay workflow run history including status, timing, and credits consumed per run.
Check which workspace the key reaches and its credit balance, and make a general API request for anything else.