> ## 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.

# CRM integrations

> Choose a connected CRM, inspect its live schema, and write only reviewed customer-data changes.

[Human guide: work with your agent →](https://deepline.com/docs/human/features/crm-integrations.md)

> [!NOTE]
>
> Choose a CRM action and verify one authorized change against its actual record
> and field contract.

Use a CRM integration after you have reviewed the record, owner, and intended
change. A CRM is a system of record. Deepline can read and write supported CRM
resources, but it does not infer permission to create, update, delete, or
reassign a record.

> [!WARNING]
>
> A CRM write can change another team's source of truth. Search or read the
> target first, show the proposed mutation, then perform it only with explicit
> approval.

## Choose your CRM

These are the current CRM integrations in the Deepline catalog. Each provider
guide links to its current generated or maintained contract.

> **[Affinity](https://deepline.com/docs/providers/affinity/guide.md)**
>
> Work with people, companies, lists, opportunities, interactions, and notes.

> **[Attio](https://deepline.com/docs/providers/attio/guide.md)**
>
> Search and upsert records, manage lists and pipeline entries, and receive
> CRM events through a Monitor.

> **[HubSpot](https://deepline.com/docs/providers/hubspot/guide.md)**
>
> Read and write standard or custom CRM objects, activities, associations, and
> tickets.

> **[Pipedrive](https://deepline.com/docs/providers/pipedrive/guide.md)**
>
> Read pipelines and records, then make explicit record changes with your
> token.

> **[Salesforce](https://deepline.com/docs/providers/salesforce/guide.md)**
>
> Inspect fields, read incrementally, and write Accounts, Contacts, Leads, or
> Opportunities.

> **[Zoho CRM](https://deepline.com/integrations/zoho_crm)**
>
> Use the connected OAuth workspace for records, metadata, automation, and
> bulk jobs.

## A safe CRM write pattern

1. Search or read the record using the provider's live schema.
2. Keep the record ID, current owner, and relevant existing values in the
   review context.
3. Show exactly which fields or associations would change.
4. Apply the approved write.
5. Read the record again and report the returned state.

The exact action IDs and payloads are provider-specific. Discover them from
the current catalog instead of copying a field name between CRMs:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline search --type tools "HubSpot update contact"
deepline describe hubspot_update_contact
```

## Related pages

* [Set up a Monitor](https://deepline.com/docs/plays/set-up-a-monitor.md)
* [Query Database](https://deepline.com/docs/database-access.md)
* [Sequencer integrations](https://deepline.com/docs/features/email-sequencer-integration.md)
* [API reference](https://deepline.com/docs/api-reference.md)

## Verify this task

Inspect the destination ID, permitted properties, prior value, and read-back state. Reconcile ambiguous outcomes before repeating writes.

Ask your agent to explain a failed check before repeating work or expanding the scope.


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