Pulse Recruitment icon

Pulse Recruitment

Recruitment actions from Pulse API

Actions20

Overview

This node interacts with a recruitment system via the Pulse API, specifically focusing on managing candidates and other recruitment-related resources. The "Get Candidate" operation under the "Candidates" resource retrieves detailed information about a specific candidate by their unique ID.

Common scenarios for this node include:

  • Fetching candidate details to review their profile or status.
  • Integrating candidate data into workflows for further processing or decision-making.
  • Automating recruitment pipelines by pulling candidate information dynamically.

For example, a recruiter could use this node to automatically retrieve candidate profiles when a new application is received, enabling seamless integration with other HR tools or databases.

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 detailed information of the requested candidate. The structure typically includes all relevant candidate fields as provided by the Pulse API, such as personal details, application status, contact information, and any custom attributes defined in the recruitment system.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Pulse API, authenticated via an API key credential configured in n8n.
  • The node depends on the Pulse API helper utilities bundled within the node's codebase to perform API requests.
  • Proper network access to the Pulse API endpoint is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing Candidate ID: Ensure the Candidate ID is correctly specified and exists in the system.
    • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
    • Network connectivity problems: Confirm that the n8n instance can reach the Pulse API servers.

  • Error Messages:

    • "The operation "getCandidateById" is not supported for resource "candidates"!" — This indicates a misconfiguration; ensure the operation and resource names are correct.
    • Errors related to missing or invalid Candidate ID will typically mention the absence or invalidity of the ID parameter.
    • API response errors (e.g., 404 Not Found) suggest the candidate does not exist or the ID is incorrect.

To resolve these issues, double-check input parameters, credentials, and network settings.

Links and References

Discussion