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

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.
</Warning>

## Choose your CRM

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

<CardGroup cols={3}>
  <Card title="Affinity" icon="network" href="/docs/providers/affinity/guide">
    Work with people, companies, lists, opportunities, interactions, and notes.
  </Card>

  <Card title="Attio" icon="database" href="/docs/providers/attio/guide">
    Search and upsert records, manage lists and pipeline entries, and receive
    CRM events through a Monitor.
  </Card>

  <Card title="HubSpot" icon="orbit" href="/docs/providers/hubspot/guide">
    Read and write standard or custom CRM objects, activities, associations, and
    tickets.
  </Card>

  <Card title="Pipedrive" icon="columns-3" href="/docs/providers/pipedrive/guide">
    Read pipelines and records, then make explicit record changes with your
    token.
  </Card>

  <Card title="Salesforce" icon="cloud" href="/docs/providers/salesforce/guide">
    Inspect fields, read incrementally, and write Accounts, Contacts, Leads, or
    Opportunities.
  </Card>

  <Card title="Zoho CRM" icon="table-properties" href="/docs/providers/zoho-crm/guide">
    Use the connected OAuth workspace for records, metadata, automation, and
    bulk jobs.
  </Card>
</CardGroup>

## 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={null}
deepline tools search "HubSpot update contact" --json
deepline tools describe hubspot_update_contact --json
```

## Monitor CRM events; use Plays for decisions

If an ongoing supported CRM event should enter Deepline, use a
[Monitor](/docs/plays/monitors). Today, Attio CRM events have a dedicated Monitor
endpoint. The Monitor stores accepted event rows; a Play decides whether to
route, enrich, draft, or propose a CRM update. For computed work such as
[deal risk review](/docs/plays/signal-deal-risk), use a Play even when the input
originated from a CRM event.

## Related pages

* [Set up a Monitor](/docs/plays/set-up-a-monitor)
* [Query Customer DB](/docs/database-access)
* [Sequencer integrations](/docs/features/email-sequencer-integration)
* [API reference](/docs/api-reference)