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 manage employee records within a business unit. Specifically, the Employee - Create operation allows users to add new employees by providing essential details such as an employee code and associated business unit. This is useful in scenarios where organizations need to automate employee data entry into their HCSS system, for example, when onboarding new staff or synchronizing HR systems.

Practical examples include:

  • Automatically creating employee profiles when new hires are added in an HR platform.
  • Bulk importing employee data from external sources into HCSS Heavy Job.
  • Integrating employee creation into workflows that trigger after contract signing or background checks.

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.
- 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 a JSON array 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 upon creation.

No binary data output is involved in 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 REST API endpoint https://api.hcssapps.com.
  • The "Business Unit Code Name or ID" property dynamically loads options via an API call to fetch available business units.
  • Proper configuration of credentials and network access to the HCSS API is necessary.

Troubleshooting

  • Missing Required Fields: If "Code" or "Business Unit Code Name or ID" is not provided, the API will reject the request. Ensure these required fields are set.
  • Authentication Errors: Failure to authenticate usually results from invalid or missing API credentials. Verify the API key and secret are correctly configured.
  • Invalid Business Unit: Selecting or specifying a non-existent business unit code may cause errors. Use the dynamic dropdown or valid expressions to ensure correctness.
  • API Rate Limits or Network Issues: Temporary failures might occur due to network problems or API throttling. Retrying or checking connectivity can help.
  • Unexpected API Response: If the API returns an error message, review the error details and confirm that all field values conform to expected formats and constraints.

Links and References

Discussion