Pulse Recruitment icon

Pulse Recruitment

Recruitment actions from Pulse API

Actions11

Overview

This node integrates with the Pulse API to perform recruitment-related actions, specifically managing candidates and quiz sessions. For the "Get Candidate" operation under the "Candidates" resource, it retrieves detailed information about a specific candidate by their unique ID. This is useful in HR workflows where you need to fetch candidate data for review, processing, or further automation.

Practical examples include:

  • Automatically fetching candidate details when a new application is received.
  • Integrating candidate data into other systems like CRMs or applicant tracking systems.
  • Triggering follow-up actions based on candidate status or profile information.

Properties

Name Meaning
Candidate ID * The unique identifier of the candidate whose details you want to retrieve. This is a required string input.

Output

The node outputs a JSON object containing the candidate's data as returned by the Pulse API. The structure typically includes all relevant candidate fields such as name, contact information, status, and any other metadata managed by the Pulse system.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the Pulse API.
  • The node depends on the Pulse API service being accessible and properly configured within n8n.
  • No additional external dependencies are indicated beyond the Pulse API integration.

Troubleshooting

  • Common issues:

    • Invalid or missing Candidate ID will cause the API call to fail.
    • Network or authentication errors if the API key is incorrect or expired.
    • Unsupported operations or resources will throw explicit errors.

  • Error messages:

    • "The operation "getCandidateById" is not supported for resource "candidates"!" indicates a misconfiguration of the operation or resource selection.
    • Errors from the Pulse API (e.g., 404 Not Found) usually mean the candidate ID does not exist.

  • Resolutions:

    • Ensure the Candidate ID is correctly provided and exists in the Pulse system.
    • Verify that the API credentials are valid and have necessary permissions.
    • Confirm that the selected resource and operation match the intended action.

Links and References

Discussion