Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

X Type Mapping → Get One X Type Mapping

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the "X Type Mapping" resource and the "Get One X Type Mapping" operation, it retrieves a single mapping entry identified by its unique ID. This is useful when you need to fetch detailed information about a specific type mapping within your PSA system.

Common scenarios include:

  • Fetching configuration details of a particular type mapping to use in automation workflows.
  • Validating or synchronizing data between Halo PSA and other systems by retrieving exact mappings.
  • Debugging or auditing specific mappings by extracting their full details.

Example: You want to get the details of an X Type Mapping with ID 123, optionally including extra details if supported, to process or display in your workflow.

Properties

Name Meaning
Id The unique numeric identifier of the X Type Mapping to retrieve.
Includedetails Optional flag or parameter to specify whether to include additional details in response.

Output

The node outputs JSON data representing the retrieved X Type Mapping object from the Halo PSA API. The structure corresponds directly to the API's response for that resource, typically including fields such as the mapping's ID, name, related types, and any additional details if requested.

If the operation fails or the item is not found, the output JSON will contain an error message describing the issue.

No binary data output is produced by this operation.

Dependencies

  • Requires valid credentials for the Halo PSA API, including base URL, tenant identifier, client ID, and client secret.
  • The node uses these credentials to authenticate requests via custom headers.
  • No additional external dependencies beyond the Halo PSA API and n8n's HTTP request capabilities.

Troubleshooting

  • No credentials returned!
    Ensure that the API credentials are properly configured and connected in n8n before running the node.

  • Resource or Operation not found errors
    Verify that the selected resource and operation names match those supported by the node.

  • HTTP request failures (e.g., 404, 401)
    Check that the provided ID exists and that the credentials have sufficient permissions.

  • JSON parsing errors
    If using advanced parameters like query strings or JSON bodies, ensure they are correctly formatted.

  • Continue On Fail behavior
    If enabled, the node will return error messages in the output JSON instead of stopping execution, allowing workflows to handle errors gracefully.

Links and References

Discussion