Pulse Talent icon

Pulse Talent

Talent resource from Pulse API

Actions24

Overview

This node interacts with the "Experience" resource of the Pulse API, specifically supporting the operation to retrieve a list of experiences. It is designed to fetch experience records related to talents, such as job history or project involvement, from the Pulse platform.

Common scenarios where this node is beneficial include:

  • Aggregating experience data for talent profiles in HR or recruitment workflows.
  • Displaying or analyzing work history details within automated pipelines.
  • Integrating experience information into broader talent management systems.

For example, you might use this node to get a paginated list of experiences filtered by organization or sorted by relevance, optionally including related talent details.

Properties

Name Meaning
Include Related Resources Select related resources to include in the response. Currently supports: Talent. Including related resources enriches the experience data with associated talent information.
Additional Fields 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: One or more filters defined by key and comma-separated values (e.g., filter by organization_id with values 1,2,3).
• Fields: Specify field groups and comma-separated field names to limit returned fields.

Output

The node outputs JSON data representing the list of experience records retrieved from the Pulse API. The structure typically includes an array of experience objects, each containing details such as position, organization, dates, and possibly related talent information if requested.

If related resources are included, the output JSON will embed those linked entities accordingly.

No binary data output is produced by this node.

Dependencies

  • Requires connection to the Pulse API via an API key credential configured in n8n.
  • The node depends on the Pulse API helper utilities bundled with the node implementation.
  • Proper network access to the Pulse API endpoint is necessary.

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 without proper values can lead to unexpected results or errors.

  • Error Messages:

    • "The operation "getExperienceList" is not supported for resource "experience"!": Indicates a mismatch in operation-resource selection; ensure correct operation is chosen.
    • "The resource "experience" is not supported!": Suggests an unsupported resource was specified; verify resource name.
    • Network or authentication errors from the Pulse API should be checked by validating credentials and connectivity.

To resolve issues, verify API credentials, confirm property values, and consult Pulse API documentation for valid filter keys and parameters.

Links and References

Discussion