# Notify Intercom of a new conversation created in a custom channel

Notifies Intercom that a new conversation was created in your custom channel/platform. This triggers conversation creation and workflow automations within Intercom for your custom channel integration.
>  This endpoint is currently under managed availability. Please reach out to your accounts team to discuss access and tailored, hands-on support.


Endpoint: POST /custom_channel_events/notify_new_conversation
Version: 2.14
Security: bearerAuth

## Request fields (application/json):

  - `event_id` (string, required)
    Unique identifier for the event.

  - `external_conversation_id` (string, required)
    Identifier for the conversation in your application.

  - `contact` (object, required)

  - `contact.type` (string, required)
    Type of contact, must be "user" or "lead".
    Enum: "user", "lead"

  - `contact.external_id` (string, required)
    External identifier for the contact. Intercom will take care of the mapping of your external_id with our internal ones so you don't have to worry about it.

  - `contact.name` (string)
    Name of the contact. Required for user type.

  - `contact.email` (string)
    Email address of the contact. Required for user type.

## Response 200 fields (application/json):

  - `external_conversation_id` (string, required)
    The external conversation ID provided in the notification request

  - `conversation_id` (string, required)
    The Intercom conversation ID mapped to the external conversation ID

  - `external_contact_id` (string, required)
    The external contact ID provided in the notification request

  - `contact_id` (string, required)
    The Intercom contact ID mapped to the external contact ID

## Response 400 fields (application/json):

  - `type` (string, required)
    The type is error.list
    Example: "error.list"

  - `request_id` (string,null)
    Example: "f93ecfa8-d08a-4325-8694-89aeb89c8f85"

  - `errors` (array, required)
    An array of one or more error objects

  - `errors.code` (string, required)
    A string indicating the kind of error, used to further qualify the HTTP response code
    Example: "unauthorized"

  - `errors.message` (string,null)
    Optional. Human readable description of the error.
    Example: "Access Token Invalid"

  - `errors.field` (string,null)
    Optional. Used to identify a particular field or query parameter that was in error.
    Example: "email"

## Response 401 fields (application/json):

  - `type` (string, required)
    The type is error.list
    Example: "error.list"

  - `request_id` (string,null)
    Example: "f93ecfa8-d08a-4325-8694-89aeb89c8f85"

  - `errors` (array, required)
    An array of one or more error objects

  - `errors.code` (string, required)
    A string indicating the kind of error, used to further qualify the HTTP response code
    Example: "unauthorized"

  - `errors.message` (string,null)
    Optional. Human readable description of the error.
    Example: "Access Token Invalid"

  - `errors.field` (string,null)
    Optional. Used to identify a particular field or query parameter that was in error.
    Example: "email"

## Response 404 fields (application/json):

  - `type` (string, required)
    The type is error.list
    Example: "error.list"

  - `request_id` (string,null)
    Example: "f93ecfa8-d08a-4325-8694-89aeb89c8f85"

  - `errors` (array, required)
    An array of one or more error objects

  - `errors.code` (string, required)
    A string indicating the kind of error, used to further qualify the HTTP response code
    Example: "unauthorized"

  - `errors.message` (string,null)
    Optional. Human readable description of the error.
    Example: "Access Token Invalid"

  - `errors.field` (string,null)
    Optional. Used to identify a particular field or query parameter that was in error.
    Example: "email"

## Response 422 fields (application/json):

  - `type` (string, required)
    The type is error.list
    Example: "error.list"

  - `request_id` (string,null)
    Example: "f93ecfa8-d08a-4325-8694-89aeb89c8f85"

  - `errors` (array, required)
    An array of one or more error objects

  - `errors.code` (string, required)
    A string indicating the kind of error, used to further qualify the HTTP response code
    Example: "unauthorized"

  - `errors.message` (string,null)
    Optional. Human readable description of the error.
    Example: "Access Token Invalid"

  - `errors.field` (string,null)
    Optional. Used to identify a particular field or query parameter that was in error.
    Example: "email"