Skip to main content
PUT
Assign an owner to a connector that is already in your network. No reimport, no job, no credits. The change is immediate.
This is the connector’s owner: it moves the whole book. An opportunity also has its own owner, set with Update Opportunity, and this endpoint overwrites it on every opportunity the connector has. Use this one when someone takes over a relationship, and the other when a single intro is handed to a colleague.The other way to set this is owner_email on Import Connectors, at import time. This endpoint is how you set or change it afterwards, without reimporting.
Assigning an owner here does three things:
  1. The connector reports that owner in List Connectors and counts toward it in List Owners connector_count, connectors_by_tag and opportunity_count.
  2. Every opportunity the connector already has moves to that owner, so their book does not split between the old and the new owner.
  3. Opportunities discovered for that connector by later imports land owned, with no further calls.
Send owner_id or owner_email, not both.

Removing an owner

DELETE on the same path clears it. The connector reports no owner afterwards and newly discovered opportunities stop inheriting one. Opportunities already assigned keep the owner stamped on them, so a DELETE leaves a live book intact. Reassign the connector with PUT if that is what you meant. The DELETE is idempotent. Clearing an owner that is already absent succeeds.

Bulk assignment

Each call assigns one connector. Call this once per connector; the writes are independent, so they can run concurrently. To find the connectors that still need an owner, list them with List Connectors and ?owner_email=unassigned.

Authorizations

Authorization
string
header
required

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

Path Parameters

linkedinId
string
required

The connector's Clustr ID (per_…), from List Connectors. Their LinkedIn public identifier, the linkedin_id that list returns, also works: for https://www.linkedin.com/in/nicdelaye that is nicdelaye.

Body

application/json

Who should own this connector. Send either owner_id or owner_email.

owner_id
string

An owner's Clustr ID (own_…) from List Owners. The id from earlier responses also works.

owner_email
string<email>

The owner's email address, looked up in your owner directory: the same address you would send as owner_email when importing.

create_owner_if_missing
boolean
default:false

Adds owner_email to the owner directory when no owner holds it yet, instead of returning an error. Use it in self-service flows where the person being assigned may not be in the directory. It adds a name to the directory only, so it uses no seat, sends no email and grants no access. See Owners are a directory, not a seat.

owner_name
string

The display name for an owner that create_owner_if_missing creates. Used only when the owner is created.

push_to_crm
boolean
default:false

Also write the owner to the connector's CRM contact. Off by default, so each CRM write is a deliberate choice. When the owner mapping is set to "Clustr sets the value", Clustr pushes the owner whatever this flag says; when it is set to "Your CRM sets the value" or paused, the owner stays in Clustr. pushToCrm is accepted as the same flag.

The owner is saved in Clustr whether or not the push succeeds. See HubSpot, Salesforce and Attio.

pushToCrm
boolean

The same flag as push_to_crm.

Response

Owner assigned

success
boolean
required
data
object
required