Define the field policy
For each target field, name the identity rule, accepted evidence, freshness window, authoritative writer, protected values, and review owner. Choose rules for the decision the field supports: a formatted close date can still be stale, and a populated owner can still be wrong.
Set writer precedence explicitly. For example, a rep-confirmed phone takes precedence over an enrichment candidate, while enrichment may fill an empty phone field. If a CRM workflow also writes that field, agree which writer wins before enabling either update path. Exclusive ownership is a policy, not a database lock; concurrent writers still need destination-supported conflict handling or reconciliation.
Resolve the record and inspect the write contract
deepline describe <returned-id> --json. Confirm its required identifiers, property types, access mode, output, and price. A missing email does not establish that a contact is new: resolve the existing object before creating anything.
Read the current values and propose only the fields permitted by the policy. Keep identity merges, ownership changes, stages, and commercial terms for the specified reviewer. A provider response supplies evidence; it does not approve a CRM change.
Retain a field-level decision record
Persist the evidence your process needs in permitted customer-owned working data; Query a database covers storage access. This illustrative record is a workflow output you implement, not a built-in CRM audit format:Pilot proposals, then authorize writes
Authorcrm-data-quality-automation.play.ts using Build a Play. Declare the input, preserve source IDs, and implement the policy above. Keep external changes disabled in the authored logic for the first pilot.
HubSpot property mapping and uncertain writes
Inspect the current HubSpot integration for supported reads and updates. Resolve the existing contact ID and inspect property internal names and types; upstream API support does not imply the selected Deepline action accepts the same inputs. For the synthetic proposal above, map the accepted phone to the contact’sphone property only after confirming that map against the destination. Keep display labels out of the request mapping. The proposed change is:
Attio records
Map Attio attributes and verify workspace access
Map Attio attributes and verify workspace access
Connect the intended Attio workspace in Integrations. OAuth requires permission
to install the app. If the installation is blocked at Attio’s application
limit, save a workspace API access token as
access_token through the existing
credential form, or a private credential file with
deepline tools connect attio --credentials-file <path> --json. Grant only the
scopes needed by the planned operations; the connection test reads objects.
An active saved token takes precedence over OAuth. Replacing the workspace
requires replacing its credential.Inspect attio_list_attributes for the target object’s attribute slugs/IDs,
value types, and writable status. Use structured attio_query_records filters
for precise record selection. A company summary may map to description or a
custom research attribute only when the field policy permits that write.
Preserve rep-owned values and read the same record back after approval.Use assert operations when an upsert is intended; create and update are distinct
operations. Check the action’s treatment of matching and non-matching multiselect
attributes before overwriting them. Lists, notes, tasks, and schema changes are
separate authored operations, not automatic consequences of enrichment.An event-driven workflow also needs an explicit Attio subscription and
authenticated Play webhook; connecting the
workspace does not create a trigger. Inspect the current Monitor contract for
supported feeds.