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 those campaigns. The "Reject Candidate" operation lets users mark a candidate as rejected for a specific recruitment campaign position. This is useful in HR automation workflows where candidates need to be programmatically moved through different stages of recruitment, including rejection.

Practical examples:

  • Automatically reject candidates who do not meet certain criteria after initial screening.
  • Integrate with other systems to update candidate status based on external assessments.
  • Batch process multiple candidates' statuses in recruitment pipelines.

Properties

Name Meaning
Recruitment Campaign ID * The unique identifier of the recruitment campaign position where the candidate is involved.
Candidate ID * The unique identifier of the candidate to be rejected in the specified recruitment campaign.

Output

The node outputs a JSON object representing the result of the reject candidate action. This typically includes confirmation details such as updated candidate status or identifiers confirming the rejection was processed successfully.

No binary data output is produced by 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 API calls.
  • Proper permissions and valid IDs for recruitment campaigns and candidates are necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or missing Recruitment Campaign ID or Candidate ID will cause errors.
    • Insufficient permissions or expired API credentials can lead to authentication failures.
    • Attempting to reject a candidate who is not part of the specified recruitment campaign may result in errors.

  • Error messages:

    • "The operation "rejectCandidate" is not supported for resource "recruitmentCampaign"!" — indicates a misconfiguration or unsupported operation; ensure correct resource and operation selection.
    • API errors returned from Pulse (e.g., 404 Not Found) usually mean the provided IDs are incorrect or the candidate does not exist in the campaign.

  • Resolution tips:

    • Double-check that the Recruitment Campaign ID and Candidate ID are correct and correspond to existing entities.
    • Verify API credentials and their permissions.
    • Use the node's error output (if continue on fail is enabled) to debug issues without stopping workflow execution.

Links and References

Discussion