From d4a6c5717321eedc8076665344e6c1eeedd6bb58 Mon Sep 17 00:00:00 2001 From: yasser-aboelgheit-intercom Date: Thu, 22 Oct 2026 08:41:36 +0100 Subject: [PATCH] Remove contact from the accepted from types when creating a conversation Co-Authored-By: Claude Opus 5.5 (1M context) --- descriptions/0/api.intercom.io.yaml | 3 +-- descriptions/2.17/api.intercom.io.yaml | 3 +-- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml index 605b1b06..3b5a7c91 100644 --- a/descriptions/0/api.intercom.io.yaml +++ b/descriptions/0/api.intercom.io.yaml @@ -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 %} @@ -37806,7 +37806,6 @@ components: enum: - lead - user - - contact description: The role associated to the contact - user or lead. example: user id: diff --git a/descriptions/2.17/api.intercom.io.yaml b/descriptions/2.17/api.intercom.io.yaml index c87a7a84..29c8b323 100644 --- a/descriptions/2.17/api.intercom.io.yaml +++ b/descriptions/2.17/api.intercom.io.yaml @@ -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 %} @@ -33404,7 +33404,6 @@ components: enum: - lead - user - - contact description: The role associated to the contact - user or lead. example: user id: