Pulse People icon

Pulse People

People resource from Pulse API

Actions8

Overview

The "Pulse People" node allows users to manage people records within the Pulse API system. Specifically, the Update Person operation updates an existing person's details by their unique ID. This is useful in scenarios where user or employee information changes and needs to be kept current, such as updating contact info, relationship status, or organizational unit.

Practical examples include:

  • Updating a person's phone number after they change it.
  • Modifying the number of kids or relationship status for HR records.
  • Correcting or adding missing middle names or secondary emails.

Properties

Name Meaning
Person ID * The unique identifier of the person to update.
First Name * The person's first name.
Middle Name The person's middle name (optional).
Last Name * The person's last name.
Gender The gender of the person. Options: Male, Female.
Birthday The person's date of birth.
Relationship Status The person's relationship status. Options: Single, Married.
Number of Kids The number of children the person has (minimum 0).
Secondary Email An additional email address for the person.
Phone Number The person's contact phone number.
Address The person's physical address.
Organizational Unit * The organizational unit the person belongs to (e.g., department or team).

(* indicates required fields)

Output

The node outputs a JSON object representing the updated person record as returned by the Pulse API. This typically includes all the person's properties after the update, such as IDs, names, contact details, and organizational data.

No binary data output is involved.

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 with the node implementation.
  • Proper permissions on the API key are necessary to perform update operations on people.

Troubleshooting

  • Common issues:

    • Missing required fields like Person ID, First Name, Last Name, or Organizational Unit will cause errors.
    • Invalid Person ID (non-existent) will result in API errors indicating the person was not found.
    • Insufficient API permissions can lead to authorization errors.
    • Incorrect data formats (e.g., invalid date for birthday) may cause validation failures.

  • Error messages:

    • "The operation "updatePerson" is not supported for resource "people"!" — indicates a misconfiguration of operation or resource parameters.
    • API error messages from Pulse API will be passed through; check the message for details.

  • Resolution tips:

    • Ensure all required fields are provided and correctly formatted.
    • Verify the Person ID exists before attempting an update.
    • Confirm API credentials have update permissions.
    • Use the "Continue On Fail" option to handle individual item errors gracefully.

Links and References

Discussion