Integrations

Update Crm Contact

Partially update a CRM contact. Omitted fields are left alone.

Sending emails: [] REPLACES the addresses with none; omitting emails leaves them. The difference is the reason this is not a PATCH-shaped merge - the app's model distinguishes "absent" from "empty" and so does this one.

put/integrations/crm/connections/{connection_id}/contacts/{contact_id}

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/integrations/crm/connections/{connection_id}/contacts/{contact_id}
  • Auth: HTTP bearer

Path parameters

connection_idstring required

The CRM connection to act through.

contact_idstring required

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

namestring nullable
first_namestring nullable
last_namestring nullable
company_idstring nullable
company_namestring nullable
titlestring nullable
user_idstring nullable
is_activeboolean nullable
tagsstring[] nullable

Response

Successful Response

dataCrmPayload required

One CRM record, or one provider response.

Open-shaped ON PURPOSE. These bodies carry whatever the provider returned, the field set differs between HubSpot, Salesforce, Pipedrive and SugarCRM, and it grows every time one of them ships something. Pinning it would drop whatever a provider reported that this contract had not caught up on - which on a CRM surface means silently hiding the customer's own data from them.

Changes

No recorded changes to this operation across all 2 revisions of this API.