Pulse Recruitment icon

Pulse Recruitment

Recruitment actions from Pulse API

Actions20

Overview

This node enables managing recruitment campaigns via the Pulse API, specifically allowing actions on candidates within those campaigns. The "Remove Candidate" operation lets you remove a candidate from a recruitment campaign. This is useful in scenarios where a candidate should no longer be considered for a particular campaign, such as when they withdraw their application or are disqualified.

Practical examples include:

  • Automatically removing candidates who fail to meet certain criteria after an initial screening.
  • Cleaning up recruitment campaigns by removing candidates who have accepted offers elsewhere.
  • Managing candidate lists dynamically based on external triggers or workflows.

Properties

Name Meaning
Candidate ID * The unique identifier of the candidate to be removed from the recruitment campaign.

Output

The node outputs JSON data representing the result of the removal operation. Typically, this will include confirmation details such as success status or any relevant metadata returned by the Pulse API about the candidate removal action.

No binary data output is involved in this operation.

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 permissions on the Pulse API side to modify recruitment campaigns and candidate data are necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Candidate ID: Ensure the Candidate ID provided exists and is correctly formatted.
    • Insufficient API permissions: Verify that the API key used has rights to modify recruitment campaigns.
    • Network or authentication errors: Check API credentials and network connectivity.

  • Error messages:

    • "The operation "removeCandidate" is not supported for resource "recruitmentCampaign"!" — This indicates a mismatch between selected resource and operation; ensure correct configuration.
    • Errors related to candidate not found or access denied typically come from the API and require verifying candidate existence and API permissions.

Links and References

Discussion