Assign a conversation
Example Request & Response (Assigning to Admin)
$ curl https://api.intercom.io/conversations/{id}/parts \\\n-X POST \\\n-H 'Authorization:Bearer <Your access token>' \\\n-H 'Accept:application/json' \\\n-H 'Content-Type:application/json' -d\n\n{\n \"type\": \"admin\",\n \"admin_id\": \"814860\",\n \"assignee_id\": \"814860\",\n \"message_type\": \"assignment\",\n \"body\": \"Reassigning for X reason.\",\n}Example Request & Response (Auto Assignment)
$ curl 'https://api.intercom.io/conversations/{id}/run_assignment_rules'\n-X POST \n-H 'Authorization: Bearer <Your access token>' \n-H 'Accept: application/json' \n-H 'Content-Type: application/json'\nYou can assign a conversation to an admin and/or team. You can also let it be automatically assigned following assignment rules.
Request Path Parameters
| Parameter | Required? | Description |
|---|---|---|
| id | Yes | The identifier for the conversation as given by Intercom. |
| run_assignment_rules | No | Runs through all assignment rules created in the Intercom Inbox product for a given workspace. |
Request Body Parameters
📘
No body parameters are required when auto assigning conversations using the
{id}/run_assignment_rulespath parameter.
| Argument | Type | Required? | Description |
|---|---|---|---|
| message_type | String | Yes | Always assignment. |
| type | String | Yes | Accepts admin or team. |
| admin_id | String | Yes | The id of the admin who is performing the action. |
| assignee_id | String | Yes | The id of the admin or team which will be assigned the conversation.A conversation can be assigned both an admin and a team. Set 0 if you want this assign to no admin or team (ie. Unassigned). |
| body | String | No | Optionally you can leave a note in the conversation for additional context to other teammates. |
Response
This will return the Conversation that has been assigned.