Pulse Office Action icon

Pulse Office Action

Office actions from Pulse API

Actions17

Overview

The node provides integration with the Pulse API to manage employee data within an organization. Specifically, the "Update Employee" operation allows users to modify existing employee records by specifying the employee's ID and updating various attributes such as organizational unit, planning association, position, employment type, service number, hire date, and additional optional fields.

This node is beneficial in scenarios where HR or administrative workflows require automated updates to employee information, such as changing job positions, updating contact details, or managing employment status changes. For example, it can be used to update an employee’s department after a transfer, mark an employee as on hold during leave, or record termination dates.

Properties

Name Meaning
Employee ID * The unique identifier of the employee to update.
Organizational Unit * The organizational unit to which the employee belongs.
Planning ID * The ID of the planning entity associated with the employee.
Position * The job position/title of the employee.
Employment Type * The type of employment contract. Options: Full-time, Part-time, Freelance, Other.
Service Number * The official service number assigned to the employee.
Hired at * The date when the employee was hired.
Update Fields A collection of optional fields that can be updated for the employee:
- Manager IDs Comma-separated list of manager IDs linked to the employee.
- Teams Comma-separated list of team names the employee belongs to.
- Starting Date The employee’s starting date.
- Is Manager Boolean indicating if the employee holds a managerial role.
- Is HR Boolean indicating if the employee is part of HR.
- Terminated at The termination date of the employee, if applicable.
- On Hold Boolean indicating if the employee is currently on hold.
- Emergency Contact Name Name of the emergency contact person for the employee.
- Emergency Contact Phone Phone number of the emergency contact.
- Emergency Contact Relationship Relationship of the emergency contact to the employee.
- End of Probation Date Date marking the end of the employee’s probation period.
- Department The department the employee serves in. Options include HR, Training, Production, Operation, LAB, Compliance, IT/Dev, IT, Finance, Sales.
- Job Classification Grouping of the employee’s position. Options include Officer, Outsourcer, Agent, Project manager, Manager, Director, Team leader, Automation Architect, Production Assistant, Data Analyst, Cloud.
- Category Professional category/job level of the employee. Options: HC, 5B, 1B.
- Group Professional sublevel group of the employee. Options: I, II, III, IV, V.

(* indicates required fields)

Output

The node outputs a JSON object representing the updated employee record as returned by the Pulse API. This JSON typically includes all relevant employee details reflecting the changes made, such as updated position, employment type, contact information, and status flags.

No binary data output is produced by this operation.

Dependencies

  • Requires connection to the Pulse API via an API key credential configured in n8n.
  • The node depends on the Pulse API helper utilities bundled in the node package to perform authenticated requests.
  • Proper permissions on the Pulse API are necessary to update employee records.

Troubleshooting

  • Common Issues:

    • Invalid or missing Employee ID will cause the update to fail.
    • Providing invalid date formats for date fields may result in errors.
    • Insufficient API permissions or expired credentials will prevent successful updates.
    • Attempting to update unsupported fields or using incorrect option values may cause API rejections.

  • Error Messages:

    • "Unknown operation: "updateEmployee" is not supported for resource "employee"!" — Indicates a misconfiguration in the operation selection; ensure "Update Employee" is selected.
    • API error messages related to authentication failures suggest checking the API key credential setup.
    • Validation errors from the API about required fields indicate missing mandatory inputs like Employee ID or Organizational Unit.

To resolve issues, verify all required properties are correctly set, confirm API credentials are valid, and ensure the Pulse API endpoint is reachable.

Links and References

Discussion