HaloPSA Complete icon

HaloPSA Complete

Get data from the HaloPSA API

Actions68

Overview

The "Timesheet Event - Get Many" operation in this node retrieves multiple timesheet event records from the HaloPSA API. It is useful for scenarios where you need to fetch a list of timesheet events, such as generating reports on work logged by agents, auditing time entries over a period, or syncing timesheet data with other systems.

Practical examples include:

  • Fetching all timesheet events for a specific agent within a date range.
  • Retrieving recent timesheet events up to a specified limit for dashboard display.
  • Filtering timesheet events by multiple agents or applying UTC offset adjustments for accurate time zone handling.

Properties

Name Meaning
Return All Whether to return all available results or limit the number of returned timesheet events.
Limit Maximum number of timesheet events to return when "Return All" is false.
Filters Collection of filters to narrow down the results:
  Agent ID Filter timesheet events by a single agent's numeric ID.
  Agents Filter by multiple agents using a comma-separated string of agent identifiers.
  End Date Filter timesheet events that end on or before this date (string format).
  Start Date Filter timesheet events that start on or after this date (string format).
  UTC Offset Numeric UTC offset to apply when filtering dates, useful for timezone adjustments.

Output

The node outputs an array of JSON objects representing timesheet events matching the query parameters. Each object typically contains details about individual timesheet events such as agent information, start and end timestamps, and related metadata.

If binary data were involved (not indicated here), it would be summarized accordingly, but this operation focuses on JSON data retrieval.

Dependencies

  • Requires an active connection to the HaloPSA API via an API key credential configured in n8n.
  • The node depends on the HaloPSA API endpoints for timesheet events.
  • Proper network access and valid authentication credentials are necessary.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Invalid date formats in filters may result in no data returned or errors.
    • Requesting too many records without enabling "Return All" might truncate results unexpectedly.
    • Network connectivity issues can prevent successful API calls.

  • Error Messages:

    • Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
    • Validation errors on filter fields suggest incorrect input formats; ensure dates are ISO strings and IDs are numbers.
    • Rate limiting or server errors from the API require retry logic or contacting HaloPSA support.

Links and References

Discussion