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 entry. It is designed for scenarios where users need to log or track work hours, breaks, and other time-related data for agents within an organization. Typical use cases include workforce management, attendance tracking, and payroll preparation.

For example, a manager could use this node to record the start and end times of an agent's workday, specify actual hours worked versus target hours, and add metadata such as color coding or assign a timesheet manager. This helps automate timesheet creation and ensures accurate time tracking in business processes.

Properties

Name Meaning
Agent ID The unique identifier of the agent for whom the timesheet is being created.
Date The specific date for the timesheet entry.
Additional Fields A collection of optional fields to provide more detailed timesheet information:
- Actual Hours Number of actual hours worked by the agent.
- Agent Name Name of the agent associated with the timesheet.
- Break Hours Number of break hours taken during the work period.
- Colour Color code assigned to the timesheet for categorization or visual identification.
- End Time Timestamp marking the end of the work period.
- Start Time Timestamp marking the start of the work period.
- Target Hours Number of target hours expected to be worked.
- Timesheet Manager Identifier of the manager responsible for the timesheet.
- Work Hours Total number of work hours logged.
- Workday ID Identifier linking the timesheet to a specific workday record.

Output

The node outputs JSON data representing the newly created timesheet record as returned by the HaloPSA API. This typically includes all submitted fields along with any additional metadata or identifiers assigned by the system upon creation.

If binary data were involved (not indicated here), it would represent file attachments or related documents, but this node focuses on JSON structured timesheet data only.

Dependencies

  • Requires an active connection to the HaloPSA API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The node relies on internal routing logic (router) to handle API calls, abstracting direct HTTP request details.

Troubleshooting

  • Common Issues:

    • Invalid or missing Agent ID can cause the API to reject the timesheet creation.
    • Incorrect date or datetime formats may lead to errors or unexpected results.
    • Missing required API credentials will prevent successful communication with HaloPSA.

  • Error Messages:

    • Authentication errors indicate issues with the provided API key/token; verify credential setup.
    • Validation errors from the API often point to missing mandatory fields or invalid field values; ensure all required properties are correctly set.
    • Network or timeout errors suggest connectivity problems; check network access and API availability.

Links and References

Discussion