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 job-related data for a specified business unit. Specifically, the "Jobs" operation under the "Job" resource fetches a list of jobs filtered by their status (e.g., active, completed) within a selected business unit.

Typical use cases include:

  • Fetching all jobs or filtering jobs by status for reporting or monitoring purposes.
  • Automating workflows that require up-to-date job information from HCSS systems.
  • Integrating job data into other business processes such as payroll, project management, or analytics.

For example, a construction company could use this node to automatically pull all active jobs for a particular business unit and feed that data into a dashboard or notification system.

Properties

Name Meaning
Business Unit Code Name or ID Select or specify the business unit by its code name or ID to filter jobs for that unit.
Status Filter jobs by their status. Options: Active, All, Completed, Discontinued, In Active, Undefined

Output

The node outputs an array of job objects in JSON format. Each object represents a job retrieved from the HCSS Heavy Job API and contains various job details as provided by the API response.

The output structure corresponds directly to the API's job data schema and can be used downstream in n8n workflows for further processing or integration.

No binary data is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the HCSS Heavy Job API.
  • The node uses the HCSS API endpoint https://api.hcssapps.com/jobs with query parameters for business unit ID and job status.
  • The business unit options are dynamically loaded via an API call to the HCSS Business Unit endpoint.

Troubleshooting

  • Missing or invalid credentials: The node requires valid API authentication credentials. If authentication fails, verify that the API key and secret are correctly configured.
  • Empty or incorrect business unit selection: Ensure the business unit ID or code is valid and exists in the HCSS system; otherwise, no jobs will be returned.
  • Invalid status filter: Use one of the predefined status options. An unsupported status value may result in no data or errors.
  • API request failures: Network issues or API downtime can cause errors. Check connectivity and API service status.
  • Error messages: Errors typically include messages from the API or network layer. Review the error message for clues and ensure all required parameters are set.

Links and References

Discussion