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 business unit. Specifically, the Employee - Create operation allows users to add new employee records by specifying essential details such as employee code and associated business unit, along with optional additional information.

Common scenarios where this node is beneficial include:

  • Automating employee onboarding processes by programmatically creating employee profiles.
  • Integrating HR systems with HCSS Heavy Job for synchronized employee data management.
  • Bulk importing employee data from external sources into the HCSS system.

For example, a construction company could use this node in an n8n workflow to automatically create employee records when new hires are added in their HR platform, ensuring that project management and payroll systems stay up-to-date.

Properties

Name Meaning
Code Unique identifier code for the employee (required).
Business Unit Code Name or ID The business unit to which the employee belongs; selectable from a list or specified via expression (required).
Additional Fields Optional extra employee details including:
- Accounting Code Identifier used for accounting and financial reporting.
- Accounting Template Name Name of the accounting template for standardized financial processing.
- Address Primary street or mailing address.
- City City of the primary address.
- Company Name of the company or organization the employee belongs to.
- Cost Type Classification for budgeting and expense tracking.
- Crew Work crew or team assignment identifier.
- Default Equipment Primary equipment/tools assigned to the employee.
- Department Organizational department or business unit assignment.
- Division Company division or major business segment classification.
- Earn Code Payroll earning code categorizing compensation types.
- Email Employee's primary email address.
- First Name Employee's first or given name.
- General Ledger Account Account number for financial record keeping.
- Is Active Boolean indicating if the employee is currently active.
- Is Discontinued Boolean indicating if the employee has been terminated or discontinued.
- Is Foreman Boolean indicating if the employee holds a 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 phone number for direct contact.
- Pay Class Pay classification or grade level determining compensation structure.
- Phone Primary phone number for contact.
- Salary Annual salary amount or compensation rate.
- State State or province of the primary address.
- Supervisor Name or identifier of the employee's direct supervisor or manager.
- Tax Code Numeric tax classification code for payroll calculations.
- Type Employee type classification (e.g., full-time, part-time, contractor).
- Union Code Union membership code or identifier.

Output

The node outputs JSON data representing the newly created employee record as returned by the HCSS Heavy Job API. This typically includes all submitted fields along with any additional metadata or identifiers assigned by the API.

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 hcssApiRequest helper function to perform HTTP requests to the API endpoints.
  • The "Business Unit Code Name or ID" property dynamically loads options via the API, so network connectivity and valid credentials are necessary.
  • Proper configuration of the API authentication token or client credentials is required in n8n.

Troubleshooting

  • Missing Required Fields: If "Code" or "Business Unit Code Name or ID" are not provided, the API will reject the request. Ensure these mandatory fields are set.
  • Invalid Business Unit: Selecting or specifying an invalid business unit code or ID may cause errors. Use the dynamic dropdown or verify the value.
  • Authentication Errors: Failure to authenticate with the API will result in connection errors. Verify API credentials and permissions.
  • API Rate Limits or Downtime: Network issues or API limits can cause request failures. Implement retry logic or check API status.
  • Unexpected API Response: If the API returns an error message, review the error details in the node output and adjust input parameters accordingly.

Links and References

Discussion