Pulse Talent icon

Pulse Talent

Talent resource from Pulse API

Actions32

Overview

This node interacts with the "Skill" resource of the Pulse API, specifically supporting the operation to retrieve a list of skills ("Get Skills List"). It is designed to fetch and return skill data from the Pulse platform, which can be useful in scenarios such as talent management, HR analytics, or integrating skill data into other workflows.

Practical examples include:

  • Retrieving a paginated list of skills for display in an internal dashboard.
  • Filtering skills based on specific criteria like organization or relevance.
  • Including related resources (e.g., associated talents) to enrich the skill data context.

Properties

Name Meaning
Include Related Resources Select related resources to include in the response. Options: Talent
Additional Fields Collection of optional parameters to customize the request:
- Sort Sort order of results, e.g., "-relevance"
- Page Number Pagination page number (requires page size)
- Page Size Number of items per page
- Filters One or more filters to narrow down results. Each filter has:
• Filter Key (e.g., "organization_id")
• Values (comma-separated values, e.g., "1,2,3")
- Fields Specify fields to include in the response. Each field group has:
• Field Key (e.g., "iam/organizations/people_directories")
• Fields (comma-separated field names, e.g., "id,name")

Output

The node outputs JSON data containing the list of skills retrieved from the Pulse API. The structure typically includes skill details such as IDs, names, descriptions, and any additional fields requested via the input properties.

If related resources are included (e.g., Talent), those will be nested within the output JSON accordingly.

No binary data output is indicated by the source code.

Dependencies

  • Requires an API key credential for authenticating with the Pulse API.
  • The node depends on the Pulse API helper utilities bundled in the package to perform API calls.
  • Proper configuration of the API credential in n8n is necessary for successful execution.

Troubleshooting

  • Common Issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Incorrect 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.

  • Error Messages:

    • "The operation "getSkillsList" is not supported for resource "skill"!" — This indicates a mismatch between selected resource and operation; ensure correct selections.
    • API errors returned from Pulse (e.g., rate limits, invalid parameters) will be propagated; check the error message for details.

  • Resolution Tips:

    • Verify API credentials and permissions.
    • Double-check filter keys and values against Pulse API documentation.
    • Use pagination parameters consistently.
    • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion