Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Message Content → Get One Message Content

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve detailed information about a specific message content by its identifier. It is designed to fetch one message content item, optionally including additional details or filtering by message group.

Common scenarios for this node include:

  • Retrieving the full content of a particular message in a service management or ticketing system.
  • Accessing message metadata or related details for auditing or processing workflows.
  • Integrating message content retrieval into automated processes such as notifications, reporting, or data synchronization.

For example, you might use this node to get the content of a support ticket message by its ID and then use that content to trigger further actions like sending an email or updating a database.

Properties

Name Meaning
Id The unique numeric identifier of the message content to retrieve.
Includedetails Optional flag or parameter to specify whether to include additional details in response.
Messagegroup Optional parameter to filter or specify the message group associated with the content.

Output

The node outputs a JSON object representing the retrieved message content. This includes all fields returned by the Halo PSA API for the requested message content, potentially enriched with additional details if requested.

The output structure corresponds directly to the API response for a single message content entity, which may include properties such as message text, timestamps, author information, and any other metadata provided by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Halo PSA API.
  • Needs credentials containing the base URL, tenant identifier, client ID, and client secret for authentication.
  • The node uses HTTP requests with appropriate headers to authenticate and query the API.

Troubleshooting

  • Missing Credentials: If no credentials are provided or they are invalid, the node will throw an error indicating "No credentials returned!" Ensure that valid API credentials are configured.
  • Resource or Operation Not Found: Errors like Resource Message Content not found or Operation Get One Message Content not found for resource Message Content indicate misconfiguration of parameters. Verify that the resource and operation names are correct.
  • Invalid ID Parameter: Since the Id property is required and must be a number, providing an invalid or missing ID will cause the request to fail.
  • API Request Failures: Network issues, incorrect base URL, or authentication failures will result in errors from the API request. Check connectivity and credential correctness.
  • JSON Parsing Errors: If additional parameters are provided as JSON strings, ensure they are well-formed to avoid parsing exceptions.

Using the node's "Continue On Fail" option can help handle errors gracefully within workflows.

Links and References

Discussion