HCSS Heavy Job icon

HCSS Heavy Job

Read, update, write and delete data from HCSS Heavy Job API
Join our community

Actions7

Overview

This node integrates with the HCSS Heavy Job API to retrieve employee attendance hour tags for a specified business unit. It is useful in scenarios where you need to programmatically access detailed hour tag data related to employee attendance within a particular business unit, such as for payroll processing, attendance tracking, or labor cost analysis.

For example, a construction company could use this node to automatically fetch and analyze attendance hour tags for employees across different business units to streamline reporting and ensure accurate labor billing.

Properties

Name Meaning
Business Unit ID The unique identifier of the business unit for which to retrieve employee attendance hour tags. This is required to specify the scope of the query.

Output

The node outputs a JSON array containing the employee attendance hour tags associated with the specified business unit. Each item in the output array represents an hour tag record retrieved from the HCSS Heavy Job 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 depends on the external HCSS Heavy Job API service endpoint: https://api.hcssapps.com.
  • Proper configuration of the API credentials (client ID, client secret, and scope) is necessary for successful authentication and data retrieval.

Troubleshooting

  • Missing or invalid Business Unit ID: Ensure that the "Business Unit ID" property is correctly set and corresponds to a valid business unit in the HCSS system.
  • Authentication errors: If the node fails to authenticate, verify that the API credentials are correctly configured and have the necessary permissions.
  • API request failures: Network issues or incorrect API endpoints can cause errors. Check connectivity and confirm that the API URL has not changed.
  • Empty results: If no hour tags are returned, confirm that the specified business unit actually has attendance hour tags recorded.

Common error messages may include:

  • "Connection details not valid: missing credentials" — indicates incomplete API credential setup.
  • "Authentication failed: No access token received" — suggests invalid client ID, secret, or scope.
  • API response errors with HTTP status codes — check the API documentation and credentials.

Links and References

Discussion