Pulse Recruitment icon

Pulse Recruitment

Recruitment actions from Pulse API

Actions20

Overview

This node enables creating a new Stage Template within a specified Pipeline Template in a recruitment management system via the Pulse API. It is useful for automating and managing recruitment pipelines by defining stages that candidates will pass through during the hiring process.

Typical use cases include:

  • Adding a new stage to an existing recruitment pipeline template.
  • Defining stage properties such as name, description, order (index), and optional warning thresholds.
  • Automating recruitment workflows by programmatically managing pipeline stages.

For example, you might create a "Phone Interview" stage with a description and specify its position in the pipeline, optionally setting a threshold to warn if a candidate stays too long in this stage.

Properties

Name Meaning
Pipeline Template ID * The unique identifier of the pipeline template to which this stage template belongs.
Stage Name * The name of the stage template (e.g., "Phone Interview", "Technical Test").
Description * A textual description explaining the purpose or details of this stage template.
Index * The position/order of this stage within the pipeline template; must be 1 or greater.
Threshold days (Optional) Number of days after which a warning should be shown if a candidate remains in this stage; must be greater than 0 if provided.

(* indicates required fields)

Output

The node outputs a JSON object representing the newly created stage template. This typically includes all details of the stage template as returned by the Pulse API, such as its ID, name, description, index, associated pipeline template ID, and any configured warning threshold.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Pulse API using an API key credential configured in n8n.
  • The node depends on the Pulse API service being available and accessible.
  • Proper permissions are needed to create stage templates within the specified pipeline template.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Pipeline Template ID will cause the creation to fail.
    • Omitting required fields like Stage Name, Description, or Index will result in validation errors.
    • Setting the Index to less than 1 or providing a non-positive number for the threshold days (if given) will cause errors.
    • Network or authentication failures with the Pulse API can prevent successful execution.

  • Error messages:

    • "The operation "createStageTemplate" is not supported for resource "stageTemplate"!" — indicates a misconfiguration of the operation or resource parameters.
    • API error messages related to invalid IDs or missing required fields will be passed through in the node's output if "Continue On Fail" is enabled.

  • Resolutions:

    • Verify all required input properties are correctly set.
    • Ensure the Pipeline Template ID exists and is correct.
    • Check API credentials and network connectivity.
    • Use the "Continue On Fail" option to handle errors gracefully and inspect error details.

Links and References

Discussion