Pulse Recruitment icon

Pulse Recruitment

Recruitment actions from Pulse API

Actions20

Overview

This node integrates with the Pulse API to manage recruitment campaigns and related entities. Specifically, the Add Candidate operation under the Recruitment Campaigns resource allows you to add a talent (candidate) to a specific recruitment campaign position and assign them to a particular stage in the hiring pipeline.

Common scenarios where this node is beneficial include automating candidate management workflows such as:

  • Adding new candidates sourced from other systems into recruitment campaigns.
  • Automatically progressing candidates through stages based on external triggers.
  • Integrating recruitment data with other HR or CRM tools.

For example, when a new applicant submits their resume via a web form, this node can be used to add that applicant as a candidate to a defined recruitment campaign and place them at the initial screening stage automatically.

Properties

Name Meaning
Talent ID * The unique identifier of the talent (candidate) to add to the recruitment campaign.
Recruitment Campaign ID * The unique identifier of the recruitment campaign position where the candidate will be added.
Stage ID * The unique identifier of the stage within the recruitment campaign to assign the candidate to.

(* indicates required fields)

Output

The output of this operation is a JSON object representing the result of adding the candidate to the recruitment campaign. This typically includes details about the candidate's association with the campaign, confirmation of the assigned stage, and any metadata returned by the Pulse API.

No binary data output is expected for 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 authenticated requests.
  • Proper permissions on the Pulse API are necessary to add candidates to recruitment campaigns.

Troubleshooting

  • Common Issues:

    • Invalid or missing Talent ID, Recruitment Campaign ID, or Stage ID will cause the operation to fail.
    • Insufficient API permissions or expired credentials may result in authentication errors.
    • Providing IDs that do not exist in the Pulse system will lead to "not found" errors.

  • Error Messages:

    • "The operation "addCandidate" is not supported for resource "recruitmentCampaign"!" — Indicates a misconfiguration or unsupported operation; ensure the correct resource and operation are selected.
    • API error messages related to invalid IDs or permissions will be passed through in the output JSON under an error field if "Continue On Fail" is enabled.

  • Resolution Tips:

    • Verify all required IDs are correct and correspond to existing entities in Pulse.
    • Check API credentials and refresh or reconfigure if necessary.
    • Enable "Continue On Fail" during testing to capture detailed error information without stopping workflow execution.

Links and References

Discussion