From d20f289f2dce67a7a94f210cde80a824a4318ee1 Mon Sep 17 00:00:00 2001 From: Rahul D'Souza Date: Tue, 28 Jul 2026 17:38:49 +0100 Subject: [PATCH 1/2] Document Fin Agent replying status in v2.16 Co-Authored-By: Claude --- descriptions/2.16/api.intercom.io.yaml | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/descriptions/2.16/api.intercom.io.yaml b/descriptions/2.16/api.intercom.io.yaml index a05459a..0525e8a 100644 --- a/descriptions/2.16/api.intercom.io.yaml +++ b/descriptions/2.16/api.intercom.io.yaml @@ -3971,7 +3971,7 @@ paths: Please reach out to your accounts team to discuss access. {% /admonition %} - Once Fin is initialized, it progresses through a series of statuses such as *thinking*, *awaiting_user_reply*, or *resolved* before ending with a status of *complete*. + Once Fin is initialized, it progresses through a series of statuses such as *thinking*, *replying*, *awaiting_user_reply*, or *resolved* before ending with a status of *complete*. During this workflow, the client should allow Fin to continue uninterrupted until a final *complete* status is returned via webhook, at which point control of the conversation passes back to the client. responses: @@ -4016,6 +4016,7 @@ paths: type: string enum: - thinking + - replying - awaiting_user_reply - escalated - resolved @@ -4203,6 +4204,7 @@ paths: type: string enum: - thinking + - replying - awaiting_user_reply - escalated - resolved @@ -31316,11 +31318,13 @@ components: status: type: string enum: + - awaiting_user_reply - escalated - resolved - complete description: | Fin's current status. + - awaiting_user_reply: Fin has finished replying and is waiting for the user to respond - escalated: The conversation has been escalated to a human - resolved: The user's query has been resolved - complete: Fin has completed its workflow @@ -31354,7 +31358,7 @@ components: description: | Event fired when Fin replies to a user. Delivered via webhooks or SSE. The content of the response will be contained in the message object. - Fin's status will update to 'awaiting_user_reply'. + Intermediate replies have status 'replying'; a separate fin_status_updated event with 'awaiting_user_reply' fires as a done signal. x-tags: - Fin Agent properties: @@ -31402,9 +31406,13 @@ components: status: type: string enum: + - replying - awaiting_user_reply - description: Fin's current status (always 'awaiting_user_reply' for this event). - example: awaiting_user_reply + description: | + Fin's current status. + - replying: Intermediate reply part; more parts may follow + - awaiting_user_reply: Legacy status; use fin_status_updated event as the done signal instead + example: replying stream_id: type: string description: | @@ -35363,7 +35371,7 @@ tags: Configure a webhook endpoint in the Fin Agent API settings to receive events, or use the `sse_subscription_url` from the API response to subscribe via SSE. See the [setup guide](/docs/guides/fin-agent-api/setup) for configuration details. - - `fin_status_updated` - Fired when Fin's status changes (escalated, resolved, complete) + - `fin_status_updated` - Fired when Fin's status changes (awaiting_user_reply, escalated, resolved, complete) - `fin_replied` - Fired when Fin sends a reply to the user - `fin_reply_chunk` - SSE-only streaming event fired during reply generation (requires streaming enabled) From 405f91f4b5ce178b23db13a116301862b3b20894 Mon Sep 17 00:00:00 2001 From: Rahul D'Souza Date: Wed, 29 Jul 2026 14:00:35 +0100 Subject: [PATCH 2/2] Reword 'done signal' phrasing in 2.16 fin_replied descriptions Co-Authored-By: Claude --- descriptions/2.16/api.intercom.io.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/descriptions/2.16/api.intercom.io.yaml b/descriptions/2.16/api.intercom.io.yaml index 0525e8a..2c3e664 100644 --- a/descriptions/2.16/api.intercom.io.yaml +++ b/descriptions/2.16/api.intercom.io.yaml @@ -31358,7 +31358,7 @@ components: description: | Event fired when Fin replies to a user. Delivered via webhooks or SSE. The content of the response will be contained in the message object. - Intermediate replies have status 'replying'; a separate fin_status_updated event with 'awaiting_user_reply' fires as a done signal. + Intermediate replies have status 'replying'; a separate fin_status_updated event with 'awaiting_user_reply' fires once Fin's reply is done. x-tags: - Fin Agent properties: @@ -31411,7 +31411,7 @@ components: description: | Fin's current status. - replying: Intermediate reply part; more parts may follow - - awaiting_user_reply: Legacy status; use fin_status_updated event as the done signal instead + - awaiting_user_reply: Legacy status; instead use the fin_status_updated event with 'awaiting_user_reply', which fires once Fin's reply is done example: replying stream_id: type: string