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 manage employee data within a specified business unit. The Search Employee operation allows users to find employees by searching for a specific field (either "Code" or "Email") and matching it against a provided value within a selected business unit.

Typical use cases include:

  • Quickly locating an employee's record by their unique code or email address.
  • Automating workflows that require employee verification or retrieval of employee details based on identifiers.
  • Integrating employee search functionality into broader HR or project management automation pipelines.

For example, you might use this node to find an employee's information by entering their email address and the business unit they belong to, then use the returned data to update records or trigger notifications.

Properties

Name Meaning
Business Unit Code Name or ID Select the business unit from a dropdown list or specify its ID via expression. This scopes the search to a particular business unit.
Search Field Choose the field to search by: either "Code" (employee code) or "Email" (employee email address).
Search Value The exact value to search for in the selected search field.

Output

The output is a JSON array containing employee objects that match the search criteria within the specified business unit. Each object represents an employee record as returned by the HCSS Heavy Job API.

The structure of each employee object includes all standard employee fields available from the API, such as code, email, name, and other employee attributes.

No binary data is output 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 being accessible.
  • The "Business Unit Code Name or ID" property dynamically loads options by calling the API to retrieve available business units.
  • Proper configuration of the API credentials in n8n is necessary for successful requests.

Troubleshooting

  • Empty results: If no employees are returned, verify that the business unit code or ID is correct and that the search value exactly matches an existing employee's code or email.
  • Authentication errors: Ensure the API key credential is correctly configured and has valid permissions.
  • API request failures: Network issues or API downtime can cause errors; check connectivity and API status.
  • Invalid parameters: Make sure required fields ("Business Unit Code Name or ID", "Search Field", and "Search Value") are provided and correctly formatted.
  • Continue on Fail: If enabled, the node will return error messages per item instead of stopping execution.

Links and References

Discussion