Skip to main content
POST
Write one critical competitor interaction onto the matched CRM company as a note, so the signal lands where the deal is worked rather than only in Clustr. It works the same way for HubSpot, Salesforce and Attio, so you do not choose a provider. Clustr composes the note body from the interaction’s stored verdict. Your request picks the interaction, and Clustr writes the text that lands in your system of record. Requires the account to resolve to a CRM company and your CRM connection to permit note creation; both fail as 403. Idempotent: an already-logged interaction returns 200 with already_logged: true rather than writing a second note, because your CRM would otherwise store a duplicate.

Authorizations

Authorization
string
header
required

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

Body

application/json
actor_linkedin_id
string
required

The Clustr ID (per_…) of the competitor's salesperson. Their LinkedIn id (rep_linkedin_id on the feed entry) also works.

target_linkedin_id
string
required

The engaged person's Clustr ID (per_…). Their LinkedIn id also works.

post_key
string
required

The interaction's post_key.

Response

Note written, or already present

success
boolean
required
Example:

true

data
object
required