Pulse Talent icon

Pulse Talent

Talent resource from Pulse API
Join our community

Actions32

Overview

The "Pulse Talent" node allows users to interact with the Talent resource of the Pulse API. Specifically, the Query Talent operation enables searching for talents based on a user-defined query string. This is useful in scenarios such as talent acquisition, recruitment automation, or building talent pools by querying candidates that match certain criteria.

For example, a recruiter could use this node to search for talents with specific skills or experience by providing a natural language query or keywords. The node then returns matching talent profiles from the Pulse platform.

Properties

Name Meaning
Query * The query string used to search for talents. This is a required text input where you specify the search terms or criteria to find relevant talents.

Output

The node outputs an array of JSON objects representing the talents that match the query. Each object contains details about a talent profile as returned by the Pulse API. The exact structure depends on the API response but typically includes fields like talent ID, name, skills, experience, and other profile information.

No binary data output is produced by this operation.

Dependencies

  • Requires connection to the Pulse API via an API key credential.
  • The node depends on the Pulse API helper utilities bundled within the node's codebase to perform authenticated requests.
  • Proper configuration of the API authentication credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing an empty or malformed query string may result in no results or API errors.
    • Network connectivity problems can prevent the node from reaching the Pulse API.

  • Error messages:

    • "The operation "queryTalent" is not supported for resource "talent"!" — indicates a misconfiguration of the operation or resource parameters.
    • API error messages returned from Pulse (e.g., rate limits, invalid queries) will be surfaced in the node output if "Continue On Fail" is enabled.

  • Resolutions:

    • Ensure the API key credential is correctly set up and valid.
    • Verify the query string is meaningful and properly formatted.
    • Check network access and Pulse API status.

Links and References

Discussion