Skip to main content
PUT
Sets which property of one connected CRM holds each owner, and which side may change it. Send only the owners you want to change; an owner you leave out keeps what is saved. Admin only.
  • company: the account owner. Attack competitor alerts mention it.
  • contact: a connector’s owner.
  • company_cs: the CS owner of a company. Defense competitor alerts mention it. It has no default field on any CRM, and it is only ever read from the CRM.
Every field is checked against the CRM’s live schema: it must exist, and it must hold a CRM user (unless allowAnyField). For company and contact, it must also be writable when the direction lets Clustr write to it. A changed field starts a sync, so owners reflect the new field without waiting for the nightly one (resync in the response). Competitor alerts read the mapped fields live from the CRM when they are sent, so they use a new field straight away.

CS owner from an associated object

On HubSpot, the CS owner can live on another record than the company: a custom object associated with it, such as a “communities” object. Set object on company_cs to that object’s type, and field to its owner property (hubspot_owner_id when you leave it empty). When a company has several associated records with an owner, the oldest record’s owner is used. Clustr reads this owner on every sync and never writes it, so the direction is saved as crm_owns.
Reading a custom object needs the HubSpot connection to include the custom object scopes.

Errors

Authorizations

Authorization
string
header
required

The API key you created on the API settings page of the Clustr app.

Query Parameters

provider
enum<string>
required

The CRM to read or change: hubspot, salesforce or attio. That CRM must be connected to your workspace.

Available options:
hubspot,
salesforce,
attio

Body

application/json
company
object

The account owner, on a CRM company.

contact
object

A connector's owner, on a CRM contact.

company_cs
object

The CS owner, on a CRM company. It is always read from your CRM, so its direction is crm_owns or off: both and an omitted direction are saved as crm_owns, and clustr_owns answers 400. Send field: "" to unmap it.

allowAnyField
boolean
default:false

Accept a field that holds something other than a CRM user. The field must still exist on the CRM.

Example:

false

Response

The saved owner field mappings

success
boolean
required
Example:

true

data
object
required