Actions8
- People Actions
- Person Identity Document Actions
Overview
The "Pulse People" node allows users to manage person records within the Pulse API. Specifically, the "Update Person" operation updates an existing person's details by their unique ID. This is useful in scenarios where user or contact information needs to be kept current, such as updating employee records, customer profiles, or membership databases.
Practical examples include:
- Updating a person's contact information after they move or change phone numbers.
- Modifying personal details like relationship status or number of children for HR systems.
- Correcting or completing missing data fields in a CRM system.
Properties
| Name | Meaning |
|---|---|
| Person ID * | The unique identifier of the person to update (required). |
| First Name * | The person's first name (required). |
| Middle Name | The person's middle name (optional). |
| Last Name * | The person's last name (required). |
| Gender | The person's gender; options are "Male" or "Female". |
| Birthday | The person's date of birth (optional). |
| Relationship Status | The person's relationship status; options are "Single" or "Married". |
| Number of Kids | The number of children the person has; must be zero or more. |
| Secondary Email | An additional email address for the person (optional). |
| Phone Number | The person's phone number (optional). |
| Address | The person's physical address (optional). |
| Organizational Unit * | The organizational unit the person belongs to (required). |
(* 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 details after the update, such as their ID, names, contact info, and other attributes.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Pulse API.
- The node depends on the Pulse API service being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
Common issues:
- Missing required fields (Person ID, First Name, Last Name, Organizational Unit) will cause errors.
- Invalid Person ID (non-existent or malformed) will result in API errors.
- Network or authentication failures can prevent successful updates.
Error messages:
"The operation "updatePerson" is not supported for resource "people"!"— indicates a misconfiguration of operation or resource parameters.- API error messages related to invalid input or authorization failure should be checked and resolved by verifying credentials and input data.
Resolution tips:
- Ensure all required properties are provided and valid.
- Verify that the API key credential is correctly set up and has necessary permissions.
- Check network connectivity to the Pulse API endpoint.
Links and References
- Pulse API Documentation (replace with actual URL)
- n8n documentation on Creating Custom Nodes