Pulse Recruitment icon

Pulse Recruitment

Recruitment actions from Pulse API

Actions20

Overview

This node enables managing recruitment campaigns via the Pulse API. Specifically, the "Create Recruitment Campaign" operation allows users to create a new recruitment campaign by specifying details such as the job description, target date, hiring count, and related organizational information.

Common scenarios for this node include automating the creation of recruitment campaigns when new projects or organizational needs arise, integrating recruitment workflows into broader HR automation pipelines, or syncing recruitment data from other systems.

For example, an HR team could use this node to automatically launch a recruitment campaign for a new project, specifying the number of hires needed, contract type, and associated organizational units, streamlining the recruitment process.

Properties

Name Meaning
Name * The name/title of the recruitment campaign.
Job Description * Detailed description of the job role for which recruitment is being conducted (must contain text).
Target Date * The deadline or target date by which the recruitment campaign aims to complete hiring.
Hiring Count * Number of people intended to be hired through this campaign.
Hiring Reason * Reason for hiring; options are: Staff Increase, Replacement.
Contract Type * Type of employment contract; options include Full Time, Part Time, Internship, Freelance, Others.
Employee Requestor ID * Numeric ID of the employee who requested the recruitment campaign.
Organization ID * Numeric ID of the organization related to this recruitment campaign.
Project ID * Numeric ID of the project related to this recruitment campaign.
Organizational Unit * The specific organizational unit involved in the recruitment campaign.
Pipeline Template ID * ID of the pipeline template attached to the recruitment campaign, defining recruitment stages.

(* indicates required fields)

Output

The output is a JSON object representing the newly created recruitment campaign as returned by the Pulse API. This typically includes all the details provided during creation along with additional metadata such as unique campaign ID, timestamps, and status.

No binary data output is produced by 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 within the node's codebase to perform authenticated requests.
  • Proper permissions and valid IDs (e.g., employee requestor, organization, project) must be available in the Pulse system.

Troubleshooting

  • Common Issues:

    • Missing or invalid required fields will cause the API call to fail.
    • Incorrect or unauthorized API credentials will result in authentication errors.
    • Providing non-existent IDs for employee, organization, project, or pipeline template will cause errors.

  • Error Messages:

    • "The operation "createRecruitmentCampaign" is not supported for resource "recruitmentCampaign"!" — indicates a misconfiguration of operation or resource parameters.
    • API errors related to validation or authorization will be returned in the error message field; ensure all required fields are correctly filled and credentials are valid.

  • Resolution Tips:

    • Double-check all required input properties are set and valid.
    • Verify API credentials and permissions.
    • Confirm that referenced IDs exist in the Pulse system.
    • Use the node’s "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion