Skip to main content
The agent resolves destination records, compares current values with evidence, and applies your writer-precedence policy. The first pilot produces proposals without changing the CRM.

Field policy and sample

Provide stable CRM IDs, target fields, accepted sources, freshness rules, writer precedence, and protected fields. For HubSpot, verify internal property names, value types, and owner IDs. Connection access does not authorize a particular record change. Each source record needs a proposal, unchanged result, or exception. Keep source/destination IDs, current/proposed values, acceptance rule, workflow version, and run ID. Record observation and retrieval times separately; fetching old evidence today does not make it fresh.
  • Keep ambiguous or protected changes for review. Job changes and stale pipeline fields do not justify guessed owners, stages, dates, or commercial terms.
  • Review expected usage and the read-back plan before the lookup pilot.
  • Apply only approved fields, verify their destination values, and reconcile timeouts before repeating an update.

Attio records

Have the agent inspect the object’s writable attribute slugs/IDs and value types before mapping a proposed update. Select the exact existing record, preserve rep-owned values, and read it back after approval. Upserts, new records, tasks, and schema changes are separate decisions.An owner or admin connects the intended workspace through OAuth, or saves a workspace access_token in the credential form when an API token is needed. The agent can guide the private-file setup; tokens stay out of chat. A connection does not create an event subscription or Play webhook.
See Validate CSV files for import checks and Query a database for permitted evidence storage. Review and operate a workflow covers authorization, pilots, and recovery. Agent guide: CLI and SDK instructions →