Skip to main content
Human guide: work with your agent → Produce proposed CRM changes for a small sample. Confirm record identity and protected fields before enabling writes.

​
Before you start

Use an authorized workspace and a small file with stable source IDs. Have source access and your team’s acceptance policy available. This guide describes customer-authored logic, not an automatically enabled product policy.

​
1. Understand the decision

Technical permission to update a CRM does not decide which fields a workflow should change. Define business authority separately. Test this fictional sample before calling providers:

​
2. Inspect supported operations

Inspect a returned ID with deepline describe <returned-id> --json. Compare required identifiers, outputs, access mode, and price. A similar title does not establish that a contract fits.

​
3. Implement the bounded workflow

Ask your agent to author crm-workflow-automation.play.ts using Write Plays. Have it declare the CSV input and preserve source IDs. Reuse existing contracts when they fit the transformation. Implement these rules explicitly:
  1. Resolve the exact destination object and retain its stable ID.
  2. Read the current value and apply field ownership and precedence.
  3. Return proposals, evidence, and protected-field exclusions.
  4. Implement destination-supported idempotency or reconciliation before enabling writes.
Keep external changes disabled for the first pilot. That control belongs in the authored logic, not a universal Play dry-run flag.

​
4. Check and pilot

Prepare pilot.csv using CSV-safe selection. Then check the source:
Resolve authoring errors first. After reviewing source and price, run only the pilot:
Use the ID returned by the pilot. Select a returned dataset path when several exist. Provider-backed execution can incur usage.

​
5. Verify the outcome

Confirm the first pilot produced proposals without writing. For authorized write testing, compare observed state with the approved proposal.
Every source ID has a result or explicit exception. The fictional cases follow the stated policy, and actual results retain their evidence.
Ask your agent why a record was accepted, held, or rejected. Correct the rule before expanding input or enabling external writes.

​
Continue

CRM repair supplies field-level steps. Production integration covers external writes.