Pulse Recruitment icon

Pulse Recruitment

Recruitment actions from Pulse API

Actions20

Overview

The node allows updating an existing Stage Template in a recruitment system via the Pulse API. It is useful for modifying details of a stage template such as its name, description, order index, or warning threshold days after creation. This operation helps keep recruitment workflows up to date by adjusting stage templates as hiring processes evolve.

Practical examples:

  • Renaming a stage template to reflect updated terminology.
  • Changing the order (index) of a stage in the recruitment pipeline.
  • Adding or updating a description to clarify the purpose of a stage.
  • Setting a threshold number of days after which a warning should be shown if a candidate remains in that stage too long.

Properties

Name Meaning
Stage Template ID * The unique identifier of the stage template to update.
Update Fields Collection of fields to update in the stage template:
- Stage Name New name for the stage template.
- Description New description text for the stage template.
- Index New position/order of the stage template (must be ≥ 1).
- Threshold days Number of days after which a warning is shown if a candidate stays too long in this stage (must be > 0 if provided).

Output

The node outputs a JSON object representing the updated stage template as returned by the Pulse API. This typically includes the updated properties of the stage template such as its ID, name, description, index, and warning threshold days.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Pulse API.
  • The node depends on the Pulse API service being available and accessible.
  • Proper configuration of the API credentials within n8n is necessary.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Stage Template ID will result in an error.
    • Supplying invalid values for fields (e.g., index less than 1 or negative threshold days) may cause the API to reject the update.
    • Network or authentication failures can prevent successful updates.

  • Error messages and resolutions:

    • "The operation "updateStageTemplate" is not supported for resource "stageTemplate"!" — indicates a misconfiguration; ensure the correct resource and operation are selected.
    • Errors related to missing or invalid API credentials require checking the configured API key.
    • Validation errors from the API about field values should be resolved by correcting input data according to the property constraints.

Links and References

Discussion