Show priority and admin_id as top-level params in the Preview update-conversation examples - #622
Merged
Apexinsideapex merged 1 commit intoAug 13, 2026
Conversation
…conversation examples
Apexinsideapex
force-pushed
the
rohitsharma/conversation-priority-preview-request-examples
branch
from
August 13, 2026 15:28
b9de162 to
5f4eb29
Compare
Apexinsideapex
changed the title
junaid-zaidi-intercom
approved these changes
Aug 13, 2026
Apexinsideapex
deleted the
rohitsharma/conversation-priority-preview-request-examples
branch
August 13, 2026 16:20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
The Preview update-conversation examples show
prioritynested insidecustom_attributes, where it means a workspace attribute that happens to share the name rather than the conversation priority the endpoint now accepts. Developers copy the example panel rather than the schema, so a request built from the page silently leaves the priority unchanged.How?
Adds the top-level
priorityandadmin_idparams to those examples and drops the same-named custom attribute that made the two ambiguous. Preview only, examples only.Generated with Claude Code