crm-enrichment-sync
Use this when enriched data is ready to cross the boundary into the CRM. It turns a contact file or result set into an explicit, reversible write plan before changing any system of record.
Confirm the boundary
Require two inputs:
- a bounded contact set with identity, enriched fields, quality status, and provenance;
- an authenticated connection to the destination CRM that can inspect schema and search existing records.
Confirm the destination workspace, object type, owner or routing expectation, and business purpose. If the connector is absent or authentication fails, stop. Offer an import-ready file; never work around the missing connection.
The enrichment source is not the CRM writer. Keep retrieval and destination writes as separate operations with separate approvals.
Read the destination schema
Inspect standard and custom fields, required fields, data types, picklist values, ownership rules, uniqueness constraints, and batch limits. Do not map based on familiar labels alone: Phone, Mobile phone, and Direct dial may have different semantics.
Propose a field map with four decisions per source field: