Actions24
- Talent Actions
- Skill Actions
- Language Actions
- Education Actions
- Certification Actions
- Experience Actions
Overview
The "Create Talent" operation in the Pulse Talent node allows users to add new talent records into the Pulse system. This can be done either by uploading a resume file or by manually providing person details. It is useful for HR teams, recruiters, or talent acquisition specialists who want to automate adding candidates or employees into their talent management system.
Common scenarios include:
- Creating a talent profile directly from a candidate's resume URL, automatically associating it with an organizational unit.
- Adding a new person manually with detailed personal information if no resume is available.
- Associating an existing person (by ID) as a talent without creating a new person record.
Practical examples:
- Uploading a PDF resume URL to create a talent profile linked to the Marketing organizational unit.
- Creating a new person named John Doe with contact details and associating him as a talent in the Sales department.
- Linking an existing employee by their person ID to a talent record without additional personal data entry.
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 | The organizational unit to associate the talent with. Required when creating from a resume or when creating a new person manually. Default example: "MG". |
Resume URL | The URL pointing to the talent's resume file. Required if Upload Resume is true. |
Mime Type | The MIME type of the uploaded resume file, e.g., application/pdf . Required if Upload Resume is true. |
New Person | Boolean flag indicating whether to create a new person record when not uploading a resume. If false, an existing person ID must be provided. |
First Name | The first name of the person. Required if creating a new person. |
Middle Name | The middle name of the person. Optional when creating a new person. |
Last Name | The last name of the person. Required if creating a new person. |
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 kids the person has. Must be zero or more. 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 | The ID of an existing person to associate with this talent. Required if not uploading a resume and not creating a new person. |
Output
The output JSON contains the result of the talent creation operation. Typically, it includes the newly created talent's details such as unique identifiers, associated person information, and metadata returned by the Pulse API.
If the talent was created from a resume, the output reflects the parsed and stored talent data based on the resume content.
If created by person details, the output confirms the creation of the person and talent records.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to the Pulse API service via an API key credential configured in n8n.
- The node depends on the Pulse API helper utilities to perform authenticated requests.
- Network access to the resume URL is necessary if creating talent from a resume.
Troubleshooting
- Missing required fields: Ensure all mandatory properties are set according to the mode (resume upload vs. manual person creation). For example,
Resume URL
andMime Type
are required if uploading a resume;Person ID
is required if not creating a new person. - Invalid resume URL or inaccessible file: Verify that the resume URL is publicly accessible and points to a valid document matching the specified MIME type.
- API authentication errors: Confirm that the API key credential is correctly configured and has sufficient permissions.
- Unsupported operation or resource errors: These occur if the node configuration specifies unsupported combinations; verify that the Resource is "Talent" and Operation is "Create Talent".
- Continue on Fail behavior: If enabled, errors will be returned as part of the output JSON instead of stopping execution.
Links and References
- Pulse API Documentation (replace with actual URL)
- n8n Documentation - Creating Custom Nodes
- Resume Parsing Best Practices (replace with relevant resource)