Update Engagement by ID

Updates an existing engagement record in HubSpot.

PUT

Query

Field selectionChoose which fields should be included in the response. Learn more

string

Comma-separated response fields to include.

Body

Arguments

stringrequired

HubSpot activity object type to update.

stringrequired

HubSpot record ID of the engagement to update.

objectrequired

Engagement property values keyed by HubSpot property name.

Uncommon arguments

string

Optional unique property name to use instead of the internal record ID.

Try this request

Request

curl --request PUT \
  --url "https://connect.mindcloud.co/v1/universal/hubspotApp/0.0.76/actions/update-engagement-by-id" \
  --header "Authorization: Bearer $MINDCLOUD_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
  "connectionId": "$CONNECTION_ID",
  "engagementType": "",
  "engagementId": "",
  "properties": ""
}'

{
  "success": true,
  "data": [
    {
      "archived": true,
      "createdAt": "2026-05-07T12:00:00.000Z",
      "id": "string",
      "objectWriteTraceId": "string",
      "properties": {},
      "updatedAt": "2026-05-07T12:00:00.000Z"
    }
  ],
  "meta": {}
}

Every app you connect,one REST pattern

Call any app with one REST pattern. MindCloud handles each provider's auth, request shape, and responses for you.

Learn what the Universal API is

One REST patternUse the same request structure across apps like Slack, HubSpot, Salesforce, and thousands more.

Managed connectionsSend a MindCloud connection ID instead of handling provider tokens, refresh logic, and credential storage yourself.

Action-level docsEach action page shows the exact endpoint, required arguments, optional controls, and response behavior for that app version.