> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Intercom: Create Conversation

> Start an Intercom conversation with a message from a contact. Includes SDK V2 guidance, input constraints, response fields, and Deepline credit cost.

Start an Intercom conversation with a message from a contact.

> [!NOTE]
>
> Tool ID: `intercom_create_conversation`

## Run this action

This action has conditional or dynamic inputs. A static example cannot describe these inputs reliably.

Read the live contract before you execute this action:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline describe intercom_create_conversation --json
```

## Example response

The SDK returns this shape at `result.toolResponse.raw`. The example values illustrate the response.

```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
{
  "data": {
    "type": "example",
    "id": "id_123",
    "created_at": 123,
    "body": "Example message",
    "message_type": "email"
  }
}
```

Use `deepline describe intercom_create_conversation --json` for the latest machine-readable contract.

## Input reference

Conversations are how you can communicate with users in Intercom. They are created when a contact replies to an outbound message, or when one admin directly sends a message to a single contact.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.from` | `object` | Yes | — | — |
| `payload.body` | `string` | Yes | — | The content of the message. HTML is not supported. |
| `payload.subject` | `string` | No | — | The title of the email. Only applicable if the message type is email. |
| `payload.attachment_urls` | `array` | No | — | A list of image URLs that will be added as attachments. You can include up to 10 URLs. Maximum items: 10. |
| `payload.created_at` | `integer` | No | — | The time the conversation was created as a UTC Unix timestamp. If not provided, the current time will be used. This field is only recommneded for migrating past conversations from another source into Intercom. Format: `date-time`. |

<details>
  <summary>Show raw input schema</summary>

  ### Input JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "Conversations are how you can communicate with users in Intercom. They are created when a contact replies to an outbound message, or when one admin directly sends a message to a single contact.",
    "properties": {
      "from": {
        "type": "object",
        "properties": {
          "type": {
            "type": "string",
            "description": "The role associated to the contact - user or lead.",
            "enum": [
              "lead",
              "user",
              "contact"
            ]
          },
          "id": {
            "type": "string",
            "description": "The identifier for the contact which is given by Intercom.",
            "minLength": 24,
            "maxLength": 24,
            "format": "uuid"
          }
        },
        "required": [
          "type",
          "id"
        ],
        "additionalProperties": false
      },
      "body": {
        "type": "string",
        "description": "The content of the message. HTML is not supported."
      },
      "subject": {
        "type": "string",
        "description": "The title of the email. Only applicable if the message type is email."
      },
      "attachment_urls": {
        "type": "array",
        "description": "A list of image URLs that will be added as attachments. You can include up to 10 URLs.",
        "maxItems": 10,
        "items": {
          "type": "string",
          "format": "uri"
        }
      },
      "created_at": {
        "type": "integer",
        "description": "The time the conversation was created as a UTC Unix timestamp. If not provided, the current time will be used. This field is only recommneded for migrating past conversations from another source into Intercom.",
        "format": "date-time"
      }
    },
    "required": [
      "from",
      "body"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output reference

Standard tool result payload.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `result.data` | `object` | Yes | — | Message are how you contact contacts in Intercom. They are created when an admin sends an outbound message to a contact. |
| `result.data.type` | `string` | Yes | — | The type of the message |
| `result.data.id` | `string` | Yes | — | The id representing the message. |
| `result.data.created_at` | `integer` | Yes | — | The time the conversation was created. Format: `date-time`. |
| `result.data.subject` | `string` | No | — | The subject of the message. Only present if message\_type: email. |
| `result.data.body` | `string` | Yes | — | The message body, which may contain HTML. |
| `result.data.message_type` | `"email" \| "inapp" \| "facebook" \| "twitter"` | Yes | — | The type of message that was sent. Can be email, inapp, facebook or twitter. Allowed: `email`, `inapp`, `facebook`, `twitter`. |
| `result.data.conversation_id` | `string` | No | — | The associated conversation\_id |
| `result.meta` | `object` | No | — | Additional response metadata (status, paging). |

<details>
  <summary>Show raw output schema</summary>

  ### Output JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "Standard tool result payload.",
    "properties": {
      "data": {
        "type": "object",
        "description": "Message are how you reach out to contacts in Intercom. They are created when an admin sends an outbound message to a contact.",
        "properties": {
          "type": {
            "type": "string",
            "description": "The type of the message"
          },
          "id": {
            "type": "string",
            "description": "The id representing the message."
          },
          "created_at": {
            "type": "integer",
            "description": "The time the conversation was created.",
            "format": "date-time"
          },
          "subject": {
            "type": "string",
            "description": "The subject of the message. Only present if message_type: email."
          },
          "body": {
            "type": "string",
            "description": "The message body, which may contain HTML."
          },
          "message_type": {
            "type": "string",
            "description": "The type of message that was sent. Can be email, inapp, facebook or twitter.",
            "enum": [
              "email",
              "inapp",
              "facebook",
              "twitter"
            ]
          },
          "conversation_id": {
            "type": "string",
            "description": "The associated conversation_id"
          }
        },
        "required": [
          "type",
          "id",
          "created_at",
          "body",
          "message_type"
        ],
        "additionalProperties": false
      },
      "meta": {
        "type": "object",
        "description": "Additional response metadata (status, paging).",
        "additionalProperties": true
      }
    },
    "required": [
      "data"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Deepline cost

* Pricing model: `fixed` (per call).
* Estimated Deepline credits: `0` per pricing unit.
* Provider-native pricing may still exist outside Deepline credit billing.

## Related documentation

* [Intercom provider guide](https://deepline.com/docs/providers/intercom/guide.md)
* [SDK V2 quickstart](https://deepline.com/docs/sdk-v2/quickstart.md)
* [SDK reference](https://deepline.com/docs/sdk-v2/sdk-reference.md)
* [Run tools across a CSV](https://deepline.com/docs/sdk-v2/batch-csv.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.