Actions68
- Client Actions
- Agent Actions
- Asset Actions
- Field Info Actions
- Invoice Actions
- Site Actions
- Ticket Actions
- Ticket Status Actions
- Ticket Type Actions
- Timesheet Actions
- Timesheet Event Actions
- Webhook Actions
- Webhook Event Actions
Overview
The node provides integration with the HaloPSA API, specifically allowing users to update timesheet records. The "Timesheet Update" operation lets you modify various fields of an existing timesheet by specifying its ID and the fields to update.
This node is useful in scenarios where you need to programmatically adjust timesheet data, such as correcting hours worked, changing agent assignments, or updating time entries after manual review or external system synchronization.
Practical examples include:
- Automatically adjusting break hours or actual hours based on external attendance systems.
- Updating the assigned agent or manager for a timesheet entry.
- Changing start and end times to reflect corrected work periods.
Properties
| Name | Meaning |
|---|---|
| Timesheet ID | The unique identifier of the timesheet record you want to update. |
| Update Fields | A collection of fields that can be updated on the timesheet. Options include: |
| - Actual Hours: Number of actual hours worked. | |
| - Agent ID: Numeric ID of the agent associated with the timesheet. | |
| - Agent Name: Name of the agent. | |
| - Break Hours: Number of break hours taken. | |
| - Colour: Color code assigned to the timesheet (for UI or categorization). | |
| - Date: The date of the timesheet entry. | |
| - End Time: Timestamp marking the end of the work period. | |
| - Start Time: Timestamp marking the start of the work period. | |
| - Target Hours: Targeted number of hours for the timesheet. | |
| - Timesheet Manager: Numeric ID of the manager responsible for the timesheet. | |
| - Work Hours: Total work hours recorded. | |
| - Workday ID: Associated workday identifier. |
Output
The node outputs JSON data representing the updated timesheet object returned from the HaloPSA API after the update operation. This typically includes all the timesheet's properties reflecting the new state post-update.
If the node supports binary data output (not indicated here), it would represent any file attachments or related binary content linked to the timesheet, but this is not applicable based on the provided information.
Dependencies
- Requires connection to the HaloPSA API via an API key credential configured in n8n.
- The node depends on the HaloPSA API being accessible and the user having appropriate permissions to update timesheets.
- No additional external dependencies are indicated.
Troubleshooting
Common Issues:
- Invalid or missing Timesheet ID will cause the update to fail.
- Providing invalid field values (e.g., wrong data types or out-of-range numbers) may result in API errors.
- Network connectivity issues or incorrect API credentials will prevent successful updates.
Error Messages:
- "Timesheet not found": Verify the Timesheet ID is correct and exists.
- "Unauthorized" or "Authentication failed": Check that the API key credential is valid and has necessary permissions.
- "Invalid input": Review the fields in "Update Fields" for correct types and valid values.
Resolving these usually involves verifying input parameters, ensuring proper authentication setup, and confirming API availability.
Links and References
- HaloPSA API Documentation (general reference for API endpoints and data models)
- n8n Documentation on Creating Custom Nodes