Pulse Recruitment icon

Pulse Recruitment

Recruitment actions from Pulse API

Actions20

Overview

This node enables updating an existing recruitment campaign within the Pulse API system. It is designed to modify various attributes of a recruitment campaign such as its name, job description, target date, hiring count, and other related organizational details.

Typical use cases include:

  • Adjusting campaign details when requirements change during the hiring process.
  • Updating the number of hires needed or changing the contract type for a campaign.
  • Modifying organizational or project associations for better tracking.

For example, if a company initially planned to hire 3 full-time employees but later decides to hire 5 part-time employees instead, this node can update those fields accordingly in the recruitment campaign record.

Properties

Name Meaning
Campaign ID * The unique identifier of the recruitment campaign to update.
Query ID * The ID of the specific query related to the update operation.
Update Fields Collection of fields to update in the recruitment campaign, including:
- Name New name for the recruitment campaign.
- Job Description Updated job description text.
- Target Date New target date for the recruitment campaign (date and time).
- Hiring Count Number of people to hire (numeric value).
- Hiring Reason Reason for hiring; options are: "Staff Increase" or "Replacement".
- Contract Type Type of contract; options include: "Full Time", "Part Time", "Internship", "Freelance", "Others".
- Requestor ID Numeric ID of the person requesting the recruitment.
- Related Organization ID Numeric ID of the related organization.
- Related Project ID Numeric ID of the related project.
- Organizational Unit Name of the organizational unit associated with the campaign.

Output

The node outputs a JSON object representing the updated recruitment campaign data as returned by the Pulse API. This typically includes all current properties of the recruitment campaign after the update has been applied.

No binary data output is involved in 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 with the node implementation to perform authenticated requests.
  • Proper permissions on the Pulse API side are necessary to update recruitment campaigns.

Troubleshooting

  • Common Issues:

    • Invalid or missing Campaign ID or Query ID will cause errors.
    • Insufficient permissions or invalid API credentials may result in authentication failures.
    • Providing invalid values for enumerated fields like Hiring Reason or Contract Type may cause request rejections.

  • Error Messages:

    • "The operation "updateRecruitmentCampaign" is not supported for resource "recruitmentCampaign"!" indicates a misconfiguration or unsupported operation.
    • Errors containing "error" in the JSON output usually indicate API-level issues; check the message for specifics.

  • Resolutions:

    • Verify that required IDs are correctly provided and exist in the system.
    • Ensure the API key credential is valid and has appropriate access rights.
    • Validate input field values against allowed options before execution.

Links and References

Discussion