Pulse Talent icon

Pulse Talent

Talent resource from Pulse API

Actions32

Overview

This node interacts with the "Experience" resource of the Pulse API, specifically supporting the operation to retrieve a list of experience records. It is designed to fetch paginated and optionally filtered lists of experience entries related to talents or employees within an organization.

Common scenarios where this node is beneficial include:

  • Retrieving a list of work experiences for talents in a recruitment or HR workflow.
  • Fetching experience data to display or analyze employee career histories.
  • Integrating experience data into dashboards or reports by filtering and sorting based on various criteria.

For example, you could use this node to get the first 10 experience records sorted by relevance, including related talent information, or filter experiences by organization ID.

Properties

Name Meaning
Include Related Resources (included) Select related resources to include in the response. Currently supports: Talent. This allows fetching related talent details along with experience records.
Additional Fields (additionalFields) A collection of optional parameters to customize the query:
- Sort: Specify sort order (e.g., -relevance).
- Page Number: Pagination page number (requires page size).
- Page Size: Number of items per page.
- Filters: Apply filters by specifying key-value pairs (comma-separated values).
- Fields: Specify which fields to return for certain field groups (comma-separated field names).

Output

The node outputs JSON data containing the list of experience records retrieved from the Pulse API. The structure typically includes:

  • An array of experience objects, each representing a single experience entry with its properties such as job title, organization, dates, etc.
  • If related resources are included, nested objects with related talent information may be present.
  • Pagination metadata may also be included depending on the API response.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Pulse API.
  • The node depends on the Pulse API service being accessible and properly configured.
  • No additional environment variables are explicitly required beyond the API authentication setup.

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 may not work as expected.
    • Including unsupported related resources will be ignored or cause errors.

  • Error Messages:

    • "The operation "getExperienceList" is not supported for resource "experience"!" — indicates a mismatch in operation-resource selection; ensure correct operation is chosen.
    • Network or API errors will propagate with their messages; verify network connectivity and API status.
    • Validation errors on input parameters will be returned by the API; check that filters and fields are correctly formatted.

To resolve issues, verify API credentials, review property inputs, and consult API documentation for valid filter keys and field names.

Links and References

Discussion