HCSS Heavy Job icon

HCSS Heavy Job

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

Actions7

Overview

This node interacts with the HCSS Heavy Job API to manage employee data, specifically allowing you to update existing employee records. It is useful in scenarios where you need to keep employee information current within your workflow automation, such as updating contact details, job roles, or payroll classifications automatically based on external triggers or data sources.

For example, you could use this node to update an employee’s phone number and department after receiving updated HR data, ensuring your system always reflects the latest employee information without manual entry.

Properties

Name Meaning
Employee ID The unique identifier of the employee record to update (required).
Code A code representing the employee, required for identification during update.
Business Unit Code Name or ID Select or specify the business unit associated with the employee (required).
Additional Fields Optional collection of additional employee attributes that can be updated, including:
- Accounting Code Unique identifier used for accounting and financial reporting purposes.
- Accounting Template Name Name of the accounting template for standardized financial processing.
- Address Primary street or mailing address.
- City City name for the primary address location.
- Company Name of the company or organization the employee belongs to.
- Cost Type Classification of cost category for budgeting and expense tracking.
- Crew Work crew or team assignment identifier.
- Default Equipment Primary equipment or tools assigned by default.
- Department Organizational department or business unit assignment.
- Division Company division or major business segment classification.
- Earn Code Payroll earning code categorizing types of compensation.
- Email Primary email address for business communication.
- First Name Employee's first or given name.
- General Ledger Account General ledger account number for financial record keeping.
- Is Active Boolean indicating if the employee record is currently active.
- Is Discontinued Boolean indicating if the employee record has been discontinued or terminated.
- Is Foreman Boolean indicating if the employee holds a foreman or supervisory role.
- Is Salaried Boolean indicating if the employee is salaried versus hourly paid.
- Last Name Employee's last or family name.
- Mobile Phone Mobile or cell phone number for direct contact.
- Pay Class Pay classification or grade level determining compensation structure.
- Phone Primary phone number for business or personal contact.
- Salary Annual salary amount or compensation rate.
- State State or province for the primary address location.
- Supervisor Name or identifier of the employee's direct supervisor or manager.
- Tax Code Tax classification code used for payroll tax calculations and reporting.
- Type Employee type classification (e.g., full-time, part-time, contractor).
- Union Code Union membership code or identifier for collective bargaining purposes.

Output

The node outputs JSON data representing the updated employee record as returned by the HCSS Heavy Job API. This typically includes all fields of the employee object after the update operation, reflecting the new state of the employee data.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the HCSS Heavy Job API.
  • The node depends on the HCSS Heavy Job API being accessible and properly configured.
  • The "Business Unit Code Name or ID" property dynamically loads options from the API, so network connectivity and valid credentials are necessary for this feature.

Troubleshooting

  • Authentication errors: If the node fails due to authentication issues, verify that the API key credential is correctly configured and has the necessary permissions.
  • Invalid Employee ID: Errors may occur if the specified Employee ID does not exist; ensure the ID is correct.
  • Missing required fields: The node requires Employee ID, Code, and Business Unit Code to be provided; missing these will cause errors.
  • API connectivity issues: Network problems or API downtime can cause request failures; check connectivity and API status.
  • Invalid field values: Providing invalid or incorrectly formatted values in additional fields may result in API validation errors.

Links and References

Discussion