The Salesforce data layer

The same read, enrich, write loop as the HubSpot version, against an org that has opinions about what it will accept.

Mechanically this is the CRM data layer again: read a filtered slice, fill the gaps, write it back, run it on a schedule. Everything true there is true here. What changes is that a mature Salesforce org has opinions encoded in it, and those opinions will reject your writes in ways that are entirely correct and completely opaque.

So the sequence is inverted. On HubSpot you build the table and then test the write. On Salesforce you test the write first, in a sandbox, with ten records, and design the table around what the org actually accepts. Teams that do it the other way round usually rebuild.

What will reject your writes

Validation rules, required fields, duplicate rules and Apex triggers all still apply to anything writing in, and a tool reporting a successful run is reporting that it sent the request. Read the error column rather than assuming a completed run also succeeded, and do it in a sandbox before anything touches production.

The pipeline, step by step

5 steps. The ones in blue are the data layer; everything else is plumbing you already own or can stand up in an afternoon.

01

Read what the org enforces

Before any table exists. Which fields are required, which validation rules fire on update, which triggers run, and what the duplicate rules do. This is an hour with an admin and it determines everything after it.

hour onewith an admin
↓
02

Read a filtered slice into Clay

Leads, contacts, accounts or opportunities missing the field you care about. Read-only, so nothing in the org changes and nothing needs approving yet.

read-onlynothing changes
↓
03

Reverse Contact fills the gaps

An HTTP API column against the enrich endpoints. Identical to the HubSpot version, because this step does not care what CRM is upstream of it.

1 callper gap row
↓
04

Write ten records to a sandbox

Not a hundred, not the whole slice. Ten, then read every error. This is where you find the required field nobody documented and the validation rule written in 2019 by somebody who has left.

10 rowssandbox only
↓
05

Promote to production, then schedule

Write to dedicated fields, promote into the trusted ones only where empty, and set the cadence from how fast the field goes stale. Then watch the API allocation for a week.

weeklyrefresh cycle

Build it with an agent

This workflow ships as a skill file: the API surface of every tool in the chain, the build order, the limits that break it, and how to check it worked. Point an agent at it and it has what it needs without reading 3 sets of vendor docs first.

salesforce-enrichment-loop/SKILL.md agent skill
---
name: salesforce-enrichment-loop
description: Build a scheduled enrichment loop against Salesforce, designed around the 
  org rules that reject writes: validation rules, required fields, duplicate r...
---

# The Salesforce data layer

## What you are building
## Prerequisites
## The tools, and how to call them   → Reverse Contact, Clay, Salesforce
## Build it                         → 6 steps
## Gotchas
## What breaks, from the vendors' own docs
## How to verify it works           → 5 checks
markdown Verified 2026-09-18
Drop it into Claude Code

mkdir -p .claude/skills/salesforce-enrichment-loop curl -o .claude/skills/salesforce-enrichment-loop/SKILL.md https://www.reversecontact.com/integrations-hub/skills/salesforce-data-layer.md

For Codex, Cursor, or anything else that reads a file or fetches a URL, hand it https://www.reversecontact.com/integrations-hub/skills/salesforce-data-layer.md directly. It is plain markdown with YAML frontmatter and no tool-specific syntax, so nothing in it depends on which agent is reading it.

3 of the joins in this chain have a full guide behind them, Salesforce and Clay and Salesforce and Reverse Contact among them. The chain crosses 3 of the seven layers a stack splits into, from the CRM layer outward, which is why no single vendor owns it.

What will bite

Documented by one of the vendors in the chain, and easier to design around than to discover.

API calls are a shared allocation
Salesforce meters daily API requests by edition and licence count, across every integration in the org. A large table writing row by row competes with your existing connectors for the same budget, and the symptom of running out is other people's integrations failing, which is an unpopular way to find out.
A completed run is not a successful write
Rejections from validation rules and triggers are not always loud upstream. Check the error column every run for the first fortnight, and alert on error rate rather than on job completion.
Clay bills the attempt, not the result
Same economics as everywhere else: effective cost per filled field is the action rate divided by your match rate. Filter the import tightly, because on Salesforce the temptation to pull a whole object is stronger.
You will need a sandbox and an admin
Both are scheduling problems rather than technical ones, and both sit on somebody else's queue. That is why this workflow is days rather than hours, and almost none of it is build time.

All four are documented by a vendor rather than observed by us, which is the useful part: a limit you can read is a limit you can design around before it costs you a week.

What it costs to run

What each component bills on, and which line actually scales with your volume.

ComponentBillingWhat drives it
SalesforceEdition with API accessAPI access is an edition feature. Without it, none of this runs regardless of what else you hold.
ClayPer actionRows imported multiplied by enrichment columns, charged on the attempt.
Reverse ContactPer creditOne call per gap row, 2 credits for a reverse lookup from an email. No dollar rate per lookup is published.
Admin timeDays, elapsedSandbox access, a change window and an hour reading validation rules. The real timeline.

Budget the elapsed time rather than the build time. The table is an afternoon. Getting a sandbox, an admin hour and a change window is the two weeks, and no amount of tooling shortens it.

Built by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every tier requirement, limit and sync direction in this chain was read from a vendor's own documentation, through the integration records each step rests on. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-09-18
Sources
12 vendor documents
Paid placement
None

This workflow runs on a data layer you can test free

Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, with a confidence score your logic can branch on. The free trial takes no card and runs until the 500 credits a new account starts with are spent, which is enough to run this end to end before anyone signs anything.

Free trial, no card required, and 500 credits to start.

Questions

Why do my enrichment writes to Salesforce fail?

Almost always a rule somebody wrote years ago: a required field the table is not populating, a validation rule the value breaks, or a duplicate rule catching the row. Start in a sandbox, write ten records, read every error, and design around what the org accepts rather than around what you expected.

Will this use up our API allocation?

It uses part of it. Salesforce meters daily API requests by edition and licence count across the whole org, so a row-by-row write competes with every other integration you run. Batch where you can, filter the slice tightly, and watch the allocation for the first week after you schedule it.

Is this different from the HubSpot data layer?

Not mechanically. The same read, enrich, write, schedule loop. What differs is that Salesforce will reject writes that HubSpot would accept, and that getting a sandbox and an admin takes longer than building the thing. Plan for the org, not for the tooling.

Do I need Clay, or can Flow do this?

Flow with an API callout can do it, and if an engineer or a capable admin owns the logic permanently that avoids a second meter. Clay earns its place when the enrichment logic is conditional and changes often, and when the person changing it does not have deploy rights in Salesforce.

Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.

Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.

Ask an assistant