Pulse Recruitment icon

Pulse Recruitment

Recruitment actions from Pulse API

Actions11

Overview

The node provides integration with a recruitment system via the Pulse API, focusing on managing candidate data. Specifically, the "Update Candidate" operation allows users to modify existing candidate records by specifying their unique ID and updating personal details such as names, organizational unit, and picture URL.

This node is beneficial in scenarios where recruitment workflows require automated updates to candidate profiles, for example:

  • Synchronizing candidate information from external HR systems.
  • Correcting or enriching candidate data after initial entry.
  • Automating bulk updates to candidate records based on new inputs or changes in organizational structure.

Practical example: Automatically update a candidate's last name and organizational unit after receiving updated information from an onboarding form submission.

Properties

Name Meaning
Candidate ID * The unique identifier of the candidate to update.
First Name * The candidate's first name.
Middle Name The candidate's middle name (optional).
Last Name * The candidate's last name.
Organizational Unit * The organizational unit or department the candidate belongs to.
Picture URL A URL pointing to the candidate's picture (optional).

(* indicates required fields)

Output

The output contains a JSON object representing the updated candidate record as returned by the Pulse API. This typically includes all candidate details after the update has been applied, reflecting the current state of the candidate profile.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Pulse API service.
  • An API authentication token or key credential must be configured in n8n to authorize requests.
  • The node depends on internal helper functions to interact with the Pulse API endpoints.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Candidate ID will result in errors indicating the candidate could not be found.
    • Missing required fields (Candidate ID, First Name, Last Name, Organizational Unit) will cause validation errors before the request is sent.
    • Network or authentication failures may prevent successful API calls.

  • Error messages:

    • "The operation "updateCandidate" is not supported for resource "candidates"!" — indicates a misconfiguration of the operation or resource parameters.
    • Errors returned from the Pulse API will be passed through; these often include messages about invalid input or permission issues.

  • Resolution tips:

    • Verify that the Candidate ID exists in the Pulse system.
    • Ensure all required fields are provided and correctly formatted.
    • Confirm that the API credentials are valid and have sufficient permissions.
    • Use the node's "Continue On Fail" option to handle errors gracefully during batch processing.

Links and References

Discussion