Clay data on new Salesforce leads
Every morning, the agent runs your Clay function on the past day's new Salesforce leads and fills in their empty title, industry and employee fields.
Combine Clay + Salesforce and move enrichment data into Salesforce. Just ask Letaido's AI agent and watch it do the work.
Use this Clay Salesforce integration to fill in new leads, add missing buyers and find new accounts.
Every morning, the agent runs your Clay function on the past day's new Salesforce leads and fills in their empty title, industry and employee fields.
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.
The agent profiles accounts you won in the past year, finds companies in Clay with the same profile and adds new ones as Salesforce accounts.
Clay's connector lives in Clay tables. Leta works from a chat request or a saved timer.
| Option | Fills empty Salesforce fields | Adds new Salesforce records | Finds people at deal accounts | Runs on its own |
|---|---|---|---|---|
| Yes | Yes | Yes | Yes | |
| Clay's Salesforce integration | Yes | Yes | Yes | Yes |
| Zapier | Partly | Yes | Partly | Yes |
| Option | How a run begins | Good at | Keep in mind |
|---|---|---|---|
| Letaido AI agent | A timer you save by chatting with Leta, or a one-off request | New lead details from your Clay function, missing buyers at open deal accounts, and new accounts shaped like your won ones | Records aren't mirrored between the apps. Clay tables are never edited. Function jobs need the Routine ID and use Clay credits. Search jobs use your search result allowance. Nothing in either app kicks off a run |
| Clay's Salesforce integration | Set up in a Clay table: Salesforce list views or reports come in as a source, re-synced every 24 hours by default, and action columns run by hand or on auto-update | SOQL lookups, plus create, update, upsert and lead convert actions on Salesforce records, next to Clay's own search and enrichment in the same table | Made by Clay; its pricing page puts CRM integrations on Growth and above. Each table and its column to field mapping is yours to build, and Clay can't undo a change it made in Salesforce |
| Zapier | A Salesforce trigger like New Lead, New Record or Updated Record, which Zapier polls for | Ready-made Zaps that put new Salesforce leads or records into a Clay table, with Clay steps to add or find a row and Salesforce steps to create, update or find records | Zapier lists Salesforce as a Premium app. Enrichment inside Clay, field mapping and writing results back to Salesforce are all yours to set up |
Saved as an automation, like “Clay data on new Salesforce leads”: every morning at 7am. Neither app sends events to Letaido.
One message, 82 Clay and Salesforce actions to draw on.
Allow all read operations once per app; approve each kind of write once.
API request · Query workflow runs · Start routine batch · Get search query reference
Get limits · Delete record · Query all · List dashboards
Yes, Clay's own Salesforce connector imports list views and reports into a Clay table and writes records back from it. Leta skips the table: say what you need in chat, or save it to repeat, and it reads both apps and writes to Salesforce.
Add a Clay API key that has Public API access, and connect Salesforce once your admin has done the one time setup. For jobs built on a Clay function you made, give Leta that function's Routine ID.
Running one of your Clay functions uses Clay credits, the same as running it inside Clay. Searching Clay's company or people database uses up your plan's search result allowance, one per record returned.
The lead job only fills empty fields, and leaves out an industry that isn't one of your picklist values. The open deals job skips people whose name is already among the account's contacts. The new accounts job skips a company only when its domain exactly matches an existing account's website and keeps your duplicate rules on, but accounts with no website aren't caught.
No. Neither Clay nor Salesforce sends events to Letaido, so a change in either app can't start a job. Pick a time instead, like 7am each day, or type the request whenever you need it.
Allow all read operations once per app; approve each kind of write once.
Connect Clay and Salesforce, then ask for a job like "Enrich new Salesforce leads with Clay every morning". Leta gets it done on your schedule, or the moment you ask.
Get Letaido