HCSS Heavy Job icon

HCSS Heavy Job

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

Actions7

Overview

The node interacts with the HCSS Heavy Job API to retrieve job-related data. Specifically, for the "Job" resource and "Jobs" operation, it fetches a list of jobs filtered by business unit and status. This is useful in scenarios where you need to integrate job management data from HCSS into workflows, such as monitoring active projects, reporting on completed jobs, or syncing job statuses with other systems.

Practical examples:

  • Automatically retrieving all active jobs for a specific business unit to generate daily progress reports.
  • Fetching completed jobs to trigger invoicing or archival processes.
  • Filtering jobs by status to update dashboards or notify stakeholders about project phases.

Properties

Name Meaning
Business Unit Code Name or ID Select or specify the business unit to filter jobs by. This can be chosen from a dynamic list or set via an expression.
Status Filter jobs by their status. Options include: Active, All, Completed, Discontinued, In Active, Undefined.

Output

The node outputs a JSON array where each item represents a job matching the specified business unit and status filters. The structure corresponds to the job objects returned by the HCSS Heavy Job API's /jobs endpoint.

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 available at https://api.hcssapps.com.
  • The "Business Unit Code Name or ID" property dynamically loads options by calling the API to list business units.
  • Proper network access and valid credentials are necessary for successful API communication.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect or empty business unit IDs may result in no jobs being returned.
    • Network connectivity problems can prevent API calls from succeeding.

  • Error messages:

    • Authentication errors typically indicate invalid client ID, secret, or scope; verify these credentials.
    • If the node returns an error related to the business unit, ensure the selected business unit exists and is accessible.
    • Timeout or request failures suggest checking network settings or API availability.

  • Resolution tips:

    • Test credentials using the node’s built-in credential test feature before running workflows.
    • Use the dynamic dropdown to select valid business units rather than manually entering IDs.
    • Review API limits or permissions if requests are rejected.

Links and References

Discussion