Integration design
Salesforce governance is stricter than most CRMs — plan accordingly:
- Dedicated integration profile with least-privilege: create/update on target objects only. No admin user for routine writes.
- Object scope: usually Account + Contact; Lead only when your routing model needs it. Fewer objects, fewer surprises.
- Field-level security checked before the first run — a profile that cannot see a field fails writes per-record, confusingly.
Write rules
Agree source-of-truth per field before connecting. Common pattern: Clay owns firmographic and enrichment fields; Salesforce owns lifecycle fields (owner, stage, activity); never both. Upsert on external ID (website domain) rather than name matching.
Change control
Test in a sandbox. Production CRM writes deserve the same discipline as production code: sample pilot, provenance fields, failure alerts, and a documented rollback (what to null out) if a bad enrichment propagates.
Need help applying this?
Describe your project and the ClayForEnterprises team will review it — the resources stay free either way.