add_comment
Destructive
Add an internal comment to a ticket, keeping it hidden from the requestor. Attach files or log work time while updating the ticket.
Instructions
Add an internal comment to a ticket (not visible to the requestor)
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Ticket ID | |
| Content | No | Comment text (optional if Attachments provided) | |
| TimeTaken | No | Minutes of work time to log | |
| Attachments | No | Files to attach. Provide either FilePath (local file path, server reads and encodes it) or FileContent (pre-encoded MIME Base64). FileName and FileType are optional with FilePath and are inferred from the path. | |
| ContentType | No | Content MIME type (default text/plain) | |
| CustomFields | No | Ticket custom field values to set while adding this comment, as {CF_name: value}. Each value replaces everything the field currently holds, so for a multi-value field pass an array of the complete set you want ({"Tags": ["Red", "Blue"]}) — to add to existing values, read them with get_ticket first and include them. RT silently ignores names it does not recognize, including transaction custom fields (not supported here), so a success response does not confirm a field was set. Use get_queue_fields to see the custom fields available on the ticket's queue. |