> ## 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 Reply Ticket: Inputs, Cost & CLI Example

> Reply to a ticket. Intercom Intercom Reply Ticket docs include request fields, response shape, pricing notes, and Deepline CLI examples.

## Run in Enrichment Spreadsheet

<Info>
  Use this function as a column step in `deepline enrich`.
</Info>

```bash theme={null}
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=intercom_reply_ticket:{"ticket_id":"{{ticket_id}}"}' --json
```

<Tip>
  Map payload values to spreadsheet columns with `{{column_name}}` placeholders.
</Tip>

## Input Schema

| Name                         | Type      | Required | Default | Description                                                                                                                                                                                                                                                                                               |
| ---------------------------- | --------- | -------- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `payload.ticket_id`          | `string`  | Yes      |         | The id of the ticket to target. \{% admonition type="info" name="Not the Inbox ticket ID" %} This is the internal `id` field from the API response, not the `ticket_id` displayed in the Intercom Inbox (e.g., #12345). Use the `id` value from the ticket object returned by the API. \{% /admonition %} |
| `payload.skip_notifications` | `boolean` | No       |         | Option to disable notifications when replying to a Ticket.                                                                                                                                                                                                                                                |

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

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "You can reply to a ticket with a message from an admin or on behalf of a contact, or with a note for admins.",
    "properties": {
      "ticket_id": {
        "type": "string",
        "description": "The id of the ticket to target. {% admonition type=\"info\" name=\"Not the Inbox ticket ID\" %} This is the internal `id` field from the API response, not the `ticket_id` displayed in the Intercom Inbox (e.g., #12345). Use the `id` value from the ticket object returned by the API. {% /admonition %}"
      },
      "skip_notifications": {
        "type": "boolean",
        "description": "Option to disable notifications when replying to a Ticket."
      }
    },
    "required": [
      "ticket_id"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output Schema

| Name          | Type     | Required | Default | Description                                                             |
| ------------- | -------- | -------- | ------- | ----------------------------------------------------------------------- |
| `result.data` | `object` | Yes      |         | A Ticket Part representing a note, comment, or quick\_reply on a ticket |
| `result.meta` | `object` | No       |         | Additional response metadata (status, paging).                          |

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

  ### Output JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Standard tool result payload.",
    "properties": {
      "data": {
        "type": "object",
        "description": "A Ticket Part representing a note, comment, or quick_reply on a ticket",
        "properties": {
          "type": {
            "type": "string",
            "description": "Always ticket_part",
            "enum": [
              "ticket_part"
            ]
          },
          "id": {
            "type": "string",
            "description": "The id representing the part."
          },
          "part_type": {
            "type": "string",
            "description": "Type of the part",
            "enum": [
              "note",
              "comment",
              "quick_reply"
            ]
          },
          "body": {
            "type": [
              "string",
              "null"
            ],
            "description": "The message body, which may contain HTML."
          },
          "created_at": {
            "type": "integer",
            "description": "The time the note was created.",
            "format": "date-time"
          },
          "updated_at": {
            "type": "integer",
            "description": "The last time the note was updated.",
            "format": "date-time"
          },
          "author": {
            "type": "object",
            "description": "The author that wrote or triggered the part. Can be a bot, admin, team or user.",
            "properties": {
              "type": {
                "type": "string",
                "description": "The type of the author",
                "enum": [
                  "admin",
                  "bot",
                  "team",
                  "user"
                ]
              },
              "id": {
                "type": "string",
                "description": "The id of the author"
              },
              "name": {
                "type": [
                  "string",
                  "null"
                ],
                "description": "The name of the author"
              },
              "email": {
                "type": "string",
                "description": "The email of the author",
                "format": "email"
              }
            },
            "additionalProperties": false
          },
          "attachments": {
            "type": "array",
            "description": "A list of attachments for the part.",
            "items": {
              "type": "object",
              "description": "The file attached to a part",
              "properties": {
                "type": {
                  "type": "string",
                  "description": "The type of attachment"
                },
                "name": {
                  "type": "string",
                  "description": "The name of the attachment"
                },
                "url": {
                  "type": "string",
                  "description": "The URL of the attachment"
                },
                "content_type": {
                  "type": "string",
                  "description": "The content type of the attachment"
                },
                "filesize": {
                  "type": "integer",
                  "description": "The size of the attachment"
                },
                "width": {
                  "type": "integer",
                  "description": "The width of the attachment"
                },
                "height": {
                  "type": "integer",
                  "description": "The height of the attachment"
                }
              },
              "additionalProperties": false
            }
          },
          "redacted": {
            "type": "boolean",
            "description": "Whether or not the ticket part has been redacted."
          }
        },
        "additionalProperties": false
      },
      "meta": {
        "type": "object",
        "description": "Additional response metadata (status, paging).",
        "additionalProperties": true
      }
    },
    "required": [
      "data"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Advanced: Direct CLI

<Info>
  Use direct execution for single payload debugging.
</Info>

```bash theme={null}
deepline tools execute intercom_reply_ticket --payload '{
  "ticket_id": "string"
}' --json
```

### CLI flags

| Flag                        | Description                                         |
| --------------------------- | --------------------------------------------------- |
| `--json`                    | Print machine-readable output.                      |
| `--wait`                    | Wait for terminal provider status when supported.   |
| `--debug`                   | Enable wait mode with additional status/log output. |
| `--wait-timeout SECONDS`    | Max seconds to wait in wait mode.                   |
| `--poll-interval SECONDS`   | Polling interval in seconds during wait mode.       |
| `--timeout SECONDS`         | Request timeout in seconds.                         |
| `--connect-timeout SECONDS` | Connection timeout in seconds.                      |

## Cost

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