> ## 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 Detach Tag From Ticket: Inputs, Cost & CLI

> Remove tag from a ticket. Intercom Intercom Detach Tag From 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_detach_tag_from_ticket:{"ticket_id":"{{ticket_id}}","tag_id":"{{tag_id}}","admin_id":"{{admin_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      |         | ticket\_id                                                      |
| `payload.tag_id`    | `string` | Yes      |         | The unique identifier for the tag which is given by Intercom    |
| `payload.admin_id`  | `string` | Yes      |         | The unique identifier for the admin which is given by Intercom. |

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

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "You can remove tag from a specific ticket. This will return a tag object for the tag that was removed from the ticket.",
    "properties": {
      "ticket_id": {
        "type": "string",
        "description": "ticket_id"
      },
      "tag_id": {
        "type": "string",
        "description": "The unique identifier for the tag which is given by Intercom"
      },
      "admin_id": {
        "type": "string",
        "description": "The unique identifier for the admin which is given by Intercom."
      }
    },
    "required": [
      "ticket_id",
      "tag_id",
      "admin_id"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output Schema

| Name          | Type     | Required | Default | Description                                                                                         |
| ------------- | -------- | -------- | ------- | --------------------------------------------------------------------------------------------------- |
| `result.data` | `object` | Yes      |         | A tag allows you to label your contacts, companies, and conversations and list them using that tag. |
| `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 tag allows you to label your contacts, companies, and conversations and list them using that tag.",
        "properties": {
          "type": {
            "type": "string",
            "description": "value is \"tag\""
          },
          "id": {
            "type": "string",
            "description": "The id of the tag"
          },
          "name": {
            "type": "string",
            "description": "The name of the tag"
          },
          "applied_at": {
            "type": [
              "integer",
              "null"
            ],
            "description": "The time when the tag was applied to the object. Only present when the tag is returned as part of a tagging operation on a contact, conversation, or ticket.",
            "format": "date-time"
          },
          "applied_by": {
            "type": [
              "object",
              "null"
            ],
            "description": "reference to another object",
            "properties": {
              "type": {
                "type": "string"
              },
              "id": {
                "type": [
                  "string",
                  "null"
                ]
              }
            },
            "additionalProperties": false
          }
        },
        "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_detach_tag_from_ticket --payload '{
  "ticket_id": "string",
  "tag_id": "string",
  "admin_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`.