Pulse Talent icon

Pulse Talent

Talent resource from Pulse API

Actions32

Overview

The "Create Talent" operation in the Pulse Talent node allows users to add new talent profiles into the Pulse system. This can be done either by uploading a resume or by manually providing person details. It is useful for HR teams and recruiters who want to automate the process of adding candidates or employees into their talent management system.

Common scenarios include:

  • Creating a talent profile directly from a candidate's resume URL, which simplifies onboarding by extracting information automatically.
  • Adding a new person manually when no resume is available, with detailed personal and contact information.
  • Associating an existing person with a talent profile if they are already in the system.

Practical example:

  • A recruiter receives a candidate's resume hosted online and wants to quickly create a talent profile by providing the resume URL and organizational unit.
  • Alternatively, the recruiter may want to add a new person with full name, birthday, contact info, and other attributes without a resume.

Properties

Name Meaning
Upload Resume Boolean flag indicating whether to create the talent from a resume (true) or by specifying person details (false).
Organizational Unit * (fromResume=true) The organizational unit to associate with the talent when creating from a resume. Default is "MG".
Resume URL * The URL pointing to the talent's resume document. Required if creating from a resume.
Mime Type The MIME type of the uploaded resume file, e.g., "application/pdf". Required if creating from a resume.
New Person Boolean flag indicating if a new person should be created when not using a resume. If false, an existing person ID must be provided.
First Name * The first name of the person to create. Required if creating a new person manually.
Middle Name The middle name of the person to create. Optional.
Last Name * The last name of the person to create. Required if creating a new person manually.
Organizational Unit * (fromResume=false, newPerson=true) The organizational unit of the person being created manually. Default is "MG".
Picture URL URL of the person's picture. Optional when creating a new person.
Gender Gender of the person to create. Options: Male, Female. Default is Male.
Birthday Birthday of the person to create. Optional.
Relationship Status Relationship status of the person. Options: Single, Married. Default is Single.
Number of Kids Number of children the person has. Minimum 0. Default is 0.
Secondary Email Secondary email address of the person. Optional.
Phone Number Contact phone number of the person. Optional.
Address Address of the person. Optional.
Person ID * ID of an existing person to associate with this talent. Required if not creating from resume and not creating a new person.
Received Date * Date when the talent profile was received. Required. Defaults to a specific date/time if not set.
Application Trigger Recruitment campaign or trigger that initiated the hiring process. Optional.
Application Source Source of the talent profile. Options include: Ingedata, LinkedIn, Spontanné, Cooptation, Ecole, or empty. Optional.
Status Current status of the talent. Options: To be treated, To be tested, Black listed, Archived. Default is To be treated. Required.
Availability Current availability of the talent. Options: Available, Not Available. Default is Available. Required.

Output

The output JSON contains the newly created talent profile data as returned by the Pulse API. This typically includes identifiers, status, associated person details, and metadata about the talent record.

No binary data output is indicated for this operation.

Dependencies

  • Requires connection to the Pulse API service.
  • Requires an API authentication credential configured in n8n to authorize requests to the Pulse API.
  • The node depends on the PulseApiFactory helper to interact with the API.

Troubleshooting

  • Missing required fields: Errors will occur if mandatory fields like "Organizational Unit", "Resume URL" (when uploading resume), or "Person ID" (when associating existing person) are missing. Ensure all required inputs are provided.
  • Invalid URLs or MIME types: Providing an invalid resume URL or unsupported MIME type may cause upload failures.
  • API authentication errors: If the API key or token is invalid or missing, the node will fail to authenticate with the Pulse API.
  • Status or availability options: Using unsupported values for status or availability will result in errors; use only the predefined options.
  • Date format issues: The "Received Date" must be a valid ISO 8601 datetime string.

To resolve errors, verify input parameters, ensure credentials are correctly set up, and confirm network connectivity to the Pulse API endpoint.

Links and References

Discussion