From 189e48dcc3f76c3e5d8c920bd96fc582f0a8978b Mon Sep 17 00:00:00 2001 From: dq Date: Tue, 25 Aug 2026 15:50:48 +0100 Subject: [PATCH 1/6] Add team_assigned_to to conversation part and ticket part schemas Co-Authored-By: Claude Opus 5 (1M context) --- descriptions/0/api.intercom.io.yaml | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml index 6012398..d0af989 100644 --- a/descriptions/0/api.intercom.io.yaml +++ b/descriptions/0/api.intercom.io.yaml @@ -32085,6 +32085,16 @@ components: nullable: true description: The id of the admin that was assigned the conversation by this conversation_part (null if there has been no change in assignment.) + team_assigned_to: + "$ref": "#/components/schemas/reference" + nullable: true + description: The team that this conversation_part assigned the conversation + to, when the part changed the team (null if the part did not change the + team). A part can assign a team and a teammate at the same time, for + example when the team uses Round Robin distribution and the teammate is + resolved inline. In that case assigned_to reports the teammate and this + field reports the team. When the part removed the team, type is + nobody_team and id is null. author: "$ref": "#/components/schemas/conversation_part_author" attachments: @@ -39754,6 +39764,15 @@ components: nullable: true description: The id of the admin that was assigned the ticket by this ticket_part (null if there has been no change in assignment.) + team_assigned_to: + "$ref": "#/components/schemas/reference" + nullable: true + description: The team that this ticket_part assigned the ticket to, when the + part changed the team (null if the part did not change the team). A part + can assign a team and a teammate at the same time, for example when the + team uses Round Robin distribution and the teammate is resolved inline. + In that case assigned_to reports the teammate and this field reports the + team. When the part removed the team, type is nobody_team and id is null. author: "$ref": "#/components/schemas/ticket_part_author" attachments: From 92daeeeb36c1d7314605489873acdf921388e001 Mon Sep 17 00:00:00 2001 From: dq Date: Wed, 26 Aug 2026 12:31:28 +0100 Subject: [PATCH 2/6] Use unassigned rather than nobody_team for a removed team Co-Authored-By: Claude Opus 5 (1M context) --- descriptions/0/api.intercom.io.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml index d0af989..648f2c4 100644 --- a/descriptions/0/api.intercom.io.yaml +++ b/descriptions/0/api.intercom.io.yaml @@ -32094,7 +32094,7 @@ components: example when the team uses Round Robin distribution and the teammate is resolved inline. In that case assigned_to reports the teammate and this field reports the team. When the part removed the team, type is - nobody_team and id is null. + unassigned and id is null. author: "$ref": "#/components/schemas/conversation_part_author" attachments: @@ -39772,7 +39772,7 @@ components: can assign a team and a teammate at the same time, for example when the team uses Round Robin distribution and the teammate is resolved inline. In that case assigned_to reports the teammate and this field reports the - team. When the part removed the team, type is nobody_team and id is null. + team. When the part removed the team, type is unassigned and id is null. author: "$ref": "#/components/schemas/ticket_part_author" attachments: From dda9d3adc2469877e1746d797bb927bb225a6f7f Mon Sep 17 00:00:00 2001 From: dq Date: Thu, 27 Aug 2026 09:13:31 +0100 Subject: [PATCH 3/6] Report part assignees as admin_assignee_id and team_assignee_id Co-Authored-By: Claude Opus 5 (1M context) --- descriptions/0/api.intercom.io.yaml | 45 ++++++++++++++++++----------- 1 file changed, 28 insertions(+), 17 deletions(-) diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml index 648f2c4..9a8fafe 100644 --- a/descriptions/0/api.intercom.io.yaml +++ b/descriptions/0/api.intercom.io.yaml @@ -32085,16 +32085,21 @@ components: nullable: true description: The id of the admin that was assigned the conversation by this conversation_part (null if there has been no change in assignment.) - team_assigned_to: - "$ref": "#/components/schemas/reference" + admin_assignee_id: + type: integer + nullable: true + description: The id of the teammate that this conversation_part assigned the + conversation to (null if the part did not assign a teammate, 0 if the part + removed the teammate). + team_assignee_id: + type: integer nullable: true - description: The team that this conversation_part assigned the conversation - to, when the part changed the team (null if the part did not change the - team). A part can assign a team and a teammate at the same time, for - example when the team uses Round Robin distribution and the teammate is - resolved inline. In that case assigned_to reports the teammate and this - field reports the team. When the part removed the team, type is - unassigned and id is null. + description: The id of the team that this conversation_part assigned the + conversation to (null if the part did not assign a team, 0 if the part + removed the team). A part can assign a team and a teammate at the same + time, for example when the team uses Round Robin distribution and the + teammate is resolved inline. In that case assigned_to reports only the + teammate, and these two fields report each assignee separately. author: "$ref": "#/components/schemas/conversation_part_author" attachments: @@ -39764,15 +39769,21 @@ components: nullable: true description: The id of the admin that was assigned the ticket by this ticket_part (null if there has been no change in assignment.) - team_assigned_to: - "$ref": "#/components/schemas/reference" + admin_assignee_id: + type: integer + nullable: true + description: The id of the teammate that this ticket_part assigned the ticket + to (null if the part did not assign a teammate, 0 if the part removed the + teammate). + team_assignee_id: + type: integer nullable: true - description: The team that this ticket_part assigned the ticket to, when the - part changed the team (null if the part did not change the team). A part - can assign a team and a teammate at the same time, for example when the - team uses Round Robin distribution and the teammate is resolved inline. - In that case assigned_to reports the teammate and this field reports the - team. When the part removed the team, type is unassigned and id is null. + description: The id of the team that this ticket_part assigned the ticket to + (null if the part did not assign a team, 0 if the part removed the team). + A part can assign a team and a teammate at the same time, for example when + the team uses Round Robin distribution and the teammate is resolved inline. + In that case assigned_to reports only the teammate, and these two fields + report each assignee separately. author: "$ref": "#/components/schemas/ticket_part_author" attachments: From 5082b02bccc43fe3bb5e91b255d0a3d56889cbcb Mon Sep 17 00:00:00 2001 From: dq Date: Thu, 27 Aug 2026 09:48:36 +0100 Subject: [PATCH 4/6] Note that the part assignee id fields can be absent as well as null Co-Authored-By: Claude Opus 5 (1M context) --- descriptions/0/api.intercom.io.yaml | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml index 9a8fafe..c7faca3 100644 --- a/descriptions/0/api.intercom.io.yaml +++ b/descriptions/0/api.intercom.io.yaml @@ -32089,16 +32089,16 @@ components: type: integer nullable: true description: The id of the teammate that this conversation_part assigned the - conversation to (null if the part did not assign a teammate, 0 if the part - removed the teammate). + conversation to. Null or absent when the part did not assign a teammate, and + 0 when the part removed the teammate. team_assignee_id: type: integer nullable: true description: The id of the team that this conversation_part assigned the - conversation to (null if the part did not assign a team, 0 if the part - removed the team). A part can assign a team and a teammate at the same - time, for example when the team uses Round Robin distribution and the - teammate is resolved inline. In that case assigned_to reports only the + conversation to. Null or absent when the part did not assign a team, and 0 + when the part removed the team. A part can assign a team and a teammate at + the same time, for example when the team uses Round Robin distribution and + the teammate is resolved inline. In that case assigned_to reports only the teammate, and these two fields report each assignee separately. author: "$ref": "#/components/schemas/conversation_part_author" @@ -39773,17 +39773,17 @@ components: type: integer nullable: true description: The id of the teammate that this ticket_part assigned the ticket - to (null if the part did not assign a teammate, 0 if the part removed the - teammate). + to. Null or absent when the part did not assign a teammate, and 0 when the + part removed the teammate. team_assignee_id: type: integer nullable: true - description: The id of the team that this ticket_part assigned the ticket to - (null if the part did not assign a team, 0 if the part removed the team). - A part can assign a team and a teammate at the same time, for example when - the team uses Round Robin distribution and the teammate is resolved inline. - In that case assigned_to reports only the teammate, and these two fields - report each assignee separately. + description: The id of the team that this ticket_part assigned the ticket to. + Null or absent when the part did not assign a team, and 0 when the part + removed the team. A part can assign a team and a teammate at the same time, + for example when the team uses Round Robin distribution and the teammate is + resolved inline. In that case assigned_to reports only the teammate, and + these two fields report each assignee separately. author: "$ref": "#/components/schemas/ticket_part_author" attachments: From 98dc6fc546aab07353bf3ab606d461b93b85addd Mon Sep 17 00:00:00 2001 From: dq Date: Thu, 27 Aug 2026 13:36:00 +0100 Subject: [PATCH 5/6] Correct when the part assignee ids return 0 0 only appears when the part named which assignee it cleared; an unassignment that named neither returns null on both. Also documents that a bot is reported in admin_assignee_id. Co-Authored-By: Claude Opus 5 (1M context) --- descriptions/0/api.intercom.io.yaml | 30 +++++++++++++++++------------ 1 file changed, 18 insertions(+), 12 deletions(-) diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml index c7faca3..868441f 100644 --- a/descriptions/0/api.intercom.io.yaml +++ b/descriptions/0/api.intercom.io.yaml @@ -32089,16 +32089,19 @@ components: type: integer nullable: true description: The id of the teammate that this conversation_part assigned the - conversation to. Null or absent when the part did not assign a teammate, and - 0 when the part removed the teammate. + conversation to, or 0 if the part removed the teammate. Null or absent when + the part did not change the teammate, including an unassignment that did not + name which assignee it cleared. A bot is reported here, because assignment + treats anything that is not a team as a teammate. team_assignee_id: type: integer nullable: true description: The id of the team that this conversation_part assigned the - conversation to. Null or absent when the part did not assign a team, and 0 - when the part removed the team. A part can assign a team and a teammate at - the same time, for example when the team uses Round Robin distribution and - the teammate is resolved inline. In that case assigned_to reports only the + conversation to, or 0 if the part removed the team. Null or absent when the + part did not change the team, including an unassignment that did not name + which assignee it cleared. A part can assign a team and a teammate at the + same time, for example when the team uses Round Robin distribution and the + teammate is resolved inline. In that case assigned_to reports only the teammate, and these two fields report each assignee separately. author: "$ref": "#/components/schemas/conversation_part_author" @@ -39773,15 +39776,18 @@ components: type: integer nullable: true description: The id of the teammate that this ticket_part assigned the ticket - to. Null or absent when the part did not assign a teammate, and 0 when the - part removed the teammate. + to, or 0 if the part removed the teammate. Null or absent when the part did + not change the teammate, including an unassignment that did not name which + assignee it cleared. A bot is reported here, because assignment treats + anything that is not a team as a teammate. team_assignee_id: type: integer nullable: true - description: The id of the team that this ticket_part assigned the ticket to. - Null or absent when the part did not assign a team, and 0 when the part - removed the team. A part can assign a team and a teammate at the same time, - for example when the team uses Round Robin distribution and the teammate is + description: The id of the team that this ticket_part assigned the ticket to, + or 0 if the part removed the team. Null or absent when the part did not + change the team, including an unassignment that did not name which assignee + it cleared. A part can assign a team and a teammate at the same time, for + example when the team uses Round Robin distribution and the teammate is resolved inline. In that case assigned_to reports only the teammate, and these two fields report each assignee separately. author: From d7a07aac00e2712f17922ac78d92c8504db6b2f3 Mon Sep 17 00:00:00 2001 From: dq Date: Thu, 27 Aug 2026 13:58:22 +0100 Subject: [PATCH 6/6] Add examples for the part assignee id fields Every other scalar property on the part schemas carries an example, and the endpoint response examples are what a reader checks the shape against, so the new fields need both. The assignment parts show the two shapes worth seeing: the conversation part is the Round Robin case with a teammate and a team set at once, the ticket part a plain teammate assignment. Co-Authored-By: Claude Opus 5 (1M context) --- descriptions/0/api.intercom.io.yaml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml index 868441f..08a8a94 100644 --- a/descriptions/0/api.intercom.io.yaml +++ b/descriptions/0/api.intercom.io.yaml @@ -14012,6 +14012,8 @@ paths: assigned_to: type: admin id: '991267715' + admin_assignee_id: 991267715 + team_assignee_id: 5017691 author: id: '991267715' type: admin @@ -23483,6 +23485,8 @@ paths: assigned_to: type: admin id: '991268013' + admin_assignee_id: 991268013 + team_assignee_id: null author: id: '991268011' type: admin @@ -32093,6 +32097,7 @@ components: the part did not change the teammate, including an unassignment that did not name which assignee it cleared. A bot is reported here, because assignment treats anything that is not a team as a teammate. + example: 991267715 team_assignee_id: type: integer nullable: true @@ -32103,6 +32108,7 @@ components: same time, for example when the team uses Round Robin distribution and the teammate is resolved inline. In that case assigned_to reports only the teammate, and these two fields report each assignee separately. + example: 5017691 author: "$ref": "#/components/schemas/conversation_part_author" attachments: @@ -39780,6 +39786,7 @@ components: not change the teammate, including an unassignment that did not name which assignee it cleared. A bot is reported here, because assignment treats anything that is not a team as a teammate. + example: 991268013 team_assignee_id: type: integer nullable: true @@ -39790,6 +39797,7 @@ components: example when the team uses Round Robin distribution and the teammate is resolved inline. In that case assigned_to reports only the teammate, and these two fields report each assignee separately. + example: 5017691 author: "$ref": "#/components/schemas/ticket_part_author" attachments: