Pulse Talent icon

Pulse Talent

Talent resource from Pulse API
Join our community

Actions32

Overview

The node provides integration with a talent management API, specifically allowing operations on various talent-related resources. For the Experience resource and the Add Experience operation, it enables users to add a new professional experience entry associated with a specific talent. This is useful in scenarios such as building or updating a talent profile with detailed work history, tracking career progression, or managing HR records.

Practical examples include:

  • Adding a new job position for an employee in an HR system.
  • Recording freelance projects or contract roles for a talent database.
  • Updating a candidate's resume information automatically from external sources.

Properties

Name Meaning
Talent ID * The unique identifier of the talent to whom this experience entry will be linked.
Organization * The name of the organization where the experience was gained.
Position * The job title or position held during the experience period.
Start Date * The date when the experience started.
End Date The date when the experience ended; can be left empty if the experience is ongoing.
Summary A textual summary describing the experience, responsibilities, or achievements.

(* indicates required fields)

Output

The node outputs a JSON object representing the newly created experience entry. This typically includes all details provided (talent ID, organization, position, dates, summary) along with any additional metadata returned by the API, such as a unique experience ID or timestamps.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the Pulse API via an API key credential configured in n8n.
  • The node depends on the Pulse API helper utilities bundled within the node package to handle authentication and API requests.
  • Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Missing required properties (e.g., Talent ID, Organization, Position, Start Date) will cause errors.
    • Invalid or expired API credentials will result in authentication failures.
    • Incorrect date formats may lead to request rejections by the API.
    • Network connectivity problems can prevent communication with the Pulse API.

  • Error messages:

    • "The operation "createExperience" is not supported for resource "experience"!" — This indicates a misconfiguration or unsupported operation; verify the selected operation matches the node capabilities.
    • API error responses often include descriptive messages; ensure input data complies with API requirements.

  • Resolution tips:

    • Double-check all required fields are filled correctly.
    • Verify API credentials and renew if expired.
    • Use ISO 8601 format for date/time inputs.
    • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion