Pulse Talent icon

Pulse Talent

Talent resource from Pulse API

Actions32

Overview

This node interacts with the "Talent" resource of the Pulse API, specifically allowing you to update talent acquisition details. It is designed to modify existing talent records by updating fields related to how a talent was acquired or their current status and availability.

Common scenarios where this node is beneficial include:

  • Updating the source or method through which a candidate applied.
  • Changing the status of a talent profile (e.g., marking as "to be tested" or "archived").
  • Recording when documents related to a talent were received.
  • Adjusting the availability status of a talent for new opportunities.

Practical example: After receiving a candidate's application via LinkedIn, you can use this node to update the talent record with the acquisition source as "LinkedIn", set the received date, and mark the talent as "available" for further processing.

Properties

Name Meaning
Talent ID * The unique identifier of the talent whose acquisition details you want to update.
Update Fields Collection of fields to update in the talent record:
- Received Date The date when the relevant document was received (date-time).
- Application Trigger The type or method that triggered the application (string).
- Application Source The origin/source of the talent profile. Options: Ingedata, LinkedIn, Spontanné, Cooptation, Ecole.
- Availability Current availability status of the talent. Options: Available, Not Available.
- Status Current status of the talent profile. Options: To be treated, To be tested, Black listed, Archived.

Output

The node outputs a JSON object representing the updated talent acquisition details after the operation completes successfully. This output typically includes the updated fields reflecting the changes made.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Pulse API via an API key credential configured in n8n.
  • The node depends on the Pulse API helper utilities bundled within the node's codebase to perform authenticated requests.
  • Proper permissions on the Pulse API are necessary to update talent records.

Troubleshooting

  • Common Issues:

    • Invalid or missing Talent ID will cause the update to fail.
    • Providing invalid values for enumerated fields like "Application Source", "Availability", or "Status" may result in errors.
    • Network or authentication issues with the Pulse API can prevent successful updates.

  • Error Messages:

    • "The operation "updateTalentAcquisition" is not supported for resource "talent"!" — indicates a misconfiguration of operation or resource parameters.
    • Errors returned from the Pulse API will be passed through; check the error message for details such as invalid IDs or permission issues.

  • Resolutions:

    • Ensure the Talent ID is correct and exists in the system.
    • Use only the allowed options for fields with predefined choices.
    • Verify API credentials and network connectivity.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully during batch operations.

Links and References

Discussion