Intercom: Reply Ticket

Reply to a ticket.

Tool ID: intercom_reply_ticket

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'intercom_reply_ticket',
  {
    "ticket_id": "ticket_123"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute intercom_reply_ticket --input '{
  "ticket_id": "ticket_123"
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": {
    "type": "ticket_part",
    "id": "id_123",
    "part_type": "note"
  }
}

Use deepline tools get intercom_reply_ticket --json for the latest machine-readable contract.

Input reference

You can reply to a ticket with a message from an admin or on behalf of a contact, or with a note for admins.

Name	Type	Required	Default	Details
`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.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	A Ticket Part representing a note, comment, or quick_reply on a ticket
`result.data.type`	`"ticket_part"`	No	—	Always ticket_part Allowed: `ticket_part`.
`result.data.id`	`string`	No	—	The id representing the part.
`result.data.part_type`	`"note" \| "comment" \| "quick_reply"`	No	—	Type of the part Allowed: `note`, `comment`, `quick_reply`.
`result.data.body`	`string \| null`	No	—	The message body, which may contain HTML.
`result.data.created_at`	`integer`	No	—	The time the note was created. Format: `date-time`.
`result.data.updated_at`	`integer`	No	—	The last time the note was updated. Format: `date-time`.
`result.data.author`	`object`	No	—	The author that wrote or triggered the part. Can be a bot, admin, team or user.
`result.data.author.type`	`"admin" \| "bot" \| "team" \| "user"`	No	—	The type of the author Allowed: `admin`, `bot`, `team`, `user`.
`result.data.author.id`	`string`	No	—	The id of the author
`result.data.author.name`	`string \| null`	No	—	The name of the author
`result.data.author.email`	`string`	No	—	The email of the author Format: `email`.
`result.data.attachments`	`array`	No	—	A list of attachments for the part.
`result.data.attachments[].type`	`string`	No	—	The type of attachment
`result.data.attachments[].name`	`string`	No	—	The name of the attachment
`result.data.attachments[].url`	`string`	No	—	The URL of the attachment
`result.data.attachments[].content_type`	`string`	No	—	The content type of the attachment
`result.data.attachments[].filesize`	`integer`	No	—	The size of the attachment
`result.data.attachments[].width`	`integer`	No	—	The width of the attachment
`result.data.attachments[].height`	`integer`	No	—	The height of the attachment
`result.data.redacted`	`boolean`	No	—	Whether or not the ticket part has been redacted.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

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

Get started

Build and automate

Common workflows

Data and integrations

Reference

Intercom: Reply Ticket

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation