Pulse Talent icon

Pulse Talent

Talent resource from Pulse API

Actions24

Overview

This node interacts with a talent management API to add professional experience entries for talents. Specifically, the "Add Experience" operation allows users to create a new experience record associated with a particular talent, detailing their work history such as organization, position, and dates of employment.

Common scenarios where this node is beneficial include:

  • Automating the enrichment of talent profiles in HR or recruitment systems.
  • Integrating external data sources to keep talent experience records up-to-date.
  • Building workflows that track career progression or validate candidate backgrounds.

For example, a recruiter could use this node to automatically add a new job experience entry when a candidate updates their resume on an external platform.

Properties

Name Meaning
Talent ID * The unique identifier of the talent to whom the experience entry will be linked.
Organization * The name of the organization where the talent gained the experience.
Position * The job title or position held by the talent during this experience.
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 brief description or summary of the experience.

(* indicates required fields)

Output

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

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Pulse API service.
  • The node depends on the Pulse API helper utilities bundled within the node's codebase to perform HTTP requests.
  • Proper configuration of the API credential 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.
    • Providing an invalid Talent ID that does not exist in the system may cause the API to reject the request.

  • Error messages:

    • "The operation "createExperience" is not supported for resource "experience"!" — indicates a misconfiguration of the operation or resource parameters.
    • API error responses related to validation or authorization will be passed through; ensure all required fields are correctly filled and credentials are valid.

  • Resolution tips:

    • Double-check all required input fields before running the node.
    • Verify that the API key credential is correctly set up and has sufficient permissions.
    • Confirm that the Talent ID exists in the target system.

Links and References

Discussion