Skip to content

Align Preview fin_replied wording with 2.16 #611

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
geetikabagga merged 1 commit into from
Jul 29, 2026
Merged

Align Preview fin_replied wording with 2.16 #611

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions descriptions/0/api.intercom.io.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36040,7 +36040,7 @@ components:
Event fired when Fin replies to a user.
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.
event with 'awaiting_user_reply' fires once Fin's reply is done.
x-tags:
- Fin Agent
properties:
Expand Down Expand Up @@ -36093,7 +36093,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
Expand Down