Pulse Talent icon

Pulse Talent

Talent resource from Pulse API

Actions24

Overview

The node interacts with the Pulse API to manage and retrieve data related to Talent resources. Specifically, for the "Get Talent List" operation, it fetches a list of talent profiles from the Pulse system. This is useful in scenarios where you want to integrate talent data into workflows, such as HR automation, recruitment pipelines, or analytics dashboards.

Practical examples include:

  • Retrieving a paginated list of talents filtered by organization or skill.
  • Sorting talent profiles by relevance or other criteria.
  • Selecting specific fields to optimize data transfer and processing.

Properties

Name Meaning
Additional Fields A collection of optional parameters to customize the talent list retrieval:
- Sort Sort order of the results, e.g., -relevance to sort by descending relevance.
- Page Number The page number for pagination (requires specifying page size).
- Page Size Number of items per page for pagination.
- Filters One or more filters to narrow down the talent list. Each filter includes:
  Filter Key The key to filter by, e.g., organization_id.
  Values Comma-separated values for the filter key, e.g., 1,2,3.
- Fields Specify which fields to return grouped by field keys. Each group includes:
  Field Key The group key, e.g., iam/organizations/people_directories.
  Fields Comma-separated list of field names to include, e.g., id,name.

Output

The output is a JSON object containing the list of talent profiles retrieved from the Pulse API according to the specified parameters. The structure typically includes an array of talent objects with their respective properties as requested via the fields input.

If binary data were involved (not indicated here), it would be summarized accordingly, but this operation returns structured JSON data only.

Dependencies

  • Requires connection to the Pulse API service.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • Pagination and filtering depend on the Pulse API's support for these features.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Using unsupported filter keys or invalid field names may result in errors or empty responses.
    • Pagination parameters without proper values can lead to unexpected results or errors.

  • Error Messages:

    • "The operation "getTalentList" is not supported for resource "talent"!" — indicates a mismatch in operation-resource selection; ensure correct operation name.
    • "The resource "X" is not supported!" — means the resource name is invalid or not implemented.
    • API errors related to authorization or request format will be returned from the Pulse API and surfaced in the node output.

To resolve issues:

  • Verify API credentials are correctly set up.
  • Double-check property values for filters, fields, and pagination.
  • Consult Pulse API documentation for valid parameter values.

Links and References

Discussion