Skip to main content
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.
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

Work with people, companies, lists, opportunities, interactions, and notes.

Attio

Search and upsert records, manage lists and pipeline entries, and receive CRM events through a Monitor.

HubSpot

Read and write standard or custom CRM objects, activities, associations, and tickets.

Pipedrive

Read pipelines and records, then make explicit record changes with your token.

Salesforce

Inspect fields, read incrementally, and write Accounts, Contacts, Leads, or Opportunities.

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:

Monitor CRM events; use Plays for decisions

If an ongoing supported CRM event should enter Deepline, use a Monitor. 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, use a Play even when the input originated from a CRM event.