Pulse People icon

Pulse People

People resource from Pulse API

Actions8

Overview

The "People" resource with the "Create Person" operation allows users to add a new person record into the Pulse system via its API. This node is useful in scenarios where you want to automate the creation of people profiles, such as onboarding new employees, registering clients, or managing contacts within an organization.

Practical examples include:

  • Automatically creating a person profile when a new user signs up on a platform.
  • Syncing employee data from an HR system into Pulse.
  • Adding customer contact details collected from a web form into the Pulse database.

Properties

Name Meaning
First Name * The first name of the person to create (required).
Middle Name The middle name of the person to create (optional).
Last Name * The last name of the person to create (required).
Gender The gender of the person to create. Options: Male, Female.
Birthday The birthday of the person to create (date and time).
Relationship Status The relationship status of the person to create. Options: Single, Married.
Number of Kids The number of kids the person has (minimum value 0).
Secondary Email A secondary email address for the person (optional).
Phone Number The phone number of the person to create (optional).
Address The address of the person to create (optional).
Organizational Unit * The organizational unit the person belongs to (required).

Output

The node outputs a JSON object representing the newly created person record as returned by the Pulse API. This typically includes all the fields sent during creation along with any additional metadata or unique identifiers assigned by the system.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Pulse API using an API key or token configured in n8n credentials.
  • The node depends on the Pulse API helper utilities bundled with the node implementation to handle API requests.
  • Proper network access to the Pulse API endpoint is necessary.

Troubleshooting

  • Missing Required Fields: If required properties like "First Name", "Last Name", or "Organizational Unit" are not provided, the API will likely return an error. Ensure these fields are filled.
  • Invalid Field Values: Providing invalid values (e.g., negative numbers for "Number of Kids") may cause validation errors.
  • Authentication Errors: If the API key credential is missing or invalid, authentication will fail. Verify that the API key is correctly set up in n8n.
  • API Connectivity Issues: Network problems or incorrect API URLs can cause request failures. Check connectivity and configuration.
  • Error Handling: If the node is set to continue on failure, errors will be included in the output JSON under an error field; otherwise, execution will stop on the first error.

Links and References

Discussion