HaloPSA Complete icon

HaloPSA Complete

Get data from the HaloPSA API

Actions68

Overview

This node integrates with the HaloPSA API to create a new Timesheet Event. It allows users to log time-related events associated with agents, tickets, and other relevant details within the HaloPSA system. This is useful for tracking work done by agents, managing time spent on tickets or projects, and maintaining detailed records of activities.

Practical examples include:

  • Logging a support agent’s work session on a specific ticket.
  • Recording time spent on internal tasks or meetings.
  • Adding notes and categorizing events by type for reporting purposes.

Properties

Name Meaning
Agent ID The unique identifier of the agent associated with the timesheet event (number).
Subject A brief description or title for the timesheet event (string).
Additional Fields Optional extra details about the event:
- End Date When the event ended (date and time).
- Event Type Numeric code representing the type/category of the event.
- Note Additional textual notes related to the event.
- Start Date When the event started (date and time).
- Ticket ID Identifier of the related ticket, if applicable (number).
- Time Taken Duration of the event in an appropriate unit (number).

Output

The node outputs JSON data representing the created timesheet event as returned by the HaloPSA API. This typically includes all submitted fields along with any additional metadata assigned by the API such as event IDs, timestamps, and status information.

If binary data were involved (not indicated here), it would represent file attachments or similar content related to the event.

Dependencies

  • Requires an active connection to the HaloPSA API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The node uses standard HTTP headers for JSON communication (Accept: application/json, Content-Type: application/json).

Troubleshooting

  • Common Issues:

    • Invalid or missing Agent ID or Ticket ID may cause the API to reject the request.
    • Incorrect date formats for start or end dates can lead to errors.
    • Lack of proper API credentials will result in authentication failures.

  • Error Messages:

    • Authentication errors indicate missing or invalid API tokens; verify credential setup.
    • Validation errors from the API often specify which field is incorrect or missing; check input values carefully.
    • Network or timeout errors suggest connectivity issues; ensure the API endpoint is reachable.

Links and References

Discussion