Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Request Type → Get One Request Type

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve detailed information about a specific "Request Type" entity. The "Get One Request Type" operation fetches data for a single request type identified by its unique ID, optionally filtering or enriching the response with various query parameters.

Typical use cases include:

  • Automating workflows that require fetching metadata or configuration details about a particular request type in a service management system.
  • Integrating request type details into reporting or ticketing automation.
  • Enriching tickets or requests with additional contextual information from the request type definition.

For example, you might use this node to get the configuration and status options of a request type before creating or updating tickets programmatically.

Properties

Name Meaning
Id The unique identifier (number) of the request type to retrieve.
Can Create Only Boolean filter to include only statuses that are created.
Can Edit Only Boolean filter to include only statuses that can be edited.
Debug Boolean flag to include debug information in the API response.
Includeconfig Boolean flag to include configuration details in the response.
Includedetails Boolean flag to include extra related objects in the response.
Includekbinfo Boolean flag to include knowledge base information in the response.
Includeteamrestrictions Boolean flag to include team restriction information.
Isdetailscreen Boolean flag, purpose unspecified but likely to indicate if the request is from a detail screen.
Isnewticket Boolean flag, possibly indicating if the request relates to a new ticket context.
Survey Fields Boolean flag to include survey fields in the response.
Ticket Id Integer filter to specify a related ticket ID for filtering the request type.

Output

The node outputs JSON data representing the requested "Request Type" object as returned by the Halo PSA API. This includes all standard fields of the request type plus any additional data included based on the optional query parameters set.

If enabled, debug information and related entities such as configuration, knowledge base info, team restrictions, and survey fields may also be present in the output JSON.

The node does not output binary data.

Dependencies

  • Requires an active connection to the Halo PSA API via an API key credential.
  • The node expects credentials containing the base URL, tenant identifier, client ID, and client secret for authentication.
  • No other external dependencies are required.

Troubleshooting

  • No credentials returned!: This error occurs if the node cannot find or access the required API credentials. Ensure that valid credentials are configured in n8n.
  • Resource or Operation not found: If the specified resource or operation is invalid or missing, verify that the correct resource ("Request Type") and operation ("Get One Request Type") are selected.
  • API request errors: Network issues, invalid IDs, or permission problems may cause API request failures. Check the error message returned in the output JSON for details.
  • JSON parsing errors: If using advanced JSON parameters, ensure they are correctly formatted.

Links and References

Discussion