Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Opps → Get One Faults

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve detailed information about a specific fault (ticket) within the "Opps" resource. The "Get One Faults" operation fetches data for a single fault identified by its unique ID, optionally including various related details such as linked objects, auditing info, appointments, and more.

Typical use cases include:

  • Fetching detailed fault/ticket information for customer support or service management workflows.
  • Automating ticket status checks or updates based on retrieved fault data.
  • Integrating fault details into broader IT service management or CRM processes.

For example, you might use this node to get all relevant information about a particular fault ticket before triggering notifications or updating other systems.

Properties

Name Meaning
Id The unique numeric identifier of the fault to retrieve. (Required)
Amailentryid Filter/query parameter for mail entry ID associated with the fault.
Assignedto Filter/query parameter specifying the assigned user or group.
Consignablelines Filter/query parameter related to consignable lines (specific meaning depends on API).
Debug Boolean flag to include debug information in the response.
Dodatabaselookup Query parameter to enable database lookup (specific behavior depends on API).
Email Filter/query parameter for email address related to the fault.
Include Auditing Boolean flag to include auditing information in the response.
Includeagent Query parameter to include agent details.
Includechildids Query parameter to include child IDs related to the fault.
Includedetails Boolean flag to include extra objects/details in the response.
Includelastaction Query parameter to include the last action performed on the fault.
Includelastappointment Boolean flag to include the last appointment related to the fault.
Includelinkedobjects Boolean flag to include linked objects in the response.
Includenextappointment Boolean flag to include the next appointment related to the fault.
Includeparentchangeinfo Query parameter to include parent change information.
Includeparentsubject Query parameter to include the subject of the parent fault/ticket.
Includeseenby Query parameter to include information about who has seen the fault.
Is Portal Query parameter indicating if the request is from a portal context.
Isdetailscreen Query parameter indicating if the request is from a detail screen context.
Ishalolink Query parameter related to Halo link integration.
Ispreview Query parameter indicating if the request is a preview.
Isteams Boolean flag to return only team tickets in the response.
Nocache Boolean flag indicating whether to cache the response.
Subject Filter/query parameter for the subject of the fault.
Ticketidonly Boolean flag to include only details related to the specified ticket.
Utcoffset Query parameter specifying the UTC offset for date/time fields.

Output

The node outputs JSON data representing the detailed fault information retrieved from the Halo PSA API. This includes the fault's core properties and any additional related data requested via the input parameters (such as auditing info, linked objects, appointments, etc.).

The output structure corresponds directly to the API response for a single fault, typically containing nested objects and arrays depending on included options.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Halo PSA API.
  • Requires configuration of credentials providing:
    • Base URL of the Halo PSA instance.
    • Tenant identifier.
    • Client ID and Client Secret for authentication.
  • The node uses HTTP requests with appropriate headers for authentication.
  • No additional external dependencies beyond the configured API credentials.

Troubleshooting

  • Missing Credentials Error: If no credentials are provided or invalid, the node will throw an error stating "No credentials returned!". Ensure that valid API credentials are configured.
  • Resource or Operation Not Found: Errors like "Resource Opps not found" or "Operation Get One Faults not found for resource Opps" indicate misconfiguration of resource or operation names.
  • API Request Failures: Network issues, incorrect base URL, or invalid authentication tokens can cause request failures. Check connectivity and credential validity.
  • JSON Parsing Errors: If JSON parameters are malformed, the node may fail parsing them. Validate JSON inputs carefully.
  • Continue On Fail Behavior: If enabled, errors during execution will be captured in the output JSON under an error field instead of stopping the workflow.

Links and References

Discussion