Skip to content

Remove contact from the accepted from types when creating a conversation #753

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
yasser-aboelgheit-intercom merged 1 commit into from
Oct 27, 2026
Merged

Remove contact from the accepted from types when creating a conversation #753

Show file tree
Hide file tree
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
3 changes: 1 addition & 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 @@ -13798,7 +13798,7 @@ paths:
The conversation can be an in-app message only.

{% admonition type="info" name="Sending for visitors" %}
You can also send a message from a visitor by specifying their `user_id` or `id` value in the `from` field, along with a `type` field value of `contact`.
You can also send a message from a visitor by specifying their `id` value in the `from` field, along with a `type` field value of `lead`.
This visitor will be automatically converted to a contact with a lead role once the conversation is created.
{% /admonition %}

Expand Down Expand Up @@ -37806,7 +37806,6 @@ components:
enum:
- lead
- user
- contact
description: The role associated to the contact - user or lead.
example: user
id:
Expand Down
3 changes: 1 addition & 2 deletions descriptions/2.17/api.intercom.io.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14056,7 +14056,7 @@ paths:
The conversation can be an in-app message only.

{% admonition type="info" name="Sending for visitors" %}
You can also send a message from a visitor by specifying their `user_id` or `id` value in the `from` field, along with a `type` field value of `contact`.
You can also send a message from a visitor by specifying their `id` value in the `from` field, along with a `type` field value of `lead`.
This visitor will be automatically converted to a contact with a lead role once the conversation is created.
{% /admonition %}

Expand Down Expand Up @@ -33404,7 +33404,6 @@ components:
enum:
- lead
- user
- contact
description: The role associated to the contact - user or lead.
example: user
id:
Expand Down
Loading