HCSS Heavy Job

Overview

This node integrates with the HCSS Heavy Job API to retrieve and manage data related to construction project management. Specifically, for the Hour Tag resource with the Employee Attendance Hour Tags operation, it fetches attendance hour tags associated with a specified business unit. This is useful for workflows that need to analyze or report on employee attendance hours categorized by tags within a business unit.

Common scenarios:

• Automating retrieval of employee attendance hour tags for payroll or reporting.
• Integrating attendance data into other HR or accounting systems.
• Monitoring labor hour allocations across different business units.

Example:
A construction company wants to automatically pull all attendance hour tags for a specific business unit daily to update their internal timesheet system.

Properties

Output

The node outputs a JSON array where each item represents an employee attendance hour tag associated with the specified business unit. Each object typically contains details about the hour tag such as its code, description, and any relevant metadata defined by the HCSS API.

No binary data output is produced by this operation.

Dependencies

• Requires an API key credential for authenticating with the HCSS Heavy Job API.
• The node uses the endpoint:
  GET /businessUnits/{businessUnitId}/attendanceHourTags
  to fetch the hour tags.
• The user must configure the API credentials in n8n prior to using this node.

Troubleshooting

• Missing or invalid Business Unit ID:
  If the Business Unit ID is not provided or incorrect, the API call will fail or return no data. Ensure the ID is valid and corresponds to an existing business unit.

• Authentication errors:
  Errors related to authentication usually indicate missing or invalid API credentials. Verify that the API key credential is correctly set up and has necessary permissions.

• API rate limits or connectivity issues:
  Network problems or hitting API rate limits can cause request failures. Check network connectivity and API usage quotas.

• Error messages from the node:

  • "Connection details not valid" indicates issues with the configured API credentials.
  • Other error messages returned from the API are passed through; review the message for clues (e.g., "Not Found" if the business unit does not exist).

Links and References

• HCSS Heavy Job API Documentation (general reference, exact URL may require login)
• n8n Expressions Documentation (for dynamic property values)

If you need details on other resources or operations, feel free to ask!