HCSS Heavy Job icon

HCSS Heavy Job

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

Actions7

Overview

This node integrates with the HCSS Heavy Job API to retrieve various types of job-related data. Specifically, for the Hour Tag resource and the Get Cost Code Progress operation, it fetches detailed progress information about cost codes associated with a particular job within a specified date range.

This functionality is useful in construction or project management scenarios where tracking the financial progress of different cost codes (budget categories) on a job is critical. For example, a project manager can use this node to monitor how much budget has been spent versus planned for specific cost codes over time, helping to identify overruns or underutilized resources.

Practical examples:

  • Retrieve cost code progress for a job between two dates to generate financial reports.
  • Automate alerts when certain cost codes exceed budget thresholds.
  • Integrate cost code progress data into dashboards for real-time project monitoring.

Properties

Name Meaning
Job ID The unique identifier of the job for which cost code progress is requested.
Start Date The start date of the period for which cost code progress data should be retrieved.
End Date The end date of the period for which cost code progress data should be retrieved.

Output

The output JSON contains the results of the cost code progress query. It is an array of objects representing progress details for each relevant cost code within the specified job and date range.

Each object typically includes fields such as cost code identifiers, progress metrics, and possibly financial figures related to the cost code's usage and status.

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 makes HTTP requests to the HCSS API endpoints, specifically to /costCode/progress/advancedRequest with a POST method.
  • Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect Job ID or date formats may result in empty or error responses.
    • Network connectivity problems can prevent API calls from succeeding.

  • Error messages:

    • Authentication errors typically indicate invalid or expired credentials; verify and update your API key.
    • Validation errors may occur if required parameters like Job ID, Start Date, or End Date are missing or malformed.
    • API rate limits or server errors might return HTTP error codes; retry after some time or check API status.

Links and References

Discussion