Actions20
- Candidates Actions
- Pipeline Templates Actions
- Stage Templates Actions
- Recruitment Campaigns Actions
Overview
This node enables managing recruitment campaigns and candidates through the Pulse API. Specifically, the "Hire Candidate" operation allows you to mark a candidate as hired within a specified recruitment campaign. This is useful in HR automation workflows where you want to update candidate statuses programmatically after interviews or assessments.
Practical examples include:
- Automatically hiring a candidate once all interview stages are completed successfully.
- Integrating with other systems to update candidate status when an offer is accepted.
- Streamlining recruitment pipelines by automating candidate status changes.
Properties
| Name | Meaning |
|---|---|
| Recruitment Campaign ID * | The unique identifier of the recruitment campaign position where the candidate is hired. |
| Candidate ID * | The unique identifier of the candidate to be marked as hired. |
Output
The node outputs a JSON object representing the result of the hire candidate action. This typically includes confirmation details such as updated candidate status and related metadata returned from the Pulse API.
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 service being available and accessible.
- Proper permissions for modifying recruitment campaigns and candidate statuses are necessary.
Troubleshooting
Common issues:
- Invalid or missing Recruitment Campaign ID or Candidate ID will cause errors.
- Insufficient API permissions may lead to authorization failures.
- Network connectivity problems can prevent successful API calls.
Error messages and resolutions:
"The operation "hireCandidate" is not supported for resource "recruitmentCampaign"!"
Ensure that the operation name and resource are correctly set.- API error messages indicating invalid IDs usually mean the provided IDs do not exist or are mistyped.
- Authentication errors suggest checking the API key credential configuration.
Links and References
- Pulse API Documentation (replace with actual URL)
- n8n documentation on creating custom nodes