HaloPSA Complete icon

HaloPSA Complete

Get data from the HaloPSA API

Actions68

Overview

This node updates an existing ticket in the HaloPSA system. It is useful for automating ticket management workflows, such as changing the assigned agent, updating the status or priority, adding details, or flagging tickets based on external triggers or internal processes. For example, you could use this node to automatically escalate tickets that have been open too long by updating their priority and notifying the assigned team.

Properties

Name Meaning
Ticket ID The unique identifier of the ticket to update (required).
Update Fields A collection of fields to update on the ticket. Options include:
- Agent ID: The ID of the agent assigned to the ticket.
- Category 1: Primary category classification of the ticket.
- Category 2: Secondary category classification.
- Details: Detailed description or notes about the ticket.
- Estimate (Hours): Estimated time to resolve the ticket.
- Flagged: Boolean indicating if the ticket is flagged for attention.
- On Hold: Boolean indicating if the ticket is currently on hold.
- Priority ID: Numeric priority level of the ticket.
- Status ID: Numeric status identifier representing the current state of the ticket.
- Summary: Short summary or subject line for the ticket.
- Team ID: The ID of the team assigned to the ticket.

Output

The node outputs JSON data representing the updated ticket object returned from the HaloPSA API after the update operation. This typically includes all ticket fields reflecting the new state post-update. If the API supports it, binary data output is not indicated for this operation.

Dependencies

  • Requires a valid API key credential for authenticating with the HaloPSA API.
  • The node depends on the HaloPSA API being accessible and responsive.
  • Proper permissions are needed on the API key to update tickets.
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Common issues:

    • Invalid or missing Ticket ID will cause the update to fail.
    • Providing invalid field values (e.g., non-existent agent or team IDs) may result in API errors.
    • Network connectivity problems can prevent successful API calls.
    • Insufficient permissions on the API key can lead to authorization errors.

  • Error messages:

    • "Ticket not found" indicates the specified Ticket ID does not exist.
    • "Unauthorized" or "Forbidden" suggests issues with API credentials or permissions.
    • Validation errors will specify which fields have invalid values; ensure all IDs and data types match expected formats.

  • Resolutions:

    • Verify the Ticket ID exists before attempting update.
    • Confirm all referenced IDs (agent, team, status, priority) are valid and available.
    • Check API credentials and permissions.
    • Ensure network access to the HaloPSA API endpoint.

Links and References

Discussion