HaloPSA Complete icon

HaloPSA Complete

Get data from the HaloPSA API

Actions68

Overview

This node updates an existing Timesheet Event in the HaloPSA system. It is useful for scenarios where you need to modify details of a previously recorded timesheet event, such as changing the start or end time, updating the subject or note, associating it with a different ticket, or adjusting the time taken.

Practical examples include:

  • Correcting the time logged on a timesheet event after discovering an error.
  • Adding additional notes or changing the subject to better describe the work done.
  • Linking the timesheet event to a different support ticket if it was initially assigned incorrectly.
  • Updating the event type or agent responsible for the event.

Properties

Name Meaning
Timesheet Event ID The unique identifier of the timesheet event to update (required).
Update Fields A collection of fields to update on the timesheet event. Options include:
- Agent ID Numeric ID of the agent associated with the timesheet event.
- End Date The end date and time of the event (dateTime format).
- Event Type Numeric code representing the type of the event.
- Note Text note providing additional information about the event.
- Start Date The start date and time of the event (dateTime format).
- Subject Subject or title describing the timesheet event.
- Ticket ID Numeric ID of the ticket associated with the event.
- Time Taken Numeric value representing the time taken for the event (e.g., duration in minutes).

Output

The node outputs JSON data representing the updated timesheet event object as returned by the HaloPSA API. This typically includes all the properties of the timesheet event after the update, such as IDs, dates, notes, and any other relevant metadata.

If the node supports binary data output, it would be related to attachments or files linked to the timesheet event, but based on the provided code and properties, this node primarily deals with JSON data.

Dependencies

  • Requires an active connection to the HaloPSA API using an API key or token configured in n8n credentials.
  • The node depends on the HaloPSA API endpoint for timesheet events to perform update operations.
  • Proper permissions on the API key are necessary to update timesheet events.

Troubleshooting

  • Invalid Timesheet Event ID: If the provided ID does not exist or is incorrect, the API will likely return an error indicating the resource was not found. Verify the ID before running the node.
  • Insufficient Permissions: Errors related to authorization may occur if the API key lacks update permissions. Ensure the API key has adequate rights.
  • Invalid Field Values: Providing invalid data types (e.g., text instead of number) or malformed dates can cause errors. Validate input formats carefully.
  • Empty Update Fields: If no fields are specified to update, the node might either do nothing or throw an error. Always specify at least one field to update.
  • API Connectivity Issues: Network problems or incorrect API URLs can cause failures. Check connectivity and credential configuration.

Links and References

Discussion