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 integrates with the HaloPSA API to retrieve timesheet data. Specifically, the "Get Many" operation under the "Timesheet" resource fetches multiple timesheet records based on user-defined filters and limits. This is useful for scenarios such as generating reports on work hours, auditing agent activities, or syncing timesheet data with other systems.
Practical examples include:
- Retrieving all timesheets for a specific agent within a date range.
- Fetching a limited number of recent timesheets for review.
- Filtering timesheets by exact dates to analyze daily productivity.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching timesheet records or limit the number of results returned. |
| Limit | Maximum number of timesheet records to return when "Return All" is false. |
| Filters | Criteria to filter the timesheets: |
| Agent ID | Filter timesheets by a specific agent's numeric ID. |
| Date | Filter timesheets by a specific date (string format). |
Output
The node outputs an array of JSON objects representing timesheet entries. Each object contains details about individual timesheets retrieved from the HaloPSA API. The exact structure depends on the API response but typically includes fields like agent information, date, hours worked, and related metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the HaloPSA API using an API key credential configured in n8n.
- The node relies on the HaloPSA API endpoints to fetch timesheet data.
- Proper network access and valid authentication credentials are necessary.
Troubleshooting
Common Issues:
- Authentication failures due to invalid or expired API keys.
- Network connectivity problems preventing API calls.
- Incorrect filter values leading to empty results.
- Exceeding API rate limits causing request rejections.
Error Messages:
- Unauthorized / 401: Check that the API key credential is correctly set up and has sufficient permissions.
- Timeouts or Network Errors: Verify internet connectivity and API endpoint availability.
- Invalid Parameter Errors: Ensure filter values like Agent ID and Date are correctly formatted and valid.
- Empty Results: Confirm that filters match existing timesheet data or try removing filters to broaden the query.
Links and References
- HaloPSA API Documentation (for detailed API usage and available fields)
- n8n Documentation on Creating Custom Nodes