library
turbot/zendesk
OverviewPipelines
0
Triggers
0
Variables
GitHub

Pipeline: Update Ticket Comment

Update a ticket comment.

Run the pipeline

To run this pipeline from your terminal:

flowpipe pipeline run zendesk.pipeline.update_ticket_comment \
--arg 'comment=<object({
body = string
public = bool
author_id = number
})>' \
--arg 'ticket_id=<number>'

Use this pipeline

To call this pipeline from your pipeline, use a step:

step "pipeline" "step_name" {
pipeline = zendesk.pipeline.update_ticket_comment
args = {
comment = <object({
body = string
public = bool
author_id = number
})>
ticket_id = <number>
}
}

Params

NameTypeRequiredDescriptionDefault
cred
string
YesName for credentials to use. If not provided, the default credentials will be used.default
comment
object({
body = string
public = bool
author_id = number
})
YesAn object that defines the properties of the ticket comment.-
allow_attachments
bool
NoPermission for agents to add attachments to a comment. Defaults to true.-
allow_channelback
bool
NoIs false if channelback is disabled, true otherwise. Only applicable for channels framework ticket.-
assignee_email
string
NoWrite only. The email address of the agent to assign the ticket to.-
assignee_id
number
NoThe agent currently assigned to the ticket.-
attribute_value_ids
list(number)
NoWrite only. An array of the IDs of attribute values to be associated with the ticket.-
brand_id
number
NoEnterprise only. The ID of the brand this ticket is associated with.-
collaborator_ids
list(number)
NoThe IDs of users currently CC'ed on the ticket.-
collaborators
list(object({
      name  = string
      email = string
    }))
NoPOST requests only. Users to add as CC's when creating a ticket. See Setting Collaborators.-
created_at
string
NoWhen this record was created.-
custom_fields
list(object({
      id    = number
      value = string
    }))
NoCustom fields for the ticket. See Setting custom field values.-
custom_status_id
number
NoThe custom ticket status ID of the ticket. See custom ticket statuses.-
description
string
NoRead-only first comment on the ticket. When creating a ticket, use comment to set the description. See Description and first comment.-
due_at
string
NoIf this is a ticket of type 'task', it has a due date. Due date format uses ISO 8601 format.-
email_cc_ids
list(number)
NoThe IDs of agents or end users currently CC'ed on the ticket. See CCs and followers resources in the Support Help Center.-
email_ccs
list(object({
      user_id = number
      email   = string
    }))
NoWrite only. An array of objects that represent agent or end users email CCs to add or delete from the ticket. See Setting email CCs.-
external_id
string
NoAn ID you can use to link Zendesk Support tickets to local records.-
follower_ids
list(number)
NoThe IDs of agents currently following the ticket. See CCs and followers resources.-
ticket_id
number
YesAutomatically assigned when the ticket is created.-
followers
list(object({
      user_id = number
    }))
NoWrite only. An array of objects that represent agent followers to add or delete from the ticket. See Setting followers.-
followup_ids
list(number)
NoThe IDs of the followups created from this ticket. IDs are only visible once the ticket is closed.-
forum_topic_id
number
NoThe topic in the Zendesk Web portal this ticket originated from, if any. The Web portal is deprecated.-
from_messaging_channel
bool
NoIf true, the ticket's via type is a messaging channel.-
group_id
number
NoThe group this ticket is assigned to.-
has_incidents
bool
NoIs true if a ticket is a problem type and has one or more incidents linked to it. Otherwise, the value is false.-
is_public
bool
NoIs true if any comments are public, false otherwise.-
macro_id
number
NoWrite only. A macro ID to be recorded in the ticket audit.-
macro_ids
list(number)
NoPOST requests only. List of macro IDs to be recorded in the ticket audit.-
metadata
object({
data = map(any)
})
NoWrite only. Metadata for the audit. In the audit object, the data is specified in the custom property of the metadata object. See Setting Metadata.-
organization_id
number
NoThe organization of the requester. You can only specify the ID of an organization associated with the requester. See Organization Memberships.-
priority
string
NoThe urgency with which the ticket should be addressed. Allowed values are 'urgent', 'high', 'normal', or 'low'.-
problem_id
number
NoFor tickets of type 'incident', the ID of the problem the incident is linked to.-
raw_subject
string
NoThe dynamic content placeholder, if present, or the 'subject' value, if not. See Dynamic Content Items.-
recipient
string
NoThe original recipient e-mail address of the ticket. Notification emails for the ticket are sent from this address.-
requester
object({
name = string
email = string
})
NoWrite only. See Creating a ticket with a new requester.-
requester_id
number
NoThe user who requested this ticket.-
safe_update
bool
NoWrite only. Optional boolean. When true and an update_stamp date is included, protects against ticket update collisions and returns a message to let you know if one occurs. See Protecting against ticket update collisions. A value of false has the same effect as true. Omit the property to force the updates to not be safe.-
satisfaction_rating
object({
score = number
comment = string
reason = string
created_at = string
updated_at = string
assignee_id = number
group_id = number
requester_id = number
})
NoThe satisfaction rating of the ticket, if it exists, or the state of satisfaction, 'offered' or 'unoffered'. The value is null for plan types that don't support CSAT.-
sharing_agreement_ids
list(number)
NoThe IDs of the sharing agreements used for this ticket.-
status
string
NoThe state of the ticket. If your account has activated custom ticket statuses, this is the ticket's status category. See custom ticket statuses. Allowed values are 'new', 'open', 'pending', 'hold', 'solved', or 'closed'.-
subject
string
NoThe value of the subject field for this ticket.-
submitter_id
number
NoThe user who submitted the ticket. The submitter always becomes the author of the first comment on the ticket.-
tags
list(string)
NoThe array of tags applied to this ticket.-
ticket_form_id
number
NoEnterprise only. The ID of the ticket form to render for the ticket.-
type
string
NoThe type of this ticket. Allowed values are 'problem', 'incident', 'question', or 'task'.-
updated_at
string
NoWhen this record last got updated.-
updated_stamp
string
NoWrite only. Datetime of last update received from API. See the safe_update property.-
url
string
NoThe API URL of this ticket.-
via
object({
channel = string
})
NoFor more information, see the Via object reference.-
via_followup_source_id
number
NoPOST requests only. The ID of a closed ticket when creating a follow-up ticket. See Creating a follow-up ticket.-
via_id
number
NoWrite only. For more information, see the Via object reference.-
voice_comment
object({
value = string
})
NoWrite only. See Creating voicemail ticket.-

Outputs

NameDescription
ticketThe updated ticket comment.