AddComment

This activity helps the user to add a new comment to the specific ticket ID.

Properties

Configuration

Once you select the respective project name where Zendesk has been authenticated, the activity will automatically retrieve the available connections for that project.

If you have not added the connection, click here to learn more. 

Below are the properties available after the project has been integrated:

Zendesk: *This parameter indicates the account name associated with the integration.

INPUT

CommentBody: *This parameter indicates to provide the body of the comment against the specific ticket ID.

It accepts the input value in “String” datatype. You can either hardcode the values in “String” format variable or provide the values in “String” datatype.

CommentType: It indicates to choose the comment type as “Public” or “Private”. 

Public: It allows the user to add a comment publicly which will be visible for every user. 
Private: It allows the user to add a comment privately which will be visible only to specific group agents. 

TicketID: *This parameter indicates to provide the “TicketID” against where the comment needs to be added. 

It accepts the input value in “String” datatype. You can either hardcode the values in “String” format variable or provide the values in “String” datatype.

Uploads: This parameter indicates to upload any attachments in the comments against ticket ID. Use the “TokenID” retrieved from “Upload Attachments” activity. 

It accepts the input value in “List of String” datatype. You can either hardcode the values in “String” format variable or provide the values in “String” datatype.
Note: If you are uploading only single attachment to the comments, the value must be provided as “New list (Of string for {“Token ID”}) or (New list (Of string for {variable})”.
If you are uploading multiple attachments to the comments, the value must be provided as “{“TokenID1”, “TokenID2″}”.

MISC

DisplayName: Displays the name of the activity. The activity name can be customized, which aids in troubleshooting.

SkipOnError: Specify the “Boolean” value as “True” or “False.”
True: Continue executing the workflow regardless of any errors thrown.
False: Halt the workflow if it encounters any errors.
None: If the option is left blank, the activity will, by default, behave as if “False” were chosen.

Version: It indicates the version of the feature being used.

OUTPUT

CommentDetails: It helps to view the details of the comment added in the specific ticket ID. It returns the following data,

Comment ID: The unique identifier for the comment.
Ticket ID: The ID of the ticket to which the comment was added.
Author ID: The ID of the user or agent who authored the comment.
Comment Body: The text content of the comment.
Public/Private: Indicates whether the comment is visible to the end user (public) or only to internal agents (private).
Created At: The timestamp when the comment was created.
Updated At: The timestamp of the most recent update to the comment.

CommentID: It helps to view the comment ID as the result of the activity. It returns the values in String datatype.

Result: It provides the ability to view the execution status of the activity. It returns values in “Boolean.”
True: Indicates that the activity has been executed successfully without any errors.
False: Indicates that the activity has been unsuccessful due to an unexpected error being thrown.

* Represents mandatory fields to execute the workflow.