ServiceDesk Plus icon

ServiceDesk Plus

Interact with ManageEngine ServiceDesk Plus

Get Conversations

AI-generated

Overview

This node operation retrieves all conversations or messages associated with a specific ticket in ManageEngine ServiceDesk Plus. It can optionally fetch the full message content for each conversation, which provides a more complete view but may be slower. This is useful for scenarios where detailed communication history of a ticket is needed, such as customer support follow-ups or auditing ticket interactions.

Use Case Examples

  1. Fetch all conversations for a given ticket to review the communication history.
  2. Retrieve full content of each conversation to analyze detailed message exchanges within a ticket.

Properties

Name Meaning
Ticket ID The unique identifier of the ticket for which to retrieve conversations.
Include Full Content Whether to fetch the full message content for each conversation, which is slower but provides complete details.

Output

JSON

  • success - Indicates if the operation was successful.
  • ticketId - The ID of the ticket for which conversations were retrieved.
  • conversations
    • ``
      * full_content - Full message content of a conversation, present if 'Include Full Content' is true.
      * subject - Subject of the conversation message, present if full content is fetched.
      * notification_details - Additional notification details related to the conversation message.
      * content_fetch_error - Error message if fetching full content for a conversation failed.
  • includeFullContent - Boolean indicating if full content was included in the response.
  • conversationCount - Number of conversations retrieved for the ticket.

Dependencies

  • ManageEngine ServiceDesk Plus API
  • An API authentication token credential

Troubleshooting

  • Ensure the provided Ticket ID is valid and exists in the ServiceDesk Plus system.
  • If 'Include Full Content' is enabled, the operation may be slower due to additional API calls; consider disabling if performance is critical.
  • API authentication token must be valid and have sufficient permissions to access ticket conversations.
  • Errors fetching full content for individual conversations will be included in the output under 'content_fetch_error'.

Links

Discussion