Pulse Recruitment icon

Pulse Recruitment

Recruitment actions from Pulse API

Actions20

Overview

The node enables managing recruitment campaigns via the Pulse API, specifically allowing actions on candidates within these campaigns. The "Move Candidate" operation moves a candidate from their current stage in a recruitment campaign pipeline to a new specified stage. This is useful for automating candidate progression through different stages of hiring workflows, such as moving a candidate from "Interview" to "Offer" or "Rejected".

Practical examples include:

  • Automatically advancing candidates after completing an interview.
  • Moving candidates back to earlier stages if additional review is needed.
  • Integrating with other systems to update candidate status based on external triggers.

Properties

Name Meaning
Recruitment Campaign ID * The unique identifier of the recruitment campaign position where the candidate is located.
Candidate ID * The unique identifier of the candidate to be moved within the recruitment campaign.
New Stage ID * The unique identifier of the target stage to which the candidate will be moved.

Output

The node outputs a JSON object representing the result of the move candidate operation. This typically includes confirmation details about the candidate's updated status and stage within the recruitment campaign. The exact structure depends on the Pulse API response but generally contains identifiers and status fields confirming the successful move.

No binary data output is involved in 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 with the node implementation to perform authenticated requests.
  • Proper permissions on the Pulse API are necessary to modify candidate stages within recruitment campaigns.

Troubleshooting

  • Common issues:

    • Invalid or missing Recruitment Campaign ID, Candidate ID, or Stage ID can cause errors.
    • Insufficient API permissions may prevent updating candidate stages.
    • Network or authentication failures with the Pulse API.

  • Error messages:

    • "The operation "moveCandidate" is not supported for resource "recruitmentCampaign"!" indicates a misconfiguration or unsupported operation selection.
    • Errors containing "error" in the output JSON indicate API call failures; check credentials and input IDs.

  • Resolutions:

    • Verify all required IDs are correct and exist in the Pulse system.
    • Ensure the API key credential has appropriate scopes/permissions.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully during batch operations.

Links and References

Discussion