> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# HubSpot enrichment workflows: safe CRM write-back

> Ask your agent to prepare HubSpot enrichment with controlled write-back.

[Agent guide: CLI and SDK instructions →](/docs/guides/hubspot-enrichment-workflows)

## 1. Have your context ready

Have the HubSpot account, target records, permitted properties, and rules for protecting trusted values.

## 2. Ask your agent

Paste this into your agent, then provide your task and example inputs when it asks:

```deepline-prompt theme={null}
/deepline-gtm Prepare HubSpot enrichment through Deepline for these records. Inspect the actual HubSpot properties, record identities, and allowed write operations. Return proposed changes with previous values, evidence, and reasons before writing. Preserve trusted fields under my precedence rule and hold ambiguous matches. Propose a small pilot and wait for approval before provider work or any CRM mutation.
```

Complete any requested sign-in yourself. Give the agent the missing information before approving execution. Provider-backed work can incur usage.

## 3. Review the result

Approved changes are read back from the intended records. Failed or uncertain writes remain visible and are reconciled before retrying.

Ask your agent:

```deepline-prompt theme={null}
/deepline-gtm Compare the result with the acceptance rule we agreed. Show the evidence for accepted and rejected outcomes, unresolved questions, and recorded Deepline usage where work ran. If work is still running or a response is uncertain, inspect the original saved execution before proposing another request. Explain the next decision I need to make.
```

Approve a larger job, recurring work, or external changes only after reviewing that decision.

## Check your understanding

Can a missing contact email justify creating a new CRM record without checking existing identity?

> **Show the answer**
>
> No. Resolve the existing person or company first. Missing email is not proof
> that no CRM record exists.

## Related guides

* [Enrich Free Trial Signups Without Blocking Onboarding](/docs/human/guides/free-trial-signup-enrichment)
* [Enrich a Company Domain into a Checked Account Record](/docs/human/guides/company-domain-enrichment)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.