Change Conversation Assignee

Updates a conversation assignee in Kommunicate.

PUT

Query

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

string

Comma-separated response fields to include.

Body

Arguments

stringrequired

Conversation identifier to update.

stringrequired

Human agent email or ID to assign to the conversation.

boolean

Whether Kommunicate should send a notification message; defaults to true.

boolean

Remove bots from the conversation when true.

stringrequired

Admin or agent user ID to route into the required Of-User-Id header.

Try this request

Request

curl --request PUT \
  --url "https://connect.mindcloud.co/v1/universal/kommunicate/0.0.7/actions/change-conversation-assignee" \
  --header "Authorization: Bearer $MINDCLOUD_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
  "connectionId": "$CONNECTION_ID",
  "groupId": "",
  "assignee": "",
  "ofUserId": ""
}'

{
  "success": true,
  "data": [
    {
      "generatedAt": 1,
      "response": "string",
      "status": "string"
    }
  ],
  "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.