Pulse Talent icon

Pulse Talent

Talent resource from Pulse API

Actions32

Overview

The "Pulse Talent" node interacts with the Pulse API to manage and retrieve talent-related data. Specifically, the Get Talent List operation fetches a list of talent profiles from the Pulse system. This is useful for HR teams, recruiters, or talent acquisition specialists who want to programmatically access and filter talent information stored in Pulse.

Common scenarios include:

  • Retrieving paginated lists of candidates or employees.
  • Filtering talent by specific criteria such as organization ID or skills.
  • Sorting talent results by relevance or other fields.
  • Selecting specific fields to optimize data retrieval.

For example, a recruiter could use this node to get a sorted list of candidates filtered by department and only retrieve their names and contact details.

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 descending by relevance.
- Page Number The page number for pagination (requires Page Size).
- Page Size Number of items per page for pagination.
- Filters One or more filters to narrow down the talent list. Each filter has:
• Filter Key: The field to filter by (e.g., organization_id).
• Values: Comma-separated values to match 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 category or path of fields (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 retrieved talent list data from the Pulse API. The structure typically includes an array of talent records, each with properties depending on the requested fields and filters.

Example output structure (simplified):

{
  "talents": [
    {
      "id": "123",
      "name": "John Doe",
      "email": "john.doe@example.com",
      ...
    },
    {
      "id": "456",
      "name": "Jane Smith",
      "email": "jane.smith@example.com",
      ...
    }
  ],
  "pagination": {
    "pageNumber": 1,
    "pageSize": 10,
    "totalPages": 5,
    "totalItems": 50
  }
}

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Pulse API.
  • The node depends on the Pulse API helper utilities bundled within the node's codebase.
  • Proper configuration of the API credential in n8n is necessary for successful requests.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Invalid filter keys or values may result in empty responses or errors.
    • Pagination parameters must be used correctly; specifying a page number without a page size might not work as expected.
    • Requesting unsupported fields or malformed field groups can cause errors.

  • Error messages:

    • "The operation "getTalentList" is not supported for resource "talent"!" — indicates a mismatch between selected operation and resource.
    • "The resource "X" is not supported!" — means the resource name is invalid or not implemented.
    • API errors returned from Pulse will be passed through; check the error message for details like rate limits or invalid parameters.

  • Resolutions:

    • Verify API credentials and permissions.
    • Double-check filter keys and field names against Pulse API documentation.
    • Use valid pagination parameters together.
    • Ensure the resource and operation selections are correct in the node configuration.

Links and References

Discussion